Pablo.Gallery

Ansi/ascii/rip/image gallery using the PabloDraw or other conversion engines as a backend.

Prerequisites

OS X and Linux

• Mono 3.2.x or higher
• Xamarin Studio 5.x or higher for development
• PostgreSQL 9.2 or higher

Ubuntu

In ubuntu 12.04 or 13.x, add the following ppa to your sources (ubuntu 14.04 you do not need this):

ppa:v-kukol/mono-testing

Then, install:

sudo apt-get install mono-complete mono-xsp4 mono-fastcgi-server4

You can then run xsp4 in the web directory to start the application for testing, or use the fastcgi server from nginx for production.

Windows

• .NET Framework 4.0 or 4.5
• Visual Studio 2012/2013 or Visual Studio Express 2013 for Web
• SQL Server / Express, or PostgreSQL

Database Setup

Create a database in either PostgreSQL or MSSQL then update the <connectionStrings> section in Web.config to have a "Gallery" connection string that points to your database.

PostgreSQL / MS SQL Server

You can create the database by using entity framework migrations. In Visual Studio, you can run Update-Database from the package manager console. If you are on linux/osx, you can run the scripts/update-database.sh script.

MySQL

MySQL has not been tested yet nor set up, however theoretically you should be able to use MySQL or derivitave. If the MySQL .NET driver doesn't support migrations, the database would have to be created manually (no script is provided).

Configuration Setup

There are a few changes in the Web.config to make for the system to run. Update the following in the <appSettings> section to suit your environment:

• MonoPath - If running in a mono environment, the path to the mono executable, or blank if running in windows.
• 7zipPath - Path to the 7Zip executable (defaults to /usr/bin/7z)
• UnzipPath - Path to the unzip executable (defaults to /usr/bin/unzip)
• 16c:ArchiveLocation - Location of the 16c Archive, organized in year folders
• 16c:CacheLocation - Location to place cached conversion output

*Note: If you do not have 7Zip or unzip installed, you need to comment out the corresponding Extractors in the Logic\Extractors\ExtractorFactory.cs file. This will be configurable in the future.