On Wed, Jan 28, 2009 at 8:43 PM, Greg Hauptmann < [email protected]> wrote:
> > thanks - Can I ask if it easy enough to set up my own central GitHub > server? (like I do wiht svn) Yes. Very much so. c) source backup <== which I'm talking about here I don't worry about that. The main property you have to remember is that EVERY checkout of Git is a full repository. At least one, probably several, of the Capistrano strategies using Git will leave a checkout on the server -- at least one. That means you have a remote repository, in that sense -- you can always pull the latest deployed code from your webserver. Probably not a best practice, but trivially easy. Or, just set up another user account, and push there. It's about two commands to do that. Backup, well, if you do either of the above, you will always have at least two full copies -- the server, and your checkout. There's also always Github, though I'm not sure what the value is for a one-man, private project. If it's open source, though, it's a great way to lower the barrier of entry -- one click for anyone with a Github account to fork it and start hacking. --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
