←back to thread

160 points MattIPv4 | 1 comments | | HN request time: 0.238s | source
Show context
retrocryptid ◴[] No.36407521[source]
I'm currently hosting a git repo on my home machine and it's used by me when I'm on the road and a few people I trust enough to have logins on my DMZ machine.

It seems there should be an easy way to use gitlab or github as a public read-only proxy to changes that are released on the private repo. And then going the other way, sucks up PRs from public sites and lovingly integrates them into the "real" repo on my home machine.

Yes. There are security ramifications. There are availability ramifications. I seems slightly to be trying to skirt GitLab's policies they're probably putting into effect to avoid going bankrupt. But the flip-side is I really don't need a wiki or a bug tracker or whatever else GitLab is working on. I would pay a small amount of cash to just get a public repo mirror.

And we all have different ideas about how to make this "easy". I don't mind running scripts on my local host, but would like to avoid polling the public repo to see if someone's posted a PR. I also don't want to have to run a script in a container on the public repo. So would love it if you could set the public repo to proxy PRs to a remote repo.

Just curious if anyone else has similar requirements. Maybe you have a corporate repo and want to mirror it to a public site like GitLab, GitHub or SourceHut. Maybe, like me, *you* just want a remote repo to stash your code but a public location so your home server doesn't melt down that one time someone slashdots your project.

replies(4): >>36407548 #>>36407593 #>>36407705 #>>36411120 #
eddythompson80 ◴[] No.36407705[source]
It’s not that hard to setup. It’s a built-in feature in something like gitea. Or you can write a `git push` cron task or a server hook in git to keep the 2 in sync. GitHub is full of mirror repos. You can also disable issues, discussions, wiki, and pull requests if you don’t want to deal with that.
replies(2): >>36407851 #>>36408320 #
retrocryptid ◴[] No.36407851[source]
That's what I'm doing now. It's what I don't want to do. I want the public repo to autopush PRs to my private repo so I don't have to poll it.

[LOL. A previous edit autocorrected "autopush" to "autopsy." Or maybe it was a Freudian slip on my part.]

replies(1): >>36407881 #
eddythompson80 ◴[] No.36407881[source]
You can trigger a GitHub action on any PR and run any arbitrary code you want.
replies(1): >>36408576 #
retrocryptid ◴[] No.36408576[source]
Again. I DON'T want to run a script in a container on github's infrastructure.
replies(2): >>36410732 #>>36411762 #
1. eddythompson80 ◴[] No.36410732[source]
If you’re polling, you can use GitHub APIs. They are pretty well documented. If you want a turn-key solution, use gitea. Depending on how flexible you need it, gitea might cover your scenarios. But you can have actions in gitea as well that automate polling GitHub APIs for issues or comments or pull requests etc.