4 ms·
All you need to run a 'personal git server' is sshd and a user. If you plan to have many others to use it, then it's not really personal, is it? > Even though
by xaduha 6y ago
All you need to run a 'personal git server' is sshd and a user. If you plan to have many others to use it, then it's not really personal, is it?
> Even though we've turned off password based authentication in a previous section, we will still receive a significant amount of bots wasting our compute cycles trying to login.
I think that's proven to be false.
- nanidin 6y agoI also came to chime in with this. I have been running a "personal git server" this way for almost a decade. On the server: cd ~ mkdir directoryname.git cd directoryname.git git init --bare On the client(s): git clone username@server:directoryname.git That's all there is to it!
- shuntress 6y ago>All you need to run a 'personal git server' is sshd To expand on this slightly: making your "personal" git server accessible to collaborators (without needing to manage user accounts user accounts) is also very simple. You can statically serve your repository using any web server. Collaboration is then based on each contributor pushing (ssh) to their personal server from which everyone else may pull (http).
- pokstad 6y agorsync.net is great for this: https://blog.kozubik.com/john_kozubik/2010/02/git-and-subversion-support-at-rsyncnet.html https://blog.kozubik.com/john_kozubik/2010/02/git-and-subver...
- anderspitman 6y agoI dream of the day when the internet is decentralized again (either by ipv6 or tunnel proxies[0]) and we can just push/pull directly to each other. [0]: https://github.com/anderspitman/awesome-tunneling https://github.com/anderspitman/awesome-tunneling