Dear all I created a module in my_rails_project/lib/ssc.rb. I can execute the method in rails console (i.e. SSC::Monitor.method1(a,b)). How can I execute the method regularly? I am using Linux, can I do it using `crontab`? Thank you. module SSC class Monitor def self.method1(a,b) bla bla bla some code will access the model class end def self.method1(a,b) end end end Many thanks Valentino
on 2009-02-13 05:48
on 2009-02-13 05:53
Dear all I tried script/runner for this, but every execution need to initialize the rails environment. Any other good idea for it? What is your good/best practice? Many thanks Valentino
on 2009-02-13 06:26
Especially if this method is accessing your models, I don't see a way around loading your entire rails environment. I think a more common solution would be to create a rake task which you invoke with cron... On Feb 12, 10:53 pm, Valentino L. <email@example.com>
on 2009-02-13 06:31
> I think a more common solution would be to create a rake task which > you invoke with cron... Thank for your reply How can I do it with rake task? Can you give me some reference? Thanks again Valentino
on 2009-02-13 06:34
Check out http://railscasts.com/episodes/128-starling-and-workling and http://railscasts.com/episodes/130-monitoring-with-god There are a number of different ways to have a task persist, and run on a regular schedule. I've also previously used background-db and cron seems to be a popular option. I tend to go with whatever has the easiest tutorials that i can find! Anyone else feel free to weigh in if you have any more suggestions.
on 2009-02-13 11:25
on 2009-02-13 17:55
I use cron to schedule wget: wget http://localhost:3000/cron cron_controller invokes your method
on 2009-02-13 18:08
That's a great idea, until someone in the outside finds out about that path/resource. You're opening up too much and scriptkiddies can get happy attempting a DoS. Wondering if you handle that somehow (IP address check or something)?
on 2009-02-13 18:53
Harold A. Gimenez wrote: > That's a great idea, until someone in the outside finds out about that > path/resource. You're opening up too much and scriptkiddies can get > happy attempting a DoS. Wondering if you handle that somehow (IP address > check or something)? How about using HTTP basic authentication so only authorized clients can access the controller action? Which would be only your rake task. I haven't thought this through, It's just the first thing that came to mind.
on 2009-02-13 19:22
If there are no hostile users on the server, in the controller: if local_request? do the action else ignore or log hostile action end HTH, Jeffrey Quoting Harold A. Gimenez <firstname.lastname@example.org>:
on 2009-02-14 06:47
Mario G. wrote: > I use cron to schedule wget: > > wget http://localhost:3000/cron > > cron_controller invokes your method Thanks, it is a very good idea. How about if my action require 2 parameters? How to do that? Thanks again Valentino
on 2009-02-14 07:21
That can be spoofed Blog: http://random8.zenunit.com/ Learn rails: http://sensei.zenunit.com/ On 14/02/2009, at 4:21 AM, "Jeffrey L. Taylor" <email@example.com>
on 2009-02-14 07:52
>> wget http://localhost:3000/cron >> >> cron_controller invokes your method > > Thanks, it is a very good idea. How about if my action require 2 > parameters? How to do that? Let me further elabroate on my question. For example in my Cron Controller def someaction some_method(params[:one],params[:two]) end Is it possible to do this in my crontab as follow? 10 10 * * * wget http://localhost:3000/cron/someaction "para1" "para2" Many thanks Valentino
on 2009-02-14 17:13
On Saturday 14 February 2009 12:52 am, Valentino L. wrote: > Is it possible to do this in my crontab as follow? > > 10 10 * * * wget http://localhost:3000/cron/someaction "para1" "para2" I'm not sure, but an alternative is to put the wget command in a small shell script (Linux talk, iiuc) or a .bat file (MS talk, iiuc). Then invoke that shell script or .bat file from cron. Randy K. -- I didn't have time to write a short letter, so I created a video instead.--with apologies to Cicero, et.al.
on 2009-02-14 18:14
No quite like that. If you're sending an HTTP GET request to any URL, you would pass parameters to the URL itself, something like: http://localhost:3000/cron?param1=value1¶m2=value2 etc What looks attractive to me about this approach (of using wget via cron instead of a rake task) is that you are not bringing up an entire rails environment to handle a task. There's less overhead. Just be sure to lock it down with a combination of things that have been suggested here: IP Address check, local_request?, http basic authentication. There may be more you can do... On Sat, Feb 14, 2009 at 12:52 AM, Valentino L. <
on 2009-02-15 11:20
Citation needed. Quoting Julian L. <firstname.lastname@example.org>:
on 2009-02-15 16:10
> def someaction > some_method(params[:one],params[:two]) > end > > Is it possible to do this in my crontab as follow? > > 10 10 * * * wgethttp://localhost:3000/cron/someaction"para1" "para2" > You will need to pass the para1, and para2 to the someaction method so at a minimum you have to change the signature of the someaction method as below: def someaction para1, para2 ... end now within this method you can do anything you want only thing is that this method needs to be public in scope and you need to make sure that it requires no authentication otherwise your wget request will fail. I usually use script/runner in Rails for such needs. wget may or may not work depending on how restful your routes are and controller action is. Bharat