4 ms·
> I imagine there's a way to setup a hook on your own server such that any pushes are then pushed to a GitHub copy without you having to do anything else yourse
by nicce 1y ago
> I imagine there's a way to setup a hook on your own server such that any pushes are then pushed to a GitHub copy without you having to do anything else yourself.
For most people, that would defeat the purpose of self-hosting.
- simonw 1y agoIf your purpose for self-hosting is fear that GitHub will ignore their own promises in their terms of service and abuse their custody of your data then sure. https://docs.github.com/en/site-policy/github-terms/github-terms-of-service#e-private-repositories https://docs.github.com/en/site-policy/github-terms/github-t... (There's also the "to comply with our legal obligations" bit, which is a concern if you're doing things that governments around the world may have issue with.) I expect there are people who like to self-host so that they're not dependent on GitHub up-time or having their accounts banned and losing access to their data. For them, having a secondary GitHub backup should still be useful.
- lionkor 1y agoThat's not accurate. I've had one of my own accounts blocked, with zero access until I talked to their support and convinced them I was, in fact, a real person. At that moment, if I had any important private repos, they would be gone.
- simonw 1y agoThat's no reason not to use them as a third offsite backup on top of your laptop and your own server hosting, which is what I'm suggesting here.
- deleted 1y ago[deleted]
- nicce 1y ago> If your purpose for self-hosting is fear that GitHub will ignore their own promises in their terms of service and abuse their custody of your data then sure. None of that protects against the U.S. laws or current political climate. There is no guarantee for EU citizen that GitHub processes data only in EU area or that data ever leaves it. So it is all about the data privacy.