- Photographer.io is an open-source photo sharing community, no longer in production.
- Created by Robert May.
- Twitter: @robotmay
No Longer Supported
I ceased operating Photographer.io last year but the repo remains here for use by others or for reference. You are welcome to ask questions but my time for providing any support is limited these days, and the repo is likely quite out of date.
Thanks to everyone who contributed and used Photographer.io.
- Ruby 2.0
- PostgreSQL 9+
- Amazon S3 and CloudFront
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), with uuid-ossp extension
- Solr (if you want search, otherwise it's safe-ish to ignore for now)
- MRI Ruby 2.0.0 (untested on anything lower, might be fine on 1.9.3)
- It currently does not run on JRuby. A port was attempted a few weeks back and it's not especially straight-forward, but it would be nice to support it in future.
First, clone the repo (ideally from your own fork):
git clone email@example.com: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.
In particular, you may want to check your username in psql with command:
$ psqlwhich should bring up your psql command line
username=#. You can update your
config/database.ymlaccordingly. Also,you may create new PG database.
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
S3 is used in development
Due to the plugins used for handling uploads, S3 support is required even in development. It's not ideal, but you'll need to fill out those S3 keys in your .env file with details for your S3 bucket.
In both development and production you will need to configure CORS correctly on Amazon. See the README in the upload script we use for more details.
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:
Instructions for running in production will be coming soon. It does run on Heroku, and you might be able to get it going with little more than the instructions above. If you do decide to host your own version of the app; great! My only request is that you switch out the branding (Photographer.io) to your own name, just to ease confusion.
I'd like to make it easier for people to maintain their own forks of the app whilst still being able to receive upstream features and bugfixes. To aid this I'll be revising a lot of the existing configuration to give you more options.
- Fork it
- Add upstream - in this case to author (
git remote add upstream firstname.lastname@example.org:afternoonrobot/photographer-io.git)
- 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