- Photographer.io is a photo sharing community.
- Created by Robert May, Afternoon Robot Ltd.
- Twitter: @robotmay and @photographer_io.
- IRC: #photographer-io on Freenode
This readme is in progress
If you have any questions don't hesitate to ask via Twitter or at email@example.com
- Rails 4.0
- Ruby 2.0
- PostgreSQL 9+
- Amazon S3 and CloudFront
There is now an active translation project on Transifex. Come along and contribute to localising this app for your language, or start up a new translation if it doesn't exist. Support for actually switching the language on Photographer.io is planned for a milestone in the next month.
The default is technically British English, which I feel I should point out before anyone goes switching all the 's' to 'z'!
To run this app you'll likely need a rough understanding of how Rails apps work these days. You will also need:
- Postgresql 9.2+ (it uses a number of DB specific features)
- Memcached (actually still used in the dev environment, though that may change)
- Solr (if you want search, otherwise it's safe-ish to ignore for now)
- Ruby 2.0.0 (untested on anything lower, might be fine on 1.9.3)
First, clone the repo (ideally from your own fork):
git clone firstname.lastname@example.org:afternoonrobot/photographer-io.git
Then move into that directory install the gems using Bundler:
Now you'll need to create a database.yml file as this isn't checked in to the repo. There's a template you can copy across for the default settings:
cp config/database.example.yml config/database.yml
You'll likely need to edit those settings for your local machine. Now you need to create and set up the database:
This will automatically set up some base data (licenses and categories).
The app depends heavily on environment variables for API keys and the like. There are two example .env files in the repo; .env.example, and .env.full_example. I believe .env.example to be the minimum required settings, though this is likely open to experimentation and could definitely use improvements.
Copy one of those files to .env and populate it:
cp .env.example .env
In theory the app will work without S3 enabled, let me know if this isn't the case.
Now start it up with Foreman:
This should start up both the web process and the worker process. To start up the automated testing you might first need to create and migrate the test DB:
RAILS_ENV=test rake db:create RAILS_ENV=test rake db:migrate
Then you can start up the automated tests with Guard:
bundle exec guard
Or manually with:
- Fork it
- Create your feature branch (
git checkout -b my-new-feature)
- Commit your changes (
git commit -am 'Add some feature')
- Push to the branch (
git push origin my-new-feature)
- Create new Pull Request