42 » production http://www.42.mach7x.com Thoughts and tips about programming with Ruby on Rails Fri, 06 Aug 2010 11:57:17 +0000 en hourly 1 http://wordpress.org/?v=3.0.1 Running script/runner in production environment http://www.42.mach7x.com/2008/09/30/running-scriptrunner-in-production-environment/ http://www.42.mach7x.com/2008/09/30/running-scriptrunner-in-production-environment/#comments Tue, 30 Sep 2008 11:47:56 +0000 kosmas http://www.42.mach7x.com/?p=47 Problem
Following from a previous post about email scheduling with runner and cron, it turns out that the runner default behaviour is to run in the development environment.

Solution
Although by reading the help for the script/runner, there is a suggestion to run it with the -e production added to the end, it doesn’t seem to be working.

The solution to make it running in the production environment was to delete the first line (shebang) from step 3 on this post

#!/usr/bin/env /path_to_your_app/script/runner

and then use the following in the cron setup:

RAILS_ENV=production /path/to/your_ror_project/script/runner /path/to/your_ror_project/lib/email_scheduler.rb

Have a look on paragraph Alternative Usage here

]]> http://www.42.mach7x.com/2008/09/30/running-scriptrunner-in-production-environment/feed/ 0 cap deploy_with_migrations default behaviour http://www.42.mach7x.com/2007/11/30/cap-deploy_with_migrations-default-behaviour/ http://www.42.mach7x.com/2007/11/30/cap-deploy_with_migrations-default-behaviour/#comments Fri, 30 Nov 2007 10:35:31 +0000 kosmas http://www.42.mach7x.com/2007/11/30/cap-deploy_with_migrations-default-behaviour/ Problem
When using cap deploy_with_migrations, the default behaviour is to deploy with the migrations in the production environment.

Solution
To change this behavior add:

set  :rails_env,  "development"

in your config/deploy.rb

]]> http://www.42.mach7x.com/2007/11/30/cap-deploy_with_migrations-default-behaviour/feed/ 0