Capistrano should be run from your workstation, not from the server. It is 
designed to deploy the software to the server, and the server's own 
configuration (monit, upstart, init.d scripts, launchd, dbus, etc) are 
responsible for running the daemons.  

Capistrano includes a legacy "start" command from the days before Rails had 
Passenger  mod_rails and one had to explicitly start a mongrel pool on every 
deployment, this hasn't been true for a number of years. The 'restart' command 
exists for anyone not in a position to use monit (or similar) to restart their 
daemons in a sane way, this applies to users of Unicorn (and thus Rainbows & 
related) where monit can't/won't signal URS2 for a seamless restart, and users 
of mod_rails, who can achieve better performance from touching 
./tmp/restart.txt, rather than restarting the whole apache daemon.

The "stop" command also exists, in the rare case that someone really wants to 
stop their production daemons, again - this made more sense in the days of 
script/spin (obsolete since 5 years?) - "stop" is more commonly replaced by 
"web:disable" - replacing the index site with a static HTML file for deployment 
safety reasons.

I hope this clarifies the purpose of the tool for you.  


On Thursday, April 19, 2012 at 1:15 PM, Bráulio Bhavamitra wrote:

> But considering you just want to run cap deploy:start on boot.
> What would you do?
>  
> Where are you going to put recipes?
> How to load gem environment so capistrano is available on system?
>  
> I surely can do this, but I wanted an example.
>  
> On Thu, Apr 19, 2012 at 06:06, Lee Hambley <[email protected] 
> (mailto:[email protected])> wrote:
> > There is no provision or best practice for Capistrano to manage your 
> > daemons.
> >  
> > On Wednesday, April 18, 2012 at 8:31 PM, Bráulio Bhavamitra wrote:
> >  
> >  
> >  
> > > Hello all,
> > >  
> > > I would like to know the best practices and references to
> > > servers start on boot.
> > >  
> > > Even with high uptime servers, we need to certify that server(s)  
> > > are running after a reboot, so this is necessary...
> > >  
> > > I saw some just copying scripts to /etc/init.d and activating them.
> > > But I would like to know more...
> > >  
> > > Thankfully,
> > > bráulio
> > >  
> > >  
> > >  
> > > --  
> > > * You received this message because you are subscribed to the Google 
> > > Groups "Capistrano" group.
> > > * To post to this group, send email to [email protected] 
> > > (mailto:[email protected])
> > > * To unsubscribe from this group, send email to 
> > > [email protected] 
> > > (mailto:[email protected]) For more options, visit 
> > > this group at http://groups.google.com/group/capistrano?hl=en  
> >  
> > --  
> > * You received this message because you are subscribed to the Google Groups 
> > "Capistrano" group.
> > * To post to this group, send email to [email protected] 
> > (mailto:[email protected])
> > * To unsubscribe from this group, send email to 
> > [email protected] 
> > (mailto:capistrano%[email protected]) For more options, visit 
> > this group at http://groups.google.com/group/capistrano?hl=en
> --  
> * You received this message because you are subscribed to the Google Groups 
> "Capistrano" group.
> * To post to this group, send email to [email protected] 
> (mailto:[email protected])
> * To unsubscribe from this group, send email to 
> [email protected] 
> (mailto:[email protected]) For more options, visit this 
> group at http://groups.google.com/group/capistrano?hl=en  

-- 
* You received this message because you are subscribed to the Google Groups 
"Capistrano" 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/capistrano?hl=en

Reply via email to