Hi Lee, Thank you for the thorough response. I think we will upgrade to paid GitHub accounts and host our project there.
I have one question about the deployment group you suggest creating. On my server, on which directories/files should I be setting the group ownership? Will this group not just be overwritten the next time the code is checked out from GitHub? I'm a little hazy on how this setting would persist across deploys. Maybe you can fill me in. Thanks again, Alex On Nov 30, 9:25 am, Lee Hambley <[email protected]> wrote: > Alex, > > Hosting the repository in your home directory is not bad for a single guy, > but in order to collaberate, you need to move it to somewhere shared, as you > mentioned - or, run a git server (starting to get complicated) and deal with > permissions. For the small, small cost involved - I would take a repository > somewhere like Github and collaberate there. > > This solves all your problems about sharing code; (and I throughoughtly > recommend not getting involved in hosting your own multi user repository, if > you're not a competant sysadmin, it can get ugly real quickly) > > With regard to the "deploy" user, I would take the approach of using groups, > and user rights - add yourself, and the designer to a deployment group, and > then chgrp the deploy directories to the group, and set "G+rwx". Then > members of the `deploy` group should be able to write there properly. > > The alternative is a dedicated deploy user, but I don't like that idea so > much. > > -- Lee Hambley > > Twitter: @leehambley | @capistranorb -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
