4 ms·
I use GitHub, but only as a mirror for the repositories I have on infrastructure under my own control. It's still very easy for others to contribute, even to se
by gsliepen 3y ago
I use GitHub, but only as a mirror for the repositories I have on infrastructure under my own control. It's still very easy for others to contribute, even to send pull requests via GitHub, while I merge them locally and push them to my primary and mirror repositories. GitHub detects that PRs are merged, even if you do not use their UI, which is very nice.
Note that you can do this for more online services; you can have GitHub, GitLab, SourceHut and other sites all as mirrors for your self-hosted repositories. It's the best of all worlds in my opinion, and enlarges your pool of potential contributors.
Of course, you have to avoid vendor lock-in that can happen if you rely too much on other services that GitHub provides, like the issue tracker, wiki, CI and so on.
- donmcronald 3y agoWhich side do you use as the primary? I use Gitea and push mirror to GitHub, but I’m not sure how that would work for collaboration. I only push to GitHub for projects that deploy to Cloudflare (via Pages). I’ve stubbornly struggled through self hosting all my stuff while everyone was saying it was a waste of time. There was a stretch where I was starting to believe it, but now I’m starting to feel more vindicated. It’s different for large companies, but I think smaller developers benefit from the control you get from self hosting everything possible.
- gsliepen 3y agoI use my own git servers as primary. Just a webserver serving the git directory read-only, and I push via SSH to it. You can slap a UI on top, from something simple like gitweb to whatever you want.