Generally, you only start the Rails application directly if you're hosting it
locally, for development purposes. For all other forms of deployment (public)
you would have a Web server to front-end requests and pass them along to your
Rails app, which would be running in Passenger or Thin or another application
server. That would be the thing you would start, not Rails itself. In the case
of Passenger, it starts when Apache does, and keeps Rails hot and ready to
receive requests as long as Apache is running.
Starting up Apache or Nginx at system boot is a really well-soved problem, you
would probably have a harder time getting it to _not_ start at boot.
Walter
On Feb 27, 2014, at 10:52 AM, Jay Amorin wrote:
> Hi,
>
> I just started ruby on rails. Would it be possible to create a start script
> that I can use on boot?
>
> /etc/init.d/my_rails_init_script.sh {start|stop}
>
> I've search the web and I can't find any.
>
> Thanks,
>
>
> Jay
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/rubyonrails-talk/2ef2cd6a-cc07-475b-a938-25026f1d4208%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/rubyonrails-talk/017593B8-49D9-42C5-B6EC-5A42AB0E2FC8%40wdstudio.com.
For more options, visit https://groups.google.com/groups/opt_out.
