Specify RACK_ENV=production in .bash_profile

Otherwise, when you run `bundle exec foreman start`, you would get:

20:01:43 web.1     | rake aborted!
20:01:43 web.1     | SQLite3::SQLException: no such table: delayed_jobs: UPDATE 
"delayed_jobs" SET "locked_by" = NULL, "locked_at" = NULL WHERE "delayed_jobs"."
locked_by" = 'host:us1 pid:5179'

...indicating that we are not in production env, and it is using the sqlite database.
Merge pull request #184 from jiehanzheng/patch-1

Specify RACK_ENV=production in .bash_profile
an attempt to fix `prepared statement "a1" already exists" issue
try again
third try
a better after_fork block without duplicating the db info
pass database.yml thru ERB parser first
Merge pull request #186 from jiehanzheng/issue186

ActiveRecord::StatementInvalid - PG::Error: ERROR:  prepared statement "a1" already exists
update translations
changed web fonts to protocol relative url
Rollback to mocha 1.8.X
Switch to mocha 1.9
rollback and freeze mocha-phantomjs
Merge pull request #194 from swanson/travis-fix

Travis fix
update translations [ci skip]
Merge remote-tracking branch 'upstream/master'