Sorry, I misread your original message. I thought you were trying to replace the current symlink; and in general, if you need to muck with the core assumptions that much, it's easier to just write your own.
I see that you were just wanting to do something after the push of the site. The before() hook you mentioned is one way, but it sounds like, even more what you want, is to just structure your repository such that everything is already in the right directory structure. Otherwise, yeah, you're looking at some shell scripting, like a for loop that skips 'www' and moves everything else to www. - Jamis On 3/5/09 12:40 PM, matt mitchell wrote: > Interesting. I'll definitely consider that. The solution I just came > up with involves using: grep -v www > > I'm curious about why you're strongly recommending against using the > defaults? There must be something bigger I'm not thinking about... > > Matt > > On Mar 5, 2:36 pm, Jamis Buck <[email protected]> wrote: >> I would strongly recommend that you not use the standard deploy tasks, >> and just write your own. >> >> - Jamis >> >> On 3/5/09 12:16 PM, goodieboy wrote: >> >>> Hi, >>> I have a repo that's a simple static site. The trunk is the websites >>> document root. I need to deploy this site to a server that has current/ >>> www as its document root, where "current" is the directory created by >>> capistrano. I'm trying to figure out the best way to: >>> create a www directory after deploy >>> move all of the files (except for "www") into "www" >>> That just seems weird though. >>> Is there are way to specify something like: >>> before 'deploy:update_code', 'create_www_and_set_current_path_to_www' >>> ? >>> Thanks for any insight on how this can be accomplished. >>> Matt >> > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
