Store and edit information about your conference for consumption by views and third-party services. Provides a data model and administration panel that should accommodate most conferences.
- Fork this project
- Clone your fork, e.g.
git clone https://github.com/bendyworks/confskel
- Install dependencies by running
bundle
in the project's directory (e.g.cd confskel && bundle
) - Overwrite
app/assets/logo.png
with your conference's logo - Overwrite
app/assets/images/speaker_default.png
with the image you wish to use when a speaker doesn't have an image (a default is provided otherwise) - Set
config.site_title
to your conference's title in /config/initializers/active_admin.rb (should be around line 30) - If you use rvm: change the
.rvmrc
to match your new project's desired gemset (if you don't use rvm, don't worry about it :)
Uploading conference images requires an S3 account.
- Set up an account
- Obtain your "Access Key ID" and "Secret Access Key" from the AWS Credentials Page
- Add these credentials to
config/credentials.yml
. Seeconfig/credentials.yml.example
for an example
To get a copy of this site up and running on Heroku, assuming you're in the project's directory you made when installing, run the following in your terminal:
heroku apps:create your_conference_name
heroku config:set AWS_ACCESS_KEY_ID=your_access_key
heroku config:set AWS_SECRET_ACCESS_KEY=your_secret_key
git push heroku master
The front end development and design is likely to vary a lot from site to site, that's why this site only includes administration. Designers and front end developers should be able to get right to work, just writing views/styles/front end behaviors, without needing to change any models/controllers. Some things that might be useful:
FIXME
comments mark items you should change before starting up your siterake routes
and controller methods are your friend when trying to figure out what to name your views, and what data is provided to views