the brain of my home: a deep dive into my homelab 2026.md ..
@@ 72,23 72,23 @@
I am not just hosting apps; I am building them. My development workflow is designed to be seamless.
1. **Code**: I write code locally in VS Code, Antigravity or connect directly via **Remote SSH** to my development VM.
-
2. **Build**: I define the environment in a `Dockerfile` so it matches production exactly.
+
2. **Build**: I define the environment in a `Dockerfile` so it matches production exactly. If it is prebuild then a simple `compose.yml` file
3. **Deploy**: A simple `docker compose up -d` brings the service to life. Traefik spots the new container, grabs an SSL certificate, and boom—it's live.
## Service Spotlight: What's Running?
So, what is all this hardware actually doing? Here are a few highlights:
-
* **Productivity**: **Obsidian** acts as my personal knowledge base.
-
* **Media**: **Jellyfin** serves up movies and music.
-
* **Monitoring**: **Beszel** and **Pulse** and **Uptime Kuma** keep an eye on system health, letting me know if a drive is filling up or a container has crashed or a system is down.
+
* **Productivity**: **Gitea** acts as my personal knowledge base and code control
+
* **Family Uses**: **Mealie** For Menus and shopping list **Wallos** Bill paying
+
* **Media**: **Jellyfin** serves up movies and music. **Piwigo** Photos
+
* **Monitoring**: **Beszel** and **Pulse** and **Uptime Kuma** and **Dozzle* Letting me know if all is good on the systems and containers health.
* **Custom Dev**: I run several custom apps, including a Grocery Tracker and a retro-styled monitoring dashboard called **NeoStatus**.
## Future Goals
A homelab is never "finished." Here is what is on my radar:
-
* **cluster High Availability**: Setting up a true Proxmox cluster for automatic failover.
* **Offsite Backup**: Pushing critical encrypted backups to a remote location.
* **More Automation**: Writing Ansible playbooks to automate the initial server provisioning.
