Settings down to eight tabs; Domains become a tab of DNS

Notifications gains Alert tickets, Display gains Badge colours, and a new Data tab holds Backup,
Logs and Cache. Domains is the 'Domain names' tab of DNS. Old addresses redirect; the docs, the
Privacy page and the links from alerts and the agenda name the new places.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
bobbanandClaude Sonnet 5.5 committed 2026-10-19 22:36:24 +02:00
1 parent 1432b148e9
commit ddd0aa622a
23 files changed
+153 -65

No files matched your search

+7 -7
View File
@@ -4,7 +4,7 @@ Everything Homelab Manager knows is in **one SQLite file**, plus a handful of se
`.env`. A backup is those two things — and the part people get wrong is keeping them **apart**
(see [Keeping backups safe](#keeping-backups-safe)).
- [The built-in backups (Settings → Backup)](#the-built-in-backups-settings--backup)
- [The built-in backups (Settings → Data → Backup)](#the-built-in-backups-settings--data--backup)
- [What to back up](#what-to-back-up)
- [Taking a backup](#taking-a-backup)
- [Checking a backup](#checking-a-backup)
@@ -12,19 +12,19 @@ Everything Homelab Manager knows is in **one SQLite file**, plus a handful of se
- [Keeping backups safe](#keeping-backups-safe)
- [Automating it](#automating-it)
- [Restoring](#restoring)
- [The encrypted export in Settings → Backup](#the-encrypted-export-in-settings--backup)
- [The encrypted export in Settings → Data → Backup](#the-encrypted-export-in-settings--data--backup)
- [If there is no backup](#if-there-is-no-backup)
- [What has been tested, and what hasn't](#what-has-been-tested-and-what-hasnt)
The commands assume the standard Docker setup from the README: you run them in the folder that
holds `docker-compose.yml`, `.env` and `data/`, and the service is called `homelab-manager`.
## The built-in backups (Settings → Backup)
## The built-in backups (Settings → Data → Backup)
You don't need the snippets below for the everyday case: Homelab Manager takes a backup of its own
database **every day** (03:30 in the notification time zone, the newest 14 kept — both changeable, and it
can be switched off), checks each one as it makes it, and keeps them in `data/backups/` with the same
names the snippets use. **Settings → Backup** shows them and does the rest:
names the snippets use. **Settings → Data → Backup** shows them and does the rest:
- **Back up now** makes one on the spot. **Download** takes a copy to your computer (the quickest way
off the machine). **Check** opens a backup and says whether SQLite finds it sound, how many users,
@@ -268,9 +268,9 @@ everything stored so far unreadable.
not show the gap, so it is worth noting it somewhere.
- Everyone has to sign in again if you restored without `data/sessions/`. That is expected.
## The encrypted export in Settings → Backup
## The encrypted export in Settings → Data → Backup
A different tool, for a different job. **Settings → Backup** downloads one file, encrypted with a
A different tool, for a different job. **Settings → Data → Backup** downloads one file, encrypted with a
passphrase you choose (AES-256-GCM, key derived with scrypt), holding:
- the settings (notification channels, display, log retention, alert tickets, and so on),
@@ -292,7 +292,7 @@ Keep the passphrase somewhere safe; it can't be recovered.
What you can get back, from least to most work:
- **You have a Settings → Backup export:** a fresh install plus an import restores the settings,
- **You have a Settings → Data → Backup export:** a fresh install plus an import restores the settings,
integrations and DNS providers. Everything else is re-created.
- **You only have the `.env`:** a fresh install with the same file works, and everything in the
database starts empty. Sign in (the first account becomes admin), re-add the integrations,