Script for production server

ruby-talk
1

Hello,

I'm pretty new with ruby and I've just installed retrospectiva with
success within ruby enterprise edition.
I ran with success the command : /XXXXX/bin/ruby script/server -e
production -p3000
Unfortunately as I close the shell, the server shut down.
How can I test that the server is in production in order to make it as a
service in a script.

best regards

2

This is not a ruby specific problem.

All processes started "normally" from a shell are terminated when the shell exits.

There are many, many posibillities to avoid this, the most easy way would be the use of the programm screen. But it has several diadvantages.

I suggest to use a process supervisor (it will restart your programm when it crashes, and takes care of starting it after your server comes up).

Personally I use:

supervise (from djbs deamontools) and
monit

Feel free to google :wink:

Mfg

Markus

···

On 06/22/2010 11:37 AM, Florent THOMAS wrote:

Hello,

I'm pretty new with ruby and I've just installed retrospectiva with
success within ruby enterprise edition.
I ran with success the command : /XXXXX/bin/ruby script/server -e
production -p3000
Unfortunately as I close the shell, the server shut down.
How can I test that the server is in production in order to make it as a
service in a script.

best regards

3

Florent THOMAS wrote:

Hello,

I'm pretty new with ruby and I've just installed retrospectiva with
success within ruby enterprise edition.
I ran with success the command : /XXXXX/bin/ruby script/server -e
production -p3000
Unfortunately as I close the shell, the server shut down.
How can I test that the server is in production in order to make it as a
service in a script.

best regards

Maybe this is actually a Rails specific question? Just use the "-d" flag
to daemonize the server.

···

--
Posted via http://www.ruby-forum.com/\.

4

Thanks a lot for your answer.

I will search in this direction.
I was just wondering if there is a ruby command to test wether an
application runs or not.
Best regards

···

Le mardi 22 juin 2010 à 18:47 +0900, Markus Schirp a écrit :

This is not a ruby specific problem.

All processes started "normally" from a shell are terminated when the
shell exits.

There are many, many posibillities to avoid this, the most easy way
would be the use of the programm screen. But it has several diadvantages.

I suggest to use a process supervisor (it will restart your programm
when it crashes, and takes care of starting it after your server comes up).

Personally I use:

supervise (from djbs deamontools) and
monit

Feel free to google :wink:

Mfg

Markus

On 06/22/2010 11:37 AM, Florent THOMAS wrote:
> Hello,
>
> I'm pretty new with ruby and I've just installed retrospectiva with
> success within ruby enterprise edition.
> I ran with success the command : /XXXXX/bin/ruby script/server -e
> production -p3000
> Unfortunately as I close the shell, the server shut down.
> How can I test that the server is in production in order to make it as a
> service in a script.
>
> best regards
>

5

Also you can use the nohup command this prevents that the command ends on shell exit.

hackob desde Blackberry®.

···

-----Original Message-----
From: Florent THOMAS <mailinglist@tdeo.fr>
Date: Tue, 22 Jun 2010 18:51:31
To: ruby-talk ML<ruby-talk@ruby-lang.org>
Reply-To: ruby-talk@ruby-lang.org
Subject: Re: script for production server

Thanks a lot for your answer.

I will search in this direction.
I was just wondering if there is a ruby command to test wether an
application runs or not.
Best regards

Le mardi 22 juin 2010 à 18:47 +0900, Markus Schirp a écrit :

This is not a ruby specific problem.

All processes started "normally" from a shell are terminated when the
shell exits.

There are many, many posibillities to avoid this, the most easy way
would be the use of the programm screen. But it has several diadvantages.

I suggest to use a process supervisor (it will restart your programm
when it crashes, and takes care of starting it after your server comes up).

Personally I use:

supervise (from djbs deamontools) and
monit

Feel free to google :wink:

Mfg

Markus

On 06/22/2010 11:37 AM, Florent THOMAS wrote:
> Hello,
>
> I'm pretty new with ruby and I've just installed retrospectiva with
> success within ruby enterprise edition.
> I ran with success the command : /XXXXX/bin/ruby script/server -e
> production -p3000
> Unfortunately as I close the shell, the server shut down.
> How can I test that the server is in production in order to make it as a
> service in a script.
>
> best regards
>

6

thanks for all your answers.
I found a package that works fine in Centos via webmin.

Best regards

···

Le mardi 22 juin 2010 à 21:50 +0900, hackob@hackob.net a écrit :

Also you can use the nohup command this prevents that the command ends on shell exit.

hackob desde Blackberry®.

-----Original Message-----
From: Florent THOMAS <mailinglist@tdeo.fr>
Date: Tue, 22 Jun 2010 18:51:31
To: ruby-talk ML<ruby-talk@ruby-lang.org>
Reply-To: ruby-talk@ruby-lang.org
Subject: Re: script for production server

Thanks a lot for your answer.

I will search in this direction.
I was just wondering if there is a ruby command to test wether an
application runs or not.
Best regards

Le mardi 22 juin 2010 à 18:47 +0900, Markus Schirp a écrit :

> This is not a ruby specific problem.
>
> All processes started "normally" from a shell are terminated when the
> shell exits.
>
> There are many, many posibillities to avoid this, the most easy way
> would be the use of the programm screen. But it has several diadvantages.
>
> I suggest to use a process supervisor (it will restart your programm
> when it crashes, and takes care of starting it after your server comes up).
>
> Personally I use:
>
> supervise (from djbs deamontools) and
> monit
>
> Feel free to google :wink:
>
> Mfg
>
> Markus
>
>
>
>
> On 06/22/2010 11:37 AM, Florent THOMAS wrote:
> > Hello,
> >
> > I'm pretty new with ruby and I've just installed retrospectiva with
> > success within ruby enterprise edition.
> > I ran with success the command : /XXXXX/bin/ruby script/server -e
> > production -p3000
> > Unfortunately as I close the shell, the server shut down.
> > How can I test that the server is in production in order to make it as a
> > service in a script.
> >
> > best regards
> >
>