Ruby on Rails

ok,

> I did use capistrano, and it would eventually stop updating the code due
> to some obscure problem. My dumb bash script never disappointed me.

I see the reason for you not in favor of using Capistrano. You sounds
frustrated to have not been able to resolve the issue you had have
with your earlier Cap implementation.
I am not saying anything against you why to go or why not to go for
Capistrano.
And I really don't know if you have anything personal against
JamisBuck(creator of Capistrano) and/or Ruby programming
language :) ... to count them a reason to not to use it apart from
considering the following advantages as compared to the script you
provided...

Your Script:
Can deploy: Yes
Keeps releases: No
Can Rollback: No
Does it know what Rollback is: No
Can just restart the server without updating code: No
Can perform additional server task(s) after/before code updation: No
Is it organized: No

Capistrano:
Can deploy: Yes
Keeps releases: Yes
Can Rollback: Yes
Does it know what Rollback is: Very well, if your latest deploy fails
and crashes the server (not a big deal, happens to lots of ninjas),
you can just fire one command "cap rollback" to bring the live server
quickly to previously functional state.
Can just restart the server without updating code: Yes
Can perform additional server task(s) after/before code updation: Yes
Is it organized: Yes, the ruby code is placed centrally on your system
as a Ruby gem, and for every application you just need to mention the
repository address, server address etc. in a configuration file.

Guys, I would just like to say, it's really better to spend some time
to get comfy with Capistrano and/or any other automated deployment
tool instead of pumping yourself to get the different scripts ready
for all server managerial work.

Needless to mention there are some other really good options available
which can be used in place of Capistrano.
e.g.
1) Vlad http://www.rubyhitsquad.com/Vlad_the_Deployer.html
2) Moonshine (and Shadow Puppet)
http://blog.railsmachine.com/articles/2009/01/16/moonshine-configuration-management-and-deployment/

Moonshine and Shadow Puppet takes the server management and deployment
to a totally different level which has not even been defined by the
Capistrano... so if you really need an advanced system administration
for Rails application's server, go for Moonshine ... but undoubtedly
it needs a certain level skills to use it up to the mark and might be
a bit difficult for the newbs.

But if you are comfortable with Capistrano and/or Vlad you can easily
look in near future to get ready for trying something awesome like
Moonshine.

So, for the beginners, I would say Capistrano could be very good
option to start with the deployments and build you understanding how
the automated deployment tools can be so very helpful in doing quick
server management(and deployment) jobs.

regards,
Sur
http://crimson9.com

On Jul 2, 5:43 pm, Fernando Perez <li...@ruby-forum.com> wrote:
> Sur Max wrote:
> > @Fernando
> > Capistrano is exactly that very "bash script" by purpose, you are
> > talking about  :D ... it's just written in Ruby
>
> > Writing another bash script won't re-invent the wheel at all.... when
> > there was no Capistrano in Rails world, I personally used to write
> > that very bash scripting..
>
> My update script:
>
> hg push ssh://... && ssh -t user@ip 'cd /myapp_path && hg update &&
> RAILS_ENV=production rake db:migrate && touch tmp/restart.txt'
>
> Do I need hundreds (thousands) of lines of ruby code to do that?
> Certainly not. But yeah, it's cap, it was started by jb, it's ruby, it
> supports svn and cvs... it's gotta be cool!
>
> I did use capistrano, and it would eventually stop updating the code due
> to some obscure problem. My dumb bash script never disappointed me.
> --
> Posted viahttp://www.ruby-forum.com/.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.