I'm really not sure what's going on there. Have you checked to make sure that you've got enough disk space? Might there be a process running periodically that cleans out the tmp directory on that server? You might check the cron log and system logs to see if anything is showing up around the time you do a deploy.
Regardless, I've just committed a tweak to capistrano, which adds a new variable (:copy_remote_dir) that the copy strategy will use to indicate where the archive should be copied to. It defaults to "/tmp", but you could use it like this: set :copy_remote_dir, deploy_to That would then cause the archive to be copied to your deployment directory, instead of /tmp. Regardless of the location, the copy strategy will delete the archive when it is done with it, so you don't have to worry about littering your file system. - Jamis On 6/20/07, gcnovus <[EMAIL PROTECTED]> wrote: > > CentOS, I believe. I'm not sure of the version. > > -Gaius > > On Jun 12, 11:23 am, Jamis Buck <[EMAIL PROTECTED]> wrote: > > What OS are you deploying to? > > > > - Jamis > > > > On Jun 10, 2007, at 12:22 PM, gcnovus wrote: > > > > > > > > > FWIW, doing the process manually: > > > > > svn exporthttp://repository20070610183345 > > > tar -czvf 20070610183345.tar.gz 20070610183345/ > > > scp 20070610183345.tar.gz [EMAIL PROTECTED]:/tmp/ > > > > > works fine, but it does yield the warning "stdin: is not a tty" even > > > though the copy does work. > > > > > I have a feeling the cap deploy version is having a problem when the > > > export is large (over a few Mib); the deploy has worked many times > > > when the total .tar.gz file size is under a meg. > > > > > -Gaius > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
