aljaz/disobey.dev
1
0
Fork 0
mirror of https://github.com/aljazceru/disobey.dev.git synced 2026-01-07 09:24:38 +01:00
Code Issues Packages Projects Releases Wiki Activity

fixing ai crap

Browse Source
This commit is contained in:
Aljaz Ceru
2025-11-06 12:00:29 +01:00
parent 365f07245b
commit 7d1ff194d9
10 changed files with 223 additions and 74 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
content/posts/github-no-more.md
View File

@@ -5,10 +5,8 @@ slug: "github-no-more"
draft: false
---
The author discusses concerns about GitHub representing a critical infrastructure vulnerability. While repositories exist across multiple machines, they lack proper organization, making recovery time-consuming.
Github is the thing we all love to hate and tend not to get rid of because its just too damn useful. But it dawned on me that its also one of the biggest single point in all of my infrasturcture, sure the repositories exist on multiple machines and I probably wouldn't lose any/much data in the end, but its far from organized nicely and I would spend a lot of time actually putting things together. So I finally decided to create a mirror of all my github stuff to a private gitea. I have a sizable storage server with RAID10 that is used for variety of data heavy loads, mirroring all my (turns out fairly numerous) github organisations and repositories seemed to be one of those.
To mitigate this risk, the author created a private Gitea mirror of all GitHub repositories. Using the tool "mirror-to-gitea," they successfully mirrored over 300 repositories across multiple organizations without manual configuration.
I found [mirror-to-gitea](https://github.com/jaedle/mirror-to-gitea?ref=disobey.dev) which saved a lot of manual clicking (it would take me forever to manually add 300+ repos that I have across multiple organizations). While this doesn't remove my use of github for now it at least makes sure I have a live mirror of everything in case anything happens to it.
Beyond personal repositories, the author maintains mirrors of third-party projects for preservation and OSINT purposes. These are currently stored separately but could potentially be integrated into Gitea, though this would significantly increase deployment size—potentially to tens of thousands of repositories.
The author acknowledges this approach doesn't eliminate GitHub dependency but ensures a comprehensive backup exists. They describe the solution as providing security through redundancy while maintaining the practical utility GitHub currently offers.
Independently of that I have mirrors of a lot of repositories from other projects that are not mine but are used either in my preservation efforts or github osint efforts, but those are outside of gitea as they were all created programmatically. I might need to rethink this approach tho as having a live mirror exposed through gitea might be beneficial. But it will also make the gitea deployment a lot bigger - the repositories are in 10s of thousands.