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.
-----Original Message-----
From: nodejs@googlegroups.com [mailto:nodejs@googlegroups.com] On Behalf
Of William Myers
Sent: Tuesday, October 16, 2012 2:53 AM
To: nodejs@googlegroups.com
Subject: [nodejs] Forever with ssh
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.
On Tuesday, October 16, 2012 10:24:40 AM UTC-4, Chad Engler wrote:
> Just use:
> > forever start <script>
> And see what is running:
> > forever list
> And stop a script:
> > forever stop <index_or_script_name>
> -Chad
> -----Original Message----- > From: nod...@googlegroups.com <javascript:> [mailto: > nod...@googlegroups.com <javascript:>] On Behalf > Of William Myers > Sent: Tuesday, October 16, 2012 2:53 AM > To: nod...@googlegroups.com <javascript:> > Subject: [nodejs] Forever with ssh
> 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.
On Tue, Oct 16, 2012 at 11:21 AM, rhasson <rhas...@gmail.com> wrote:
> use "screen"
> On Tuesday, October 16, 2012 10:24:40 AM UTC-4, Chad Engler wrote:
>> Just use:
>> > forever start <script>
>> And see what is running:
>> > forever list
>> And stop a script:
>> > forever stop <index_or_script_name>
>> -Chad
>> -----Original Message-----
>> From: nod...@googlegroups.com [mailto:nod...@googlegroups.**com] On
>> Behalf
>> Of William Myers
>> Sent: Tuesday, October 16, 2012 2:53 AM
>> To: nod...@googlegroups.com
>> Subject: [nodejs] Forever with ssh
>> 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.
> On Tue, Oct 16, 2012 at 11:21 AM, rhasson <rhas...@gmail.com> wrote:
>> use "screen"
>> On Tuesday, October 16, 2012 10:24:40 AM UTC-4, Chad Engler wrote:
>>> Just use:
>>> > forever start <script>
>>> And see what is running:
>>> > forever list
>>> And stop a script:
>>> > forever stop <index_or_script_name>
>>> -Chad
>>> -----Original Message-----
>>> From: nod...@googlegroups.com [mailto:nod...@googlegroups.**com] On
>>> Behalf
>>> Of William Myers
>>> Sent: Tuesday, October 16, 2012 2:53 AM
>>> To: nod...@googlegroups.com
>>> Subject: [nodejs] Forever with ssh
>>> 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.
Forever daemonizes the processes, there is no need for screen. From the
README:
actions:
start Start SCRIPT as a daemon
stop Stop the daemon SCRIPT
stopall Stop all running forever scripts
restart Restart the daemon SCRIPT
restartall Restart all running forever scripts
list List all running forever scripts
...
[Daemon]
The forever process will run as a daemon which will make the target
process start
in the background. This is extremely useful for remote starting
simple node.js scripts
without using nohup. It is recommended to run start with -o -l, &
-e.
ex. forever start -l forever.log -o out.log -e err.log my-daemon.js
forever stop my-daemon.js
(bold added by me). I use this in production and it works fine.
-Chad
From: nodejs@googlegroups.com [mailto:nodejs@googlegroups.com] On Behalf
Of rhasson
Sent: Tuesday, October 16, 2012 11:22 AM
To: nodejs@googlegroups.com
Subject: Re: [nodejs] Forever with ssh
use "screen"
On Tuesday, October 16, 2012 10:24:40 AM UTC-4, Chad Engler wrote:
[mailto:nod...@googlegroups.com <javascript:> ] On Behalf Of William Myers Sent: Tuesday, October 16, 2012 2:53 AM To: nod...@googlegroups.com <javascript:>
Subject: [nodejs] Forever with ssh
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.
Note we also use --pidFile so we can monitor the process with monit as
well.
-Chad
From: nodejs@googlegroups.com [mailto:nodejs@googlegroups.com] On Behalf
Of Chad Engler
Sent: Tuesday, October 16, 2012 11:53 AM
To: nodejs@googlegroups.com
Subject: RE: [nodejs] Forever with ssh
Forever daemonizes the processes, there is no need for screen. From the
README:
actions:
start Start SCRIPT as a daemon
stop Stop the daemon SCRIPT
stopall Stop all running forever scripts
restart Restart the daemon SCRIPT
restartall Restart all running forever scripts
list List all running forever scripts
...
[Daemon]
The forever process will run as a daemon which will make the target
process start
in the background. This is extremely useful for remote starting
simple node.js scripts
without using nohup. It is recommended to run start with -o -l, &
-e.
ex. forever start -l forever.log -o out.log -e err.log my-daemon.js
forever stop my-daemon.js
(bold added by me). I use this in production and it works fine.
-Chad
From: nodejs@googlegroups.com [mailto:nodejs@googlegroups.com] On Behalf
Of rhasson
Sent: Tuesday, October 16, 2012 11:22 AM
To: nodejs@googlegroups.com
Subject: Re: [nodejs] Forever with ssh
use "screen"
On Tuesday, October 16, 2012 10:24:40 AM UTC-4, Chad Engler wrote:
[mailto:nod...@googlegroups.com <javascript:> ] On Behalf Of William Myers Sent: Tuesday, October 16, 2012 2:53 AM To: nod...@googlegroups.com <javascript:>
Subject: [nodejs] Forever with ssh
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.
> On Tue, Oct 16, 2012 at 11:21 AM, rhasson <rhas...@gmail.com> wrote:
>> use "screen"
>> On Tuesday, October 16, 2012 10:24:40 AM UTC-4, Chad Engler wrote:
>>> Just use:
>>> > forever start <script>
>>> And see what is running:
>>> > forever list
>>> And stop a script:
>>> > forever stop <index_or_script_name>
>>> -Chad
>>> -----Original Message-----
>>> From: nod...@googlegroups.com [mailto:nod...@googlegroups.com] On Behalf
>>> Of William Myers
>>> Sent: Tuesday, October 16, 2012 2:53 AM
>>> To: nod...@googlegroups.com
>>> Subject: [nodejs] Forever with ssh
>>> 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.
It does bother me a bit that people are running their node daemons in
"screen". Can I at least presume this isn't for production?
I highly recommend using runit - it restarts on failure and is very simple
to install and use, and handles logging (including timestamping and log
rotation), privilege dropping, and environment variable setting.
On Wed, Oct 17, 2012 at 12:09 AM, Axel Kittenberger <axk...@gmail.com>wrote:
> > On Tue, Oct 16, 2012 at 11:21 AM, rhasson <rhas...@gmail.com> wrote:
> >> use "screen"
> >> On Tuesday, October 16, 2012 10:24:40 AM UTC-4, Chad Engler wrote:
> >>> Just use:
> >>> > forever start <script>
> >>> And see what is running:
> >>> > forever list
> >>> And stop a script:
> >>> > forever stop <index_or_script_name>
> >>> -Chad
> >>> -----Original Message-----
> >>> From: nod...@googlegroups.com [mailto:nod...@googlegroups.com] On
> Behalf
> >>> Of William Myers
> >>> Sent: Tuesday, October 16, 2012 2:53 AM
> >>> To: nod...@googlegroups.com
> >>> Subject: [nodejs] Forever with ssh
> >>> 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.
Is there a problem with running in "screen"? I've very little actual Linux experience, but we've been very happy with running ours in "screen", lets us trivially get both the aspects of a daemon, automatic logging all output to one stream, and be able to connect to it interactively when things need to be debugged. In general, we still need something like runit to actually launch the screen'd node process, and re-launch it if it fails, but I don't see why running in a screen would be bad (but am by no means an expert =).
On Wednesday, October 17, 2012 6:33:02 AM UTC-7, Matt Sergeant wrote:
> It does bother me a bit that people are running their node daemons in > "screen". Can I at least presume this isn't for production?
> I highly recommend using runit - it restarts on failure and is very simple > to install and use, and handles logging (including timestamping and log > rotation), privilege dropping, and environment variable setting.
> On Wed, Oct 17, 2012 at 12:09 AM, Axel Kittenberger <axk...@gmail.com<javascript:> > > wrote:
>> +2 for screen. I also run my node.js daemon in a "screen".
>> On Tue, Oct 16, 2012 at 5:33 PM, Julian Lannigan >> <julian....@homes.com <javascript:>> wrote: >> > +1 for screen
>> > On Tue, Oct 16, 2012 at 11:21 AM, rhasson <rha...@gmail.com<javascript:>> >> wrote:
>> >> use "screen"
>> >> On Tuesday, October 16, 2012 10:24:40 AM UTC-4, Chad Engler wrote:
>> >>> Just use:
>> >>> > forever start <script>
>> >>> And see what is running:
>> >>> > forever list
>> >>> And stop a script:
>> >>> > forever stop <index_or_script_name>
>> >>> -Chad
>> >>> -----Original Message----- >> >>> From: nod...@googlegroups.com [mailto:nod...@googlegroups.com] On >> Behalf >> >>> Of William Myers >> >>> Sent: Tuesday, October 16, 2012 2:53 AM >> >>> To: nod...@googlegroups.com >> >>> Subject: [nodejs] Forever with ssh
>> >>> 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.
I'm no sysadmin, but I've created/worked on some extremely large systems
(thousands of machines) and nobody running anything in production
environments would ever use screen for keeping things running. It's just
not designed for that. It has horrendous potential scenarios for disaster
by people pressing the wrong keys. It doesn't deal with log rotation or
storage or timestamping. It doesn't deal with restarting failed processes.
It's designed for interactive use. It's in no way designed as a secure
keep-alive system for daemons.
I think if you hired a sysadmin (at least one worth what you pay him) he
would replace your "screen" based system in a flash.
On the other hand, I do use screen for everything else, and have it
constantly logged in doing "tail -F" on all my logs, so I can instantly see
what's going on in real time and pause and scroll back those logs if I need
to. I just don't use it for keeping daemons running.
On Wed, Oct 17, 2012 at 12:59 PM, Jimb Esser <wastel...@gmail.com> wrote:
> Is there a problem with running in "screen"? I've very little actual
> Linux experience, but we've been very happy with running ours in "screen",
> lets us trivially get both the aspects of a daemon, automatic logging all
> output to one stream, and be able to connect to it interactively when
> things need to be debugged. In general, we still need something like runit
> to actually launch the screen'd node process, and re-launch it if it fails,
> but I don't see why running in a screen would be bad (but am by no means an
> expert =).
> On Wednesday, October 17, 2012 6:33:02 AM UTC-7, Matt Sergeant wrote:
>> It does bother me a bit that people are running their node daemons in
>> "screen". Can I at least presume this isn't for production?
>> I highly recommend using runit - it restarts on failure and is very
>> simple to install and use, and handles logging (including timestamping and
>> log rotation), privilege dropping, and environment variable setting.
>> On Wed, Oct 17, 2012 at 12:09 AM, Axel Kittenberger <axk...@gmail.com>wrote:
>>> +2 for screen. I also run my node.js daemon in a "screen".
>>> On Tue, Oct 16, 2012 at 5:33 PM, Julian Lannigan
>>> <julian....@homes.com> wrote:
>>> > +1 for screen
>>> > On Tue, Oct 16, 2012 at 11:21 AM, rhasson <rha...@gmail.com> wrote:
>>> >> use "screen"
>>> >> On Tuesday, October 16, 2012 10:24:40 AM UTC-4, Chad Engler wrote:
>>> >>> Just use:
>>> >>> > forever start <script>
>>> >>> And see what is running:
>>> >>> > forever list
>>> >>> And stop a script:
>>> >>> > forever stop <index_or_script_name>
>>> >>> -Chad
>>> >>> -----Original Message-----
>>> >>> From: nod...@googlegroups.com [mailto:nod...@googlegroups.**com] On
>>> Behalf
>>> >>> Of William Myers
>>> >>> Sent: Tuesday, October 16, 2012 2:53 AM
>>> >>> To: nod...@googlegroups.com
>>> >>> Subject: [nodejs] Forever with ssh
>>> >>> 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.
Screen is really for having multiple terminals open with only 1
connection, and for working in a space that doesn't get destroyed if you
lose your connection. It isn't designed to keep a process running in a
production environment. Upstart, monit, forever, and other solutions
are.
-Chad
From: nodejs@googlegroups.com [mailto:nodejs@googlegroups.com] On Behalf
Of Matt
Sent: Wednesday, October 17, 2012 2:29 PM
To: nodejs@googlegroups.com
Subject: Re: [nodejs] Forever with ssh
I'm no sysadmin, but I've created/worked on some extremely large systems
(thousands of machines) and nobody running anything in production
environments would ever use screen for keeping things running. It's just
not designed for that. It has horrendous potential scenarios for
disaster by people pressing the wrong keys. It doesn't deal with log
rotation or storage or timestamping. It doesn't deal with restarting
failed processes. It's designed for interactive use. It's in no way
designed as a secure keep-alive system for daemons.
I think if you hired a sysadmin (at least one worth what you pay him) he
would replace your "screen" based system in a flash.
On the other hand, I do use screen for everything else, and have it
constantly logged in doing "tail -F" on all my logs, so I can instantly
see what's going on in real time and pause and scroll back those logs if
I need to. I just don't use it for keeping daemons running.
On Wed, Oct 17, 2012 at 12:59 PM, Jimb Esser <wastel...@gmail.com>
wrote:
Is there a problem with running in "screen"? I've very little actual
Linux experience, but we've been very happy with running ours in
"screen", lets us trivially get both the aspects of a daemon, automatic
logging all output to one stream, and be able to connect to it
interactively when things need to be debugged. In general, we still
need something like runit to actually launch the screen'd node process,
and re-launch it if it fails, but I don't see why running in a screen
would be bad (but am by no means an expert =).
On Wednesday, October 17, 2012 6:33:02 AM UTC-7, Matt Sergeant wrote:
It does bother me a bit that people are running their node
daemons in "screen". Can I at least presume this isn't for production?
I highly recommend using runit - it restarts on failure and is
very simple to install and use, and handles logging (including
timestamping and log rotation), privilege dropping, and environment
variable setting.
On Wed, Oct 17, 2012 at 12:09 AM, Axel Kittenberger
>>
>> use "screen"
>>
>>
>> On Tuesday, October 16, 2012 10:24:40 AM UTC-4, Chad
Engler wrote:
>>>
>>> Just use:
>>>
>>> > forever start <script>
>>>
>>> And see what is running:
>>>
>>> > forever list
>>>
>>> And stop a script:
>>>
>>> > forever stop <index_or_script_name>
>>>
>>> -Chad
>>>
>>> -----Original Message-----
>>> From: nod...@googlegroups.com
[mailto:nod...@googlegroups.com] On Behalf
>>> Of William Myers
>>> Sent: Tuesday, October 16, 2012 2:53 AM
>>> To: nod...@googlegroups.com
>>> Subject: [nodejs] Forever with ssh
>>> 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.
On Wed, Oct 17, 2012 at 6:59 PM, Jimb Esser <wastel...@gmail.com> wrote:
> Is there a problem with running in "screen"? I've very little actual
> Linux experience, but we've been very happy with running ours in "screen",
> lets us trivially get both the aspects of a daemon, automatic logging all
> output to one stream, and be able to connect to it interactively when
> things need to be debugged. In general, we still need something like runit
> to actually launch the screen'd node process, and re-launch it if it fails,
> but I don't see why running in a screen would be bad (but am by no means an
> expert =).
> On Wednesday, October 17, 2012 6:33:02 AM UTC-7, Matt Sergeant wrote:
>> It does bother me a bit that people are running their node daemons in
>> "screen". Can I at least presume this isn't for production?
>> I highly recommend using runit - it restarts on failure and is very
>> simple to install and use, and handles logging (including timestamping and
>> log rotation), privilege dropping, and environment variable setting.
>> On Wed, Oct 17, 2012 at 12:09 AM, Axel Kittenberger <axk...@gmail.com>wrote:
>>> +2 for screen. I also run my node.js daemon in a "screen".
>>> On Tue, Oct 16, 2012 at 5:33 PM, Julian Lannigan
>>> <julian....@homes.com> wrote:
>>> > +1 for screen
>>> > On Tue, Oct 16, 2012 at 11:21 AM, rhasson <rha...@gmail.com> wrote:
>>> >> use "screen"
>>> >> On Tuesday, October 16, 2012 10:24:40 AM UTC-4, Chad Engler wrote:
>>> >>> Just use:
>>> >>> > forever start <script>
>>> >>> And see what is running:
>>> >>> > forever list
>>> >>> And stop a script:
>>> >>> > forever stop <index_or_script_name>
>>> >>> -Chad
>>> >>> -----Original Message-----
>>> >>> From: nod...@googlegroups.com [mailto:nod...@googlegroups.**com] On
>>> Behalf
>>> >>> Of William Myers
>>> >>> Sent: Tuesday, October 16, 2012 2:53 AM
>>> >>> To: nod...@googlegroups.com
>>> >>> Subject: [nodejs] Forever with ssh
>>> >>> 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.
I would agree with you and that is what I expected forever start <script> to do however when I disconnect ssh then forever is also exiting. With another ssh connection I check the running of the application with ps aux while I am simultaneously connect and after to confirm what I am seeing online with the app.
Can you or someone else confirm this behavior? Otherwise, I will have to go with 'screen' as a possible solution or see if I can get vm console access to run forever in the 'actual' console.
Why are you so hung up on using forever? It's written in node which means
it can't have safe locking, it is far from 100% proven and solid. Just use
something proven instead.
On Wed, Oct 17, 2012 at 9:04 PM, William Myers <meun...@gmail.com> wrote:
> Chad,
> I would agree with you and that is what I expected forever start <script>
> to do however when I disconnect ssh then forever is also exiting. With
> another ssh connection I check the running of the application with ps aux
> while I am simultaneously connect and after to confirm what I am seeing
> online with the app.
> Can you or someone else confirm this behavior? Otherwise, I will have to
> go with 'screen' as a possible solution or see if I can get vm console
> access to run forever in the 'actual' console.
On Wed, Oct 17, 2012 at 7:56 PM, Matt <hel...@gmail.com> wrote:
> Why are you so hung up on using forever? It's written in node which means
> it can't have safe locking, it is far from 100% proven and solid. Just use
> something proven instead.
> On Wed, Oct 17, 2012 at 9:04 PM, William Myers <meun...@gmail.com> wrote:
>> Chad,
>> I would agree with you and that is what I expected forever start <script>
>> to do however when I disconnect ssh then forever is also exiting. With
>> another ssh connection I check the running of the application with ps aux
>> while I am simultaneously connect and after to confirm what I am seeing
>> online with the app.
>> Can you or someone else confirm this behavior? Otherwise, I will have to
>> go with 'screen' as a possible solution or see if I can get vm console
>> access to run forever in the 'actual' console.
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.
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.
I use it for development and testing-semi-production. You are very
right there are far superior tools. If you take Williams question
literally "I started something manually through ssh, but when I closed
the connection it died". "screen" is the answer to exactly that
problem. Maybe its good to tell, "screen is a solution to the problem
you are seeing, but actually you want to take it beyond that", or
maybe its just that
On Wed, Oct 17, 2012 at 3:32 PM, Matt <hel...@gmail.com> wrote:
> It does bother me a bit that people are running their node daemons in
> "screen". Can I at least presume this isn't for production?
> I highly recommend using runit - it restarts on failure and is very simple
> to install and use, and handles logging (including timestamping and log
> rotation), privilege dropping, and environment variable setting.
> On Wed, Oct 17, 2012 at 12:09 AM, Axel Kittenberger <axk...@gmail.com>
> wrote:
>> +2 for screen. I also run my node.js daemon in a "screen".
>> On Tue, Oct 16, 2012 at 5:33 PM, Julian Lannigan
>> <julian.lanni...@homes.com> wrote:
>> > +1 for screen
>> > On Tue, Oct 16, 2012 at 11:21 AM, rhasson <rhas...@gmail.com> wrote:
>> >> use "screen"
>> >> On Tuesday, October 16, 2012 10:24:40 AM UTC-4, Chad Engler wrote:
>> >>> Just use:
>> >>> > forever start <script>
>> >>> And see what is running:
>> >>> > forever list
>> >>> And stop a script:
>> >>> > forever stop <index_or_script_name>
>> >>> -Chad
>> >>> -----Original Message-----
>> >>> From: nod...@googlegroups.com [mailto:nod...@googlegroups.com] On
>> >>> Behalf
>> >>> Of William Myers
>> >>> Sent: Tuesday, October 16, 2012 2:53 AM
>> >>> To: nod...@googlegroups.com
>> >>> Subject: [nodejs] Forever with ssh
>> >>> 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.
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.
> 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.
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
> 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.
>> 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.
> 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
> <groundwa...@gmail.com> wrote:
>> +1 for upstart - I think using the platform native tools is good form
>> 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.
>>> 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.
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.
> > 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
> > <groundwa...@gmail.com> wrote:
> >> +1 for upstart - I think using the platform native tools is good form
> >> 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.
> >>> 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.
