This repository was archived by the owner on Oct 1, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Installation
Stephen Yeargin edited this page Aug 12, 2014
·
10 revisions
-
Bundler (
gem install bundler
) -
Bower (
npm install bower -g
) -
PosgtresSQL (
brew install postgresql
) -
Mailcatcher (
gem install mailcatcher
) - Heroku Toolbelt (for deployment to server, reading configs)
- An Amazon S3 bucket for ticket files (see
heroku config
for credentials)
- Clone the repository into your projects directory
- Execute
bundle install
(for required gems) - Execute
bower install
(for required JS assets) - Execute
rake db:setup
(creates the development and test database and seeds the initial data) - Run
rake test
to verify that existing tests pass - Run
mailcatcher
to bring up the local email transport (registration fails without it) - Execute
rails server
to bring up a local instance - Register for an account through the normal process
The following are used within the application:
-
SEATSHARE_S3_KEY
- S3 credentials to use for storing ticket files -
SEATSHARE_S3_SECRET
- S3 credentials to use for storing ticket files -
SEATSHARE_S3_BUCKET
- Bucket name to use for storing ticket files -
SEATSHARE_S3_PUBLIC
- Public address for S3 downloads -
SIMPLE_FORM_API_TOKEN
- The private API token for a Simple Form instance -
SIMPLE_FORM_FORM_API_TOKEN
- The public API token for a Simple Form instance -
SODA_USERNAME
- Username for SODA from XML Team -
SODA_PASSWORD
- Password for SODA from XML Team -
SODA_ENVIRONMENT
- Eitherdevelopment
orproduction
-
MANDRILL_SMTP_USER
- User identifier for Mandrill (production only) -
MANDRILL_SMTP_PASS
- API key for Mandrill (production only) -
MANDRILL_SMTP_HOST
- Hostname to use with Mandrill (production only) -
GOOGLE_ANALYTICS_ID
- Google Analytics profile identifier (production only) -
MIXPANEL_API_KEY
- API key for Mixpanel (production only)
The easiest way to do this is to create a file called config/local_env.yml
(see the example file in that directory). When configuring on Heroku, you will simply add these as configuration settings. To see the current production values, simply run heroku config
.