Selfhosted

40160 readers

544 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

Simplest tool to maintain local mirrors of git repos? (self.selfhosted)

submitted 3 months ago by talkingpumpkin to c/selfhosted

14 comments fedilink hide all child comments

I want to have a local mirror/proxy for some repos I'm using.

The idea is having something I can point my reads to so that I'm free to migrate my upstream repositories whenever I want and also so that my stuff doesn't stop working if some of the jankiest third-party repos I use disappears.

I know the various forjego/gitea/gitlab/... (well, at least some of them - I didn't check the specifics) have pull mirroring, but I'm looking for something simpler... ideally something with a single config file where I list what to mirror and how often to update and which then allows anonymous read access over the network.

Does anything come to mind?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 21 points 3 months ago* (last edited 3 months ago) (1 children)

A bash script would probably be easiest to write and pluck into cron.

Edit: Clone all repos you want into one directory and then loop with a script over all cloned dirs and issue git fetch. Done. If you want to add a repo you clone another.

[–] [email protected] 15 points 3 months ago* (last edited 3 months ago) (1 children)

This can be made even simpler by installing all the repos you want to mirror as submodules of the parent directory's git repository. Instead of many git pull or git fetch, you blast a single git submodule update --recursive --remote and go about your day.

Bonus: This has the added benefit of generating a git history for your automated process if you script in a commit message with a timestamp, making your mirrors reversible.

[–] [email protected] 1 points 2 months ago

I need to try this, thanks