One more thing, my repositories are usually quite small. My virtualenv and static file directories are in my .gitignore, so they're never included. So cloning an entire repo isn't a big deal and disk space itself is very rarely a problem (and when it is, it's not down to the size of the repo).
On Monday, 3 September 2012 11:19:55 UTC+1, Matt Stevens wrote: > > Hi Mike, > > I think this is a matter of preference. I've always cloned the entire > repository - new features can go live by simply checking out a new branch, > if something goes wrong I can just checkout the (stable) master branch > again. I can also see if any boxes are out of sync with the current > codebase with git diff. Having this all wrapped up in fabric tasks makes > everything tidy and painless to deal with. > > > I've never had any security issues with this, if I had a compromise I > would just drop the SSH key of the compromised box from my central Git > server (Github in my case) and restore the repo from my daily backups. If > this is more of an issue for you though then something like Gitosis would > help. > > > Cheers, > Matt Stevens | http://www.dirtymonkey.co.uk > > On Sunday, 2 September 2012 06:07:03 UTC+1, Mike wrote: >> >> I just started to use Fabric to automate my deployments to my staging >> server. (and when I'm ready, to the production server as well). I have >> just a few questions for more experienced folks: >> >> Do you clone your whole git repository onto your server, or upload a new >> archive each time you release? Seems like it would be easier to switch >> versions of the running code, by switching tags, but it would use up a lot >> more disk space. I'd also have to have an ssh key to the central git >> repository on the web server. Sounds like that could be a security issue. >> At the moment I'm programming Fabric to upload an archive, untar it, and >> symlink it to a fixed directory where the web server expects it to be. >> >> Do you log out all users or just reset the sessions (manage.py reset >> sessions)? >> >> thanks! >> > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/hKfhrtiD8NcJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
