thanks for a great tool!
On Thursday, October 31, 2013 11:27:41 AM UTC-4, Lee Hambley wrote: > > 3.1 won't assign a Pty, so dotfiles and colours should be less of an issue. > > Thanks for reporting back! > On 31 Oct 2013 16:21, "Gary Leydon" <[email protected] <javascript:>> > wrote: > >> The problem was the environment variable CLICOLOR=1 in my .bashrc. >> Before the rm -rf command runs , the ls command runs to get a list of >> directories in the release directory. Because I had CLICOLOR=1 that list of >> directories comes back from the ls command with invisible escape codes to >> turn them blue on a terminal. When the rm -rf command tries to run it is >> working on a string that looks ilke this internally (though the escape >> sequences are invisible on screen, I just see blue text): >> >> rm -rf, >> /path/to/releases/\e[34m20131030204607\e[39;49m\e[0 >> \e[34m20131030204659\e[39;49m\e[0m, >> \e[34m20131030205506\e[39;49m\e[0m, \e[34m20131030210411\e[39;49m\e[0m >> >> So that is why rm -rf fails. >> >> moving export CLICOLOR=1 into .bash_profile fixed it >> >> >> On Wednesday, October 30, 2013 2:47:22 PM UTC-4, Gary Leydon wrote: >>> >>> No idea, I thought there must have been something funky in a script >>> somewhere but this same script works fine up until I exceed the value of >>> keep_releases so I don't think it's 'noise' in one of the tasks, I'll poke >>> around some more though thanks >>> >>> >>> On Wednesday, October 30, 2013 1:16:02 PM UTC-4, Lee Hambley wrote: >>>> >>>> Any idea where the 49m is coming from? >>>> On 30 Oct 2013 15:57, "Gary Leydon" <[email protected]> wrote: >>>> >>>>> Hi, >>>>> I can' t figure out what the issue is when "cap local deploy" fails >>>>> at the step where it is pruning back the releases directory so that there >>>>> are only 3 versions kept. I can succesfully deploy 3 times but at the 4th >>>>> deploy I get the following in my terminal >>>>> >>>>> INFO [71e52a9b] Running rm -rf /path/to/my/releases/**20131030144117 >>>>> on my.development.system >>>>> DEBUG [71e52a9b] Command: ( RAILS_ENV=local rm -rf >>>>> /path/to/my/releases/**20131030144117 ) >>>>> DEBUG [71e52a9b] bash: 49m: command not found >>>>> >>>>> >>>>> in my local.rb config I've got >>>>> set :stage, :local >>>>> set :rails_env, 'local' >>>>> set :deploy_to , '/path/to/my' >>>>> set :bundle_flags, '--deployment' >>>>> >>>>> >>>>> # Simple Role Syntax >>>>> # ================== >>>>> # Supports bulk-adding hosts to roles, the primary >>>>> # server in each group is considered to be the first >>>>> # unless any hosts have the primary property set. >>>>> role :app, %w{[email protected]} >>>>> role :web, %w{[email protected]} >>>>> role :db, %w{[email protected]} >>>>> >>>>> >>>>> Tool versions: >>>>> >>>>> Capistrano Version: 3.0.0 (Rake Version: 10.1.0) >>>>> Rails 4.0.0 >>>>> ruby 2.0.0p195 (2013-05-14 revision 40734) [x86_64-darwin11.4.2] >>>>> rvm 1.20.10 (stable) >>>>> >>>>> The system I'm deploying to is the same one I'm developing on, public >>>>> keys are set up, what's odd is that I can do the following successfuly >>>>> from >>>>> the command line >>>>> >>>>> ssh [email protected] "RAILS_ENV=local " rm -rf >>>>> /path/to/my/releases/**20131030144117" and it successfully deletes >>>>> the directory (does not prompt for password so keys are working) so it >>>>> doesn't seem to be a permissions issue >>>>> >>>>> I can successfuly deploy the same app to another physical server at >>>>> another IP and it works fine, prunes directories once releases > 3 >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> -- >>>>> * 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 >>>>> capistrano+...@googlegroups.**com For more options, visit this group >>>>> at >>>>> http://groups.google.com/**group/capistrano?hl=en<http://groups.google.com/group/capistrano?hl=en> >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Capistrano" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to capistrano+...@googlegroups.**com. >>>>> For more options, visit >>>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>>> . >>>>> >>>> -- >> -- >> * You received this message because you are subscribed to the Google >> Groups "Capistrano" group. >> * To post to this group, send email to [email protected]<javascript:> >> * To unsubscribe from this group, send email to >> [email protected] <javascript:> 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 unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > -- -- * 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
