github-migration/whenever
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

I am adding RVM gotcha directions to the README since I ran into the same issue as another user https://github.com/javan/whenever/issues/110 and thought at first it may be related to Whenever. The wiki may be a good place for this instruction, but I find it much more useful / easier to find in the README. The wikis homepage doesn't link to the relevant page, and it could be difficult for users to find (as it was for me).

Browse Source
This commit is contained in:
Jeff Dutil 2011-05-31 18:23:59 -07:00
parent 1214114c40
commit 7be0626800
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -102,6 +102,14 @@ If you are using different environments (such as staging, production), then you
The capistrano variable `:stage` should be the one holding your environment name. This will make the correct `:environment` available in your schedule.rb. The capistrano variable `:stage` should be the one holding your environment name. This will make the correct `:environment` available in your schedule.rb.
### RVM Integration
If your production environment uses RVM (Ruby Version Manager) you will run into a gotcha that causes your cron jobs to hang. This is not directly related to Whenever, and can be tricky to debug. Your .rvmrc files must be trusted or else the cron jobs will hang waiting for the file to be trusted. A solution is to disable the prompt by adding this line to your user rvm file in `~/.rvmrc`
rvm_trust_rvmrcs_flag=1
This tells rvm to trust all rvmrc files, which is documented here: http://wayneeseguin.beginrescueend.com/2010/08/22/ruby-environment-version-manager-rvm-1-0-0/
### The `whenever` command ### The `whenever` command
$ cd /my/rails/app $ cd /my/rails/app