Chroma32 was created between 2009/2010 as my final-year university project and was built on top of alphas & betas of Rails 3 and development versions of associated plugins.
The project is based on a simple document management framework with support for plugins, theming and security. The code that turns the framework into Chroma32 is contained entirely within plugins so can easily be removed.
For those that are interested, plugin support is provided by a 'rails engine' called Plugineer that can be found in the lib/engines directory with an extension to ActiveRecord that can be found in the lib/extensions directory.
Licensing information for Chroma32 can be found in the LICENSE.txt file contained in this repository.
Chroma32 is a photographic asset management system built on a custom document management framework. This system in it's current guise provides a basic web application through which digital images can be easily distributed to friends, family & event clients. With full support or user authentication, authorisation and event management.
Once you've checked out the app you'll need to run:
git submodule init
git submodule update
To ensure you have the required libraries.
These requirements will need to be satisfied before the application can be installed, automatically or manually;
- Ruby 1.8.x or above.
- RubyGems 1.3.6 or greater.
- Rake 0.8.x or higher (RubyGem).
- Bundler 0.9.16 or greater (RubyGem).
- The freeimage libraries (for the image_science RubyGem).
- SQLite libraries (for the sqlite3-ruby RubyGem).
From with the application directory (defaults to an SQLite3 databse);
From within the application directory;
If the above step fails due to an error installing the MySQL gem
you will need to edit Gemfile and comment or remove the line
- Copy config/database.example.yml to config/database.yml.
- Customise the configuration in this file to suit your needs.
Running The Application
After completing the installation steps you should be able to
the application by running the command
In your web browser you can then navigate to http://localhost:3000/, the default email address for logging in is firstname.lastname@example.org and the default password is changeme. You can change both of these in the administrative control panel.