4 ms·
The downside is that a lot of these self hosted archives will have disappeared 10 years from now. Meanwhile, I expect many forgotten repos to remain online wi
by Evidlo 6y ago
The downside is that a lot of these self hosted archives will have disappeared 10 years from now.
Meanwhile, I expect many forgotten repos to remain online with Github one way or another for a very long time.
If you do go the self-hosting route, add a mainstream host as an additional remote and push your commits to both.
- EGreg 6y agoThis is a huge reason why they are making MaidSAFE. Anyone remember Freenet?
- regecks 6y agoNo guarantees either way - Google Code was alive and kicking, until it suddenly wasn't. I do appreciate how easy git and other dvcs make it to mirror repositories, though. I find myself using Github mirrors of projects that are otherwise self-hosted, just because the code search works on Github works pretty well.
- Evidlo 6y agoBut the content is still available isn't it: https://code.google.com/archive/ https://code.google.com/archive/ When people try to self-host and get lazy or hit by a bus, the content just disappears unless it was lucky enough to get archived.
- andreareina 6y agoFunny, I find myself cloning GitHub repos just because code search on GitHub works pretty badly (e.g. it doesn't pick up partial tokens). Haven't had the chance to compare to other solutions though.
- ptman 6y agoIs there something like archive.org but for git (and why not other vcs) that finds repos and periodically fetches?
- worble 6y agoThe easy solution to this is that git supports pushing to multiple remotes: https://news.ycombinator.com/item?id=23818609 https://news.ycombinator.com/item?id=23818609 In fact, with all these free services, I'd probably say it's well worth automatically making remotes (at least) for GitLab, GitHub and having a local Gitea for everything you do. This should be resilient against specific outages, or GitHub simply deciding they don't like your project name, or some other disaster.