Why Ilexarium is about safety, not apps
There are many ways to install an app on a home server. Ilexarium is about what comes after.
Why run a server at home at all? That's its own article. This one is about what comes once you've decided.
Installing an app on your own server has never been easier. A Compose file, one command, and it runs. The hard part comes later: the disk that fills up one night, the update that breaks a database, the backup you never tested.
The question that shaped Ilexarium
Every time I SSH into my server, that's a feature the interface is missing.
We kept a list of every reason to open a terminal: a container that stopped, a disk to mount, a log to read, a backup to restore. Ilexarium is that list, turned into an interface.
Safe by default
Ilexarium holds no root of its own. Changes to the machine run as your Linux account (Ilexarium itself may only start and stop containers and remove unused Docker data), and root work goes through your own sudo, unlocked with your password — which Ilexarium never keeps. Backups are Borg archives run by the system on a schedule, whether Ilexarium is running or not.
| What can go wrong | What Ilexarium does |
|---|---|
| An app stops | An alert by email or ntfy |
| A disk fills up | An alert before it's full |
| An update goes wrong | Restore the app from its backup, as it was |
What's next
The guides to HTTPS in front and reaching your server from outside are out. Next come backups to a USB disk and recovering on a new machine. Subscribe to the feed to hear when they're ready.