Migrating Hg to ... IDK ... codeberg/sr.ht?
Shugits is dead - I just don’t have the time. Here’s what I’m doing instead to keep using Mercurial in an increasingly git world.
… hopefully I don’t prove myself wrong 24 hours after posting this …
Every few years I try to “swtich to git” and hit some issue after a week. Git’s just harder to use, and, requires more of the human’s memory and attention.
So.
I’ve put aside my all-singing-all-dancing hg+git layer, and, I’m now … mirroring hg, to git, and using free hosting for both. Here’s how I got there.
Self Hosting?
I assessed several self-hosted solutions … and didn;t like any of them.
| solution | issue |
|---|---|
| hgkeeper | missing the ci/issues and general completeness |
| hglab | missing just about everything |
| it’s a webdev project | |
| heptapod | ungainly, frequently crashes |
| probably fine for corpo use | |
| throws too much crap on screen at once | |
| phabricator | again - too much work for one admin |
| kalithea | no CI |
| source.hut | too complext to get through docs - again |
Best of Both Worlds
My current solution goes like this …
- i ahve a sr.ht accountl i put my hg repos there
- i have a codeberg account; i put my git repos, and git mirrors there
- i have a rasperry pi, it …
- checks/updates a list of projects to poll/check
- hg clone/pull a few of them every 15 mintes from sr.ht
- hg-git push’s them to codeberg
… and that’s it.
There.
Why not just codeberg? No Mercurial
Why not just sr.ht? No … well no per-repo Issues, and, the CI needs a credit card.
… I could give them money … I just won’t get around to it …
Future?
Spood/Spooder is the script I use to do this synch. It’s simple so don’t get excited. I’d like to implement …
- web-hooks to trigger it when sr.ht sees changes
- import git commits and push them back upstream
- an SSH proxy that defers to codeberg’s key records
… but that’s basically all of shugits again … so why worry?