Generally, you want to put this sort of thing in a rake task (instead
of a script) and then your cron is just
cd /application_rails_directory; rake do_my_thing --RAILS_ENV=production

> On Wed, Feb 25, 2009 at 12:57 PM, Duane Morin
> <rails-mailing-l...@andreas-s.net> wrote:
>>
>> I could swear I've seen instructions before on how to do this, but I
>> can't find them.  I've got a backend process that runs in the same
>> environment as my webapp, injecting data into the model. In the
>> interests of not repeating myself I'd like to take advantage of the
>> app/models from my webapp as well as my config/database.yml information.
>>
>> Normally when running the script by hand I'd go into script/console and
>> just do a 'require' on it.  This has served me quite nicely, actually.
>>
>> But I've got to put this into a cron job and take the people out of the
>> loop.  Is there a "right" way to do that, and simulate all those
>> assumptions that the console has to make before running my script?  As
>> far as I can figure the console app does not have a standard "start up,
>> run X script and then exit" option.  I suppose I can just string
>> together all the necessary requires at the top of my script, manually
>> including the model files I need and such.  I'm just trying to figure
>> out if there's a better/cleaner way already out there.
>>
>> [This feels like a FAQ and trust me, I'm googling as best I can and just
>> not finding it!  I hate asking when I feel like I should know the
>> answer...]

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to 
rubyonrails-talk+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to