I have been using Foreman to run my jobs locally which can also export
upstart jobs.

Foreman is a ruby gem however, so over the weekend I decided to port a Node
version of foreman. http://nodefly.github.com/node-foreman/

I will be adding to the module over the next few weeks, if anyone would
like to help field test it, it would be much appreciated. It can export
upstart jobs that are not foreman dependent, so that should lower the risk
of using it.

Thanks!

- Jacob Groundwater

On Fri, Oct 19, 2012 at 6:09 PM, William Myers <[email protected]> wrote:

> I appreciate everyone's great insight and I will go with upstart!
>
>
> On Oct 19, 2012, at 8:21 AM, Tim Caswell <[email protected]> wrote:
>
> > I run all my sites using upstart.
> >
> > http://creationix.com/
> > http://howtonode.org/
> > http://nodebits.org/
> > http://luvit.io/
> >
> > The sites themselves are mostly static content, so I don't need
> > cluster or anything.  The auto-restart directive in upstart keeps them
> > running between crashes and server reboots perfectly.
> >
> > On Thu, Oct 18, 2012 at 10:59 PM, Jacob Groundwater
> > <[email protected]> wrote:
> >> +1 for upstart - I think using the platform native tools is good form
> >>
> >> It can also be complimented with
> >> [start-stop-daemon](http://man.he.net/man8/start-stop-daemon) when
> required.
> >>
> >> On Thursday, October 18, 2012 6:39:24 AM UTC-7, Clay Simmons wrote:
> >>>
> >>> I like using upstart on Ubuntu to keep my node process running. Not
> sure
> >>> if this is considered bad form, but I've been using it in production
> for
> >>> about 8 months without any issues.
> >>>
> >>> https://gist.github.com/3911822
> >>>
> >>> If you're using screen, not to keep your node processes running, but
> just
> >>> for doing things in the shell, I would recommend giving tmux a try.
> >>>
> >>> On Tuesday, October 16, 2012 2:53:18 AM UTC-4, William Myers wrote:
> >>>>
> >>>> Is that a way to run forever in an ssh connection so that it
> continues to
> >>>> run even after the connection has been severed?
> >>>>
> >>>> Currently, I have only had success with $ nohup node app.js however I
> >>>> would like to use forever and thought that it could be used like a
> daemon
> >>>> tool to keep a process going.
> >>
> >> --
> >> Job Board: http://jobs.nodejs.org/
> >> Posting guidelines:
> >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> >> You received this message because you are subscribed to the Google
> >> Groups "nodejs" group.
> >> To post to this group, send email to [email protected]
> >> To unsubscribe from this group, send email to
> >> [email protected]
> >> For more options, visit this group at
> >> http://groups.google.com/group/nodejs?hl=en?hl=en
> >
> > --
> > Job Board: http://jobs.nodejs.org/
> > Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> > You received this message because you are subscribed to the Google
> > Groups "nodejs" group.
> > To post to this group, send email to [email protected]
> > To unsubscribe from this group, send email to
> > [email protected]
> > For more options, visit this group at
> > http://groups.google.com/group/nodejs?hl=en?hl=en
>
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Reply via email to