Skip to content

Commit 1cb9c01

Browse files
committed
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.
1 parent d05d531 commit 1cb9c01

1 file changed

Lines changed: 1 addition & 0 deletions

File tree

‎VPS.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -73,6 +73,7 @@ Stringer uses environment variables to determine information about your database
7373
echo 'export STRINGER_DATABASE="stringer_live"' >> $HOME/.bash_profile
7474
echo 'export STRINGER_DATABASE_USERNAME="stringer"' >> $HOME/.bash_profile
7575
echo 'export STRINGER_DATABASE_PASSWORD="EDIT_ME"' >> $HOME/.bash_profile
76+
echo 'export RACK_ENV="production"' >> $HOME/.bash_profile
7677
source ~/.bash_profile
7778

7879
Tell stringer to run the database in production mode, using the postgres database you created earlier.

0 commit comments

Comments
 (0)