Browse and subscribe to the trip calendar for great justice
Written in Ruby. Version 2.0.x
RVM provides a mechanism for managing multiple versions of Ruby and project-specific dependency sets (gemsets). The .rvmrc file in the project directory specifies the version of the ruby interpreter and the name of the gemset to use for this project.
# Install RVM
$ \curl -#L https://get.rvm.io | bash -s stable --ruby
# Load RVM in your current shell (not needed if you close the shell and open a new one)
$ source ~/.rvm/scripts/rvm
# If you did not follow the instructions provided in the output of the installation script, run these commands and do what they say
$ rvm requirements
$ rvm notes
# Install Ruby 2.0
$ rvm install 2.0.0
# Load the project-specific RVM configuration
$ source .rvmrc
Using /Users/bcm/.rvm/gems/ruby-2.0.0-p0 with gemset oac
# Ensure rvm is using the right ruby and gemset
$ rvm info
ruby-2.0.0-p0@oac:
...Bundler is used to manage dependencies.
# Install bundler
$ gem install bundler
# Install dependencies
$ bundleA project-specific Bash script provides a number of utility functions.
# Load bash script
$ source etc/bashrcThe system is expected to provide services for data storage etc, including Postgres and Redis. See below for how to install them.
# Start services
$ oac-start-services
# Stop services
$ oac-stop-servicesOur deployment platform is Heroku.
You'll need to install the Heroku Toolbelt which provides a command line application for communicating with Heroku. Note that this installs a self-contained package including Ruby and Git and it ignores your RVM ruby and gemset. Don't worry about any of that; just use the heroku script that it provides.
Next you'll need to set up a Heroku account if you don't already have one and have it added to the staging application as a collaborator.
Configuration items specific to the host environment are configured in the .env file. This file is read when the server starts up and its contents are made available to the server process as environment variables. The file is ignored by git and must be created by hand.
# yes, "none" is correct for RACK_ENV in development due to how Unicorn works
$ cat .env
RACK_ENV=none
RAILS_ENV=developmentData is stored in PostgreSQL.
Database connection information is the one exception we don't put in the .env files (due to incomplete support in Active Record). This information for all environments is provided in config/database.yml.
Use these commands to install Postgres and set up the database:
# Install Postgres
$ brew install postgres
# Create the database user (role) with a password and permission to create databases
$ createuser -P -d oac
Enter password for new role: oac
Enter it again: oacUse these commands to create and migrate the database:
# Creates the database
$ rake db:create
# Applies migrations to arrive at the final schema
$ rake db:migrateRuby tests are run using the RSpec framework.
$ rake spec
..................
Finished in 2.2 seconds
18 examples, 0 failures
Randomized with seed 45111The server runs on port 5000 using the Unicorn web server. Foreman is used to launch the web server and Sidekiq worker processes.
$ foreman start
10:47:07 web.1 | started with pid 52646
10:47:08 web.1 | I, [2014-07-14T10:47:08.075013 #52646] INFO -- : Refreshing Gem list
10:47:09 web.1 | I, [2014-07-14T10:47:09.283276 #52646] INFO -- : listening on addr=0.0.0.0:5000 fd=10
10:47:09 web.1 | I, [2014-07-14T10:47:09.437697 #52646] INFO -- : master process ready
10:47:09 web.1 | I, [2014-07-14T10:47:09.442695 #52649] INFO -- : worker=0 ready
10:47:09 web.1 | I, [2014-07-14T10:47:09.445419 #52650] INFO -- : worker=1 ready
10:47:09 web.1 | I, [2014-07-14T10:47:09.447653 #52651] INFO -- : worker=2 ready
The web server is now running at http://localhost:5000.