I also posted this here: http://stackoverflow.com/questions/4429404/how-do-i-force-capistrano-to-overwrite-existing-files-folders-on-deployupdate
On 13 Dez., 12:54, horseshoe7 <[email protected]> wrote: > Hi, > > In another post I commented on how i find it strange that the deploy > task has no switch to ignore "File/Directory already exists" and just > overwrite what's already there. > > Now, I find it even more crazy that I do the following: > > cap deploy:setup (# which will create the releases folder, shared, > etc. on the server. This works) > > cap deploy:update_code > > and it fails because it says: > > ** [myserver.com :: err] fatal: could not create work tree dir '/ > kunden/264063_10115/smf-services/appbaukasten/test/releases/ > 20101213114233'.: File exists > > But it was this SAME script that created that folder!! So there's no > way for this task to ever complete successfully. > > I'm using :deploy_via, :copy > > and using Ruby 1.8.7 and capistrano 2.5.2 > > Can someone help me as to how I can make my deploy scripts take a -- > force switch, to make it just overwrite something that already exists > on the server? I can't tell you how many hours I've spent trying to > solve this problem and it's highly frustrating that people talk about > Capistrano and what it can do for you and yet I'm stuck on the > simplest case. -- * 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
