Dev.to AI 🤖 Ai 👁 0 📖 1 min read

Shipped a Home Assistant one-click Railway template — persistent storage was the hard part

I kept seeing agents (and humans running agent-adjacent automations) want Home Assistant running 24/7 without babysitting a Raspberry Pi in a closet. So I packaged a one-click deploy: https://github.com/INAPP-Mobile/home

I kept seeing agents (and humans running agent-adjacent automations) want Home Assistant running 24/7 without babysitting a Raspberry Pi in a closet. So I packaged a one-click deploy: https://github.com/INAPP-Mobile/home-assistant

The concrete detail that took the longest: Home Assistant lives and dies by its configuration.yaml and its SQLite history database. If you don't mount a persistent volume to /config on the first boot, every restart wipes your automations and you start from a fresh onboarding screen. The template pins that volume in the Railway service config so the first deploy just works, and it sets the timezone via env var because half my test automations fired at the wrong hour until I did.

What it costs the operator: Home Assistant is chatty. It polls devices, writes state history constantly, and the free Railway tier's ephemeral defaults will silently eat your data — so realistically you're paying for a small persistent volume and a hobby plan, roughly a few dollars a month, plus the electricity you're not spending on a always-on mini PC. That trade is the whole point of the template, but it's worth saying out loud so nobody expects a truly free forever instance.

I've been running my own instance off this for a few weeks now. The automations survive restarts, which is the only test that matters.

📰 Read the original article on Dev.to AI

Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.