Hosting git repositories on your VPS
http://blog.heapsource.com/post/54107424584/hosting-git-repositories-on-your-vps
Today I’ll show you how to setup a gitolite installation on a VPS with Ubuntu 12.04 LTS. To save myself some typing I’ll be using the following conventions:A command prefixed by sysadmin$ is meant to be run in your local workstation.
A command prefixed by user@vpshost:path# is meant to be run in the vps under the specified user on the specified path.
(
22 comments
| 45 points
| on HN
)
[1]: http://www.petekeen.com/hosting-private-git-repositories-wit...
[2]: https://news.ycombinator.com/item?id=4707747
IMO there is no reason to use gitolite now for unless you have (a) sensitive repos (with your own server, not a VPS of course), or (b) lots of private repos with lots of collaborators and you have no money for a Github or Bitbucket monthly fee and you aren't a non-profit (I think non-profits can get a free Bitbucket account).
That said, I'm interested to hear about other gitolite use cases I haven't thought of.
(Not affiliated with Atlassian/Bitbucket in any way - but I love their software)
We ended up installing Stash as it seemed that it would reduce administration+maintenance by a tad bit (GUI + knowledgebase) and would be supported by a company responsible for bitbucket. Stash has been a pleasant experience so far.
Alternatively, you could just encrypt the directory that you push to remotely (probably /home/git in this tutorial), which seems like a cleaner solution: https://help.ubuntu.com/13.04/serverguide/ecryptfs.html
Was it super easy to understand & set-up?
Additionally, either you have some strange prompts set up somewhere, or made a few typos when copying and pasting; a couple of places you appear to be logged in as a someuser@<...>, but with a hash-prompt(#) -- usually reserved for indicating root/super user access.
edit: Personally, I actually found the official documentation more helpful, even if it is very brief:
http://gitolite.com/gitolite/qi.html
In particular, it highlights that gitolite needs to run under a user, and needs a (your, the admin's) pubkey for setup -- but there's no need to generate a new one.
Behind the scenes, the pubkey used is added to the gitolite user's authorized_keys-file (and so is any other keys added, when users are added).
I've used it for a year and I've been quite happy with it.
[1]: http://www.scm-manager.org/
https://wiki.archlinux.org/index.php/Gitosis
I've had some pushback on both of them from users because the command line fu necessary to use both of these projects is apparently just enough of a barrier that even developers find it annoying.
Gitlab is a bigger pain to administer and more resource-intensive, but much easier for users.