Versioning
Planned self-hosted Git and Epic Games' Lore stack — moving creative projects off SaaS with room for game-scale binaries and full pipeline control.
Self-hosted versioning is still in the very early stages of planning and design — but it will play an important personal role as I want to move away from other people's services and the world becomes a more hostile place for international connectivity.
Many pieces of this picture already run today — Git, documentation, ticketing — but not yet as one connected stack, and much of it is not on my own hardware yet. The main challenge ahead is the homelab itself: choosing the hardware, tying everything together, and hosting it at home.
The goal is to move my projects from GitLab (and elsewhere) onto infrastructure I control, so every creative repo lives on my own terms. It is more ambitious than a lone Git server: because we make games, I am also looking at a Lore repository — Epic games’ open-source, Git-adjacent versioning stack for non-text assets. That matters in game dev, where 3D models and textures often outweigh code by orders of magnitude.
In our world where allies do not always play nice with each other anymore; reducing dependencies is not a bad idea. Hosting at home, at my own cost, also avoids paying for extra space or subscriptions. Most code repos stay modest in size — games do not. Unoptimised textures and models during development can climb to many gigabytes quickly.
Additional info
Highlights
- Self-hosted Git plus Epic Games' Lore — code repos and game-scale binary assets under one roof.
- Full stack on own hardware: Obsidian for docs, OpenProject ticketing, custom bridges.
- Encrypted Proton backups — weekly incremental when changed, monthly full, long-term retention.
I am still designing how the homelab hardware and software fit together. Some decisions are settled: separate Git and Lore systems. Git for normal projects; Lore for larger, asset-heavy work.
I also want the full production lifecycle on my own environment — versioning and documentation through pipelines and ticketing. For docs, instead of something like Confluence, we will use Obsidian paired with Git: a version-controlled encyclopedia that runs on most devices. For ticketing and work tracking, OpenProject instead of Jira — it can integrate with GitLab-style workflows. Custom bridges will tie what off-the-shelf tools cannot.
No serious storage plan is complete without backups. I am not running a data centre from home, nor do I have the space — but I do intend frequent backups. When changes land in a given week, that week gets a backup: changed files only, zipped and encrypted, uploaded to a privacy-focused cloud — Proton Drive, which now has a CLI that makes scripted uploads reasonable.
Once a month, a full backup runs. After two years, monthly archives roll off except December each year — enough history to survive a house fire taking out the homelab, without hoarding every byte forever.