Post your deploy.rb what your experiencing isn't normal. What version of capistrano
What os are you deploying to? On Dec 13, 2010, at 12:14 PM, horseshoe7 <[email protected]> wrote: > Hi Donovan, > yeah, sorry to bark at you. It's just been highly frustrating that > nobody has documented this issue, but then I realize that instead of > just looking for recipes online, writing my own tasks could be > quicker. > > I was using :remote_cache, but got these problems there as well, > but :clear_release_path could do the trick in the end. I'll give it a > try. > > To bring it back to my general question - is there no way to 'force' > things to get done? I suppose that would be at a bash command level, > like the rm -rf command will force things. What about ln -rf ? does > that work? > > Thanks for your help! > > > On Dec 13, 9:07 pm, Donovan Bray <[email protected]> wrote: >> You were asking for help for some bizarre behavior, and you were skipping a >> step, I'm not a mind reader I could only infer as much as you wrote. It >> seemed to me natural to verify you had followed a normal progression to get >> where you got yourself. >> >> Without looking at your code we can't predict all of the custom before and >> after callbacks that may change by calling update_code directly ie: possibly >> missing any callbacks you yourself have done for deploy. I was simply making >> sure you were correctly using capistrano. Jumping directly to update_code is >> abnormal. >> >> I don't use the :copy strategy, I have a feeling that might be where the >> problem most likely lies. >> >> I use the :remote_cache strategy for all of my deployments, but I still run >> into what you describe because I overwrite how Capistrano generates the >> release path, so I use this task to make sure the directory doesn't exist >> when I do a full deploy. >> >> before "deploy:update_code", "deploy:clear_release_path" >> >> namespace :deploy do >> desc "Clear the release_path for a new checkout" >> task :clear_release_path, :roles=>[:app] do >> run "rm -rf #{release_path}" >> end >> end >> >> Try the above, or try a different strategy. >> >> Consider posting your deploy.rb as a gist, or other snippit posting service. >> >> On Mon, Dec 13, 2010 at 9:34 AM, horseshoe7 <[email protected]> wrote: >>> obviously. but deploy:update_code is a sub-task of deploy, so if it >>> doesn't work, neither will deploy >> >>> I don't mean to be rude, but it's pretty much safe to assume that all >>> users of capistrano would have tried deploy:setup and then deploy, so >>> perhaps you're trying to help, but I wouldn't have spent hours trying >>> to figure this out if that were the solution. it's in every >>> introductory document. > > -- > * 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 -- * 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
