Wow, since I last posted, I purchased and upgraded my OS to Leopard. I ran a cap deploy at 7:22pm (actual time on my mac), it still made a release folder five hours in the future (at 00:22), only this time no errors. So weird. Any post postmortem thoughts?
Thanks for asking Jamis. On Jul 19, 10:41 am, Jamis Buck <[EMAIL PROTECTED]> wrote: > The timestamp is always in UTC, as determined by the clock on your > local machine. Capistrano shouldn't care about that being the future > though--what is the exact error you're getting? Can you paste the full > output? > > - Jamis > > On Jul 19, 2008, at 9:38 AM, Riley wrote: > > > > > Hi Guys, > > > I was wondering if anyone know how capistrano determines the timestamp > > on the release folder (/tmp/YYYYMMDDHHMMSS). When I run cap deploy, I > > get an TON of errors about how the time is in the future, and then it > > rolls back to the version currently live on my site. > > > FYI, the timezones on my server and repository were wrong, and I have > > since changed those to match my timezone. But Capistrano still creates > > the release folder 5 hours in the future and I still get the errors. > > > Thanks in advance! --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
