i found a great recipe on creating a launchd item for mongrel so that all of the mongrel servers can be start automatically when the computer is rebooted. http://blog.neontology.com/articles/2006/07/08/mongrel-with-launchd-and-lighttpd what would be the equivalent of this on my production server? currently, after every reboot, i am having to ssh into the computer and run mongrel_rails start. --~--~---------~--~----~------------~-------~--~----~ 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
On 9/17/06, Josh <jjkiesch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > i found a great recipe on creating a launchd item for mongrel so that > all of the mongrel servers can be start automatically when the computer > is rebooted. > > http://blog.neontology.com/articles/2006/07/08/mongrel-with-launchd-and-lighttpd > > what would be the equivalent of this on my production server? > currently, after every reboot, i am having to ssh into the computer and > run mongrel_rails start. >Exactly how you add/create a system service is fairly platform dependent i think, and probably better answered elsewhere. -- In brief you create a script for starting and stopping your tasks, then assign that script to the proper run levels somehow. On a production server I think you should also consider mongrel_cluster, which makes it easier to manage several processes/applications at once. I pieced my vps setup together following the two articles below: <http://www.entanke.se/blog/2006/06/26/setup-of-ruby-rails-mongrel-and-pound-on-a-vps> <http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you> Isak --~--~---------~--~----~------------~-------~--~----~ 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
On 9/17/06, Isak Hansen <isak.hansen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> On 9/17/06, Josh <jjkiesch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > i found a great recipe on creating a launchd item for mongrel so that > > all of the mongrel servers can be start automatically when the computer > > is rebooted. > > > > http://blog.neontology.com/articles/2006/07/08/mongrel-with-launchd-and-lighttpd > > > > what would be the equivalent of this on my production server? > > currently, after every reboot, i am having to ssh into the computer and > > run mongrel_rails start. > > > > Exactly how you add/create a system service is fairly platform > dependent i think, and probably better answered elsewhere. -- In brief > you create a script for starting and stopping your tasks, then assign > that script to the proper run levels somehow. > > On a production server I think you should also consider > mongrel_cluster, which makes it easier to manage several > processes/applications at once. > > > I pieced my vps setup together following the two articles below: > <http://www.entanke.se/blog/2006/06/26/setup-of-ruby-rails-mongrel-and-pound-on-a-vps> > <http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you> >These are also good reads: <http://notrocketsurgery.com/articles/2006/08/27/nginx-yet-another-rails-deployment-option> <http://mongrel.rubyforge.org/docs/mongrel_cluster.html> Isak --~--~---------~--~----~------------~-------~--~----~ 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---