Scott, thanks for the actual data on time taken moving to Capistrano. My gut reaction was that it would take more than an hour to get Capistrano working in a new environment. I just set up Capistrano for a couple of servers of mine and it took most of the day - and I had the luxury of having a deploy destination that was not in active use while I was setting it up (no worries about taking down the live sites while I was getting stuff taken care of).
I don't know about everyone else, but my time estimation skills are pretty bad - particularly in situations where I am thinking "this will be straightforward". I am trying to be better at including time for all the stuff that comes up along the way. It is nice to have actual data from others to help confirm the need for projecting that time. Quoting Scott Olmsted <[email protected]>: > My log says it took me two hours to create several shared > directories, move the content there, and get a new Capistrano script > working to make the soft links in the right places and handle > whatever else, so maybe I'm just slow. I may have had some other > problem I don't recall now. > > Then I show almost five hours of puzzling over the problems I had, > and submitting tickets to RailsPlayground to get them to do what they > needed to do, including kill the old app and keep it from being > restarted (it kept rising from the dead). This new client runs on > Slicehost, so there won't be any help (or hindrance) of that sort. I > may need assistance from, say, Rob, who says he configures servers > for fun ("it's relaxing, like rolling coins" he said after Nick's > talk the other night) :^) > > Scott > > > At 12:38 PM 1/15/2010, you wrote: > >hmm it shouldn't take you hours, maybe 1 hour max unless their > >server is really messed. > > > >- Matt > > > >On Fri, Jan 15, 2010 at 12:32 PM, Scott Olmsted > ><<mailto:[email protected]>[email protected]> wrote: > >I don't need convincing, Patrick, I'm a confirmed Capistrano user on > >projects where it was in place or I put it in place (except for > >Heroku, which deploys via Git; Nick Zadrozny's suggestion about > >tagging the Git branch so it can be found again easily could be useful > >there). > >Now I must tell the client that the first thing I must do is spend > >some hours on something that produces no visible benefit at all. I > >did this on another project on a managed host (there wasn't even a > >script, I guess they just copied files in) and it took quite a few > >hours to get all the soft links and other stuff right and the tech > >people to point Apache and other things to the new code location. > >Blew their budget, but had to be done if I was going to continue to > >work on the site. > >Scott > > > >At 12:13 PM 1/15/2010, you wrote: > >>You should definitely use Capistrano, Scott. > >>It's well-documented and can handle most deployments. And by > >>learning it now, you'll be able to apply that knowledge to future > >>Rails app deployments. > >>Trust me on this. Months from now... when you reflect on this > >>thread and realize how much time you've saved with Capistrano, you > >>can buy me a beer. ;) > >>-- Patrick
-- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
