Welcome to Jimbo's Files
A personal self-hosted infrastructure hub running on NixOS. This is where I tinker with open-source tools, host my own services, and share what I learn along the way. Everything here is licensed under GPL-3.0 — free to inspect, fork, and adapt.
The stack includes Nextcloud for file storage, Vaultwarden for password management, and Forgejo for collaborative code hosting. Plus a handful of experimental social and media services.
Running a self-hosted infrastructure on NixOS means embracing reproducibility and declarative configuration. Every service, from file storage to password management, is defined in code that can be versioned, shared, and rebuilt at any time. This approach eliminates the drift that plagues manually configured servers and makes it possible to replicate the entire stack on new hardware with a single command. The configuration files live alongside the services they describe, creating a living document of how everything fits together under one roof.
Nextcloud sits at the heart of the file server setup, offering a familiar interface for storing and sharing documents, photos, and media. It replaces reliance on third-party cloud providers by keeping everything on hardware you control. Calendar syncing, contact management, and collaborative document editing all run through the same platform, making it a versatile hub for both personal organization and group projects without ever handing data over to someone else’s data center.
Password management becomes straightforward and private with Vaultwarden, a lightweight implementation of the Bitwarden API that runs comfortably on modest hardware. It handles secure credential storage, generates strong passwords, and syncs across browsers and mobile devices through end-to-end encryption. Self-hosting a password manager means the encrypted vault never leaves infrastructure you trust, while still providing the convenience of autofill and cross-device access that modern workflows demand.
Forgejo provides a collaborative code hosting environment under a free software license, making it ideal for personal projects and small team development. It supports Git repositories, issue tracking, pull requests, and continuous integration pipelines without depending on proprietary platforms. Hosting your own code forge means complete control over data, custom workflows, and the freedom to tinker with the platform itself, all while maintaining compatibility with standard Git tooling and federation protocols.
Media streaming and internet radio production round out the creative side of the server stack. Whether broadcasting live audio, curating playlists, or experimenting with streaming formats, self-hosted tools open up possibilities that commercial platforms often restrict. Running these services locally means no algorithmic interference, no content takedowns, and the ability to fine-tune every aspect of the signal chain from source to listener.
The social web finds a home here through federated platforms that connect without central gatekeepers. Mastodon offers microblogging that feels familiar yet independent, while Lemmy provides link aggregation and discussion threads on a community-owned model. Pixelfed brings photo sharing into the same decentralized ecosystem. Each service talks to the wider fediverse, so users can interact across platforms without being locked into any single provider’s terms or timeline algorithms.
Behind the scenes, internal mail handling and system monitoring keep everything running smoothly. Self-hosted email infrastructure handles notifications, alerts, and administrative messages without routing sensitive communications through external services. Combined with logging dashboards and health checks, this layer ensures that when something needs attention, the right people hear about it quickly and through channels that remain entirely under local control.
Everything shared on this hub carries a GPL-3.0 license, reflecting a commitment to free and open-source principles. Configuration snippets, service templates, and deployment notes are published so others can study, modify, and adapt them for their own setups. The goal is not just to run a personal server but to contribute back to the broader community of self-hosters and tinkerers who believe that infrastructure should be transparent, inspectable, and owned by the people who use it.