Personal ATProto PDS implementation optimised for NixOS/Caddy, with no Bluesky infrastructure defaults.
A Dockerised Tangled knot server with optional Cloudflare Tunnel routing.
A personal PaperMC Minecraft server in Docker Compose with DuckDNS dynamic DNS and management scripts.
A Bash script for automated, resumable PDS backups via rsync over SSH with change detection and cron scheduling.
Considering how the user benefits when a mature project goes fully open-source—even one with the baggage of something like Gumroad.
Self-hosted apps are having a moment, but people are still a little freaked out by them. Could a Flatpak-style approach to self-hosting help matters?
What I learned about trying to run my own cloud from a few weeks of trying to run the whole dang thing myself. (Hint: I found myself trying multiple solutions.)
I recently decided to start using my own home server to store my dotfiles. The main reasons are simplicity, privacy, and security. I previously stored them in a repository on my GitHub account and installed them with Ansible, but I have increasingly found it cumbersome when trying to keep them updated and in sync. On GitHub, the changes (and mistakes!) I make to my dotfiles are publicly viewable; sometimes I'll make changes several times a day, sometimes scrapping a change entirely when I later realize it was not such a good idea or breaks something in my activity flow. I also would love the convenience of keeping SSH keys and GPG keychains in sync and updated, and storing them on a public server is obviously not an option, nor even in a private repository hosted on GitHub or GitLab.