diff --git a/docs/home-server/authentication.md b/docs/home-server/authentication.md index 1c78c43..4fe25bb 100644 --- a/docs/home-server/authentication.md +++ b/docs/home-server/authentication.md @@ -6,6 +6,8 @@ scope: [jupiter, authentik, oidc, forward-auth, per-user-access, secrets] sensitivity: private-infrastructure last_reviewed: "2026-10-27" sources: + - kind: live-inspection + reference: "PostgreSQL moved to /home/jay/data/authentik/postgres on SSD 2026-10-27; server/worker restored with unchanged image and credentials" - kind: owner-report reference: "Authentik deployed/Authelia retired 2026-10-16; Homarr login 2026-10-18; per-user policy and account linking still unconfirmed 2026-10-26" - kind: repository @@ -28,7 +30,7 @@ unknowns: [deployed-per-user-bindings-and-jay-superuser-membership, per-applicat ## Per-user application access -- All 15 applications bind existing user `jay` at order `0`; `policy_engine_mode: any`. +- All 16 applications bind existing user `jay` at order `0`; `policy_engine_mode: any`. - Add others under **Policy / Group / User Bindings**: enabled, non-negated **User** binding, order `10+`. Unassigned users are denied; manual higher-order bindings survive reapplication. - Blueprint replaces custom `admins`, `development`, `clients` groups; does not create users or change passwords/MFA/app-native roles. - **Keep Jay in the built-in superuser group** (`authentik Admins`); application admission is not administration. @@ -77,6 +79,28 @@ unknowns: [deployed-per-user-bindings-and-jay-superuser-membership, per-applicat - Credential fallback bypasses Authentik MFA/access policy for password logins. - Internal `docker-api` proxy: only proxy mounts socket; no published API/Traefik attachment; inventory/logs allowed, `POST=0`, lifecycle controls disabled. Redeploy the whole stack. +## Native SAML: Joplin + +- Repository configuration: `https://notes.umbra.mom`, Authentik application + `joplin`, shared MFA authorization flow and per-user admission. +- Signed assertions and responses; required attributes `email` and `displayName`. +- ACS: `https://notes.umbra.mom/api/saml`; entity ID/audience: + `https://notes.umbra.mom`. +- Joplin reads `/data/joplin/saml/{sp.xml,idp.xml}` through a read-only bind. + Copy the SP file from `stacks/joplin/saml/sp.xml`; download IdP metadata from + `https://auth.umbra.mom/application/saml/joplin/metadata/` after applying the + blueprint. Refresh the metadata after signing-certificate rotation. +- Clients use **Joplin Server (SAML)**, not the password-based sync target. + No forward-auth on the API. Local password login is disabled by default. +- First SAML login creates a non-admin Joplin account. Existing password accounts + with the same email are not automatically linked; preserve their data and + plan migration before switching. +- Temporary `JOPLIN_LOCAL_AUTH_ENABLED=true` permits recovery-admin login but + bypasses Authentik; remove it and redeploy after administration. +- Session cleanup is disabled to avoid repeated interactive sync logins. + Removing an Authentik binding alone does not revoke Joplin sessions; disable + the Joplin user and revoke their sessions too. + ## Forward-auth - Protected apps: Backrest (`backups`), Notes, Prowlarr, Radarr, Sonarr, qBittorrent. @@ -100,7 +124,7 @@ X-authentik-meta-app, X-authentik-meta-version | Host path | Container use | | --- | --- | -| `/data/authentik/postgres` | PostgreSQL `/var/lib/postgresql/data` | +| `/home/jay/data/authentik/postgres` | PostgreSQL `/var/lib/postgresql/data`; SSD since 2026-10-27 | | `/data/authentik/data` | Server + worker `/data` | | `/data/authentik/blueprints` | Worker `/blueprints/custom:ro` | diff --git a/docs/home-server/backups.md b/docs/home-server/backups.md index 941a181..7f40496 100644 --- a/docs/home-server/backups.md +++ b/docs/home-server/backups.md @@ -6,6 +6,8 @@ scope: [jupiter, backrest, restic, google-drive, recovery] sensitivity: private-infrastructure last_reviewed: "2026-10-27" sources: + - kind: live-inspection + reference: "Backrest plan and read-only SSD mount verified after PostgreSQL cutover 2026-10-27; seven original application paths plus four new SSD database paths" - kind: owner-report reference: "Plan/hooks/key custody 2026-10-06; six-directory plan and Authentik names 2026-10-16; downloads not backed up 2026-10-26; no restore evidence" - kind: repository @@ -30,9 +32,13 @@ unknowns: [last-successful-backup-and-check, google-drive-repository-path, measu ## Coverage -- Backrest sees `/data` as `/userdata:ro`; **only** these six directories are selected: - `authentik`, `gitea`, `paperless-ngx`, `portainer`, `vaultwarden`, `wardrowbe`. -- Case-insensitive exclusions: `/userdata/gitea/gitea/packages`, `/userdata/wardrowbe/redis`. +- Backrest sees `/data` as `/userdata:ro`; these seven application directories are selected: + `authentik`, `gitea`, `paperless-ngx`, `portainer`, `trek`, `vaultwarden`, `wardrowbe`. +- `/home/jay/data` is exposed read-only as `/ssddata`. The plan additionally selects + `/ssddata/{authentik/postgres,gitea/db,paperless-ngx/postgres,wardrowbe/postgres}`. +- Case-insensitive exclusions: `/userdata/gitea/gitea/packages`, `/userdata/wardrowbe/redis`, + and stale pre-SSD copies `/userdata/{authentik/postgres,gitea/db,paperless-ngx/postgres,wardrowbe/postgres}`. +- CTQ's new `/ssddata/ctq/postgres` is **not** in the scheduled plan; the migration did not extend its previous backup coverage. Private logical dumps for all five databases are retained on the SSD, not off-host backups. - `excludes: []`; CLI `--skip-if-unchanged` despite plan `skipIfUnchanged: false`; unchanged runs may create no snapshot. ### Local-downloads recovery gap @@ -72,6 +78,7 @@ unknowns: [last-successful-backup-and-check, google-drive-repository-path, measu | `/data/backrest/rclone` | `/root/.config/rclone` | | `/home/jay/data/backrest/cache` | `/cache` | | `/data/backrest/restore` | `/restore` | +| `/home/jay/data` | `/ssddata:ro`; selected PostgreSQL directories only | | `/var/run/docker.sock` | Same path; lifecycle hooks | ## Recovery limits diff --git a/docs/home-server/notes.md b/docs/home-server/notes.md index d8d561f..4005597 100644 --- a/docs/home-server/notes.md +++ b/docs/home-server/notes.md @@ -44,7 +44,8 @@ flowchart LR Git -->|"Signed POST"| Builder -->|"/site-output"| Static -->|"/usr/share/nginx/html"| Web ``` -- Web: `https://notes.umbra.mom`, Traefik + [Authentik forward-auth](authentication.md#forward-auth). +- Web: `https://docs.umbra.mom`, Traefik + [Authentik forward-auth](authentication.md#forward-auth). +- `https://notes.umbra.mom` is reserved for Joplin Server sync, using native Authentik SAML and the **Joplin Server (SAML)** client target. - Clone source: `http://gitea:3000/jay/notes.git`; requires `zensical.toml`, `pyproject.toml`, `uv.lock`. - Listener `/builder/listener.py` checks `X-Gitea-Signature` with `WEBHOOK_SECRET`. - **202 = queued**, not built. Single worker logs `Documentation build succeeded` after generated `index.html`. diff --git a/docs/home-server/storage.md b/docs/home-server/storage.md index 6b30588..737a310 100644 --- a/docs/home-server/storage.md +++ b/docs/home-server/storage.md @@ -6,6 +6,8 @@ scope: [jupiter, disks, raid, filesystems, docker-volumes, media-import] sensitivity: private-infrastructure last_reviewed: "2026-10-27" sources: + - kind: live-inspection + reference: "Five PostgreSQL SSD cutovers and Backrest mount verified 2026-10-27; original database copies retained" - kind: owner-report reference: "lsblk/mdadm/fstab/findmnt/volume snapshots 2026-10-06; local hardlinks/imports and remote-mount removal confirmed 2026-10-26" - kind: repository @@ -36,12 +38,12 @@ config: .infraService rect { fill:var(--infra-service-fill);stroke:var(--infra-service-stroke);rx:8px;ry:8px; } --- flowchart TB - accTitle: SSD system storage and non-redundant HDD application storage - accDescr: Docker volumes and caches are on SSD; service bind mounts, downloads and libraries are on the striped HDD array. + accTitle: SSD system and database storage with non-redundant HDD application storage + accDescr: Docker volumes, PostgreSQL and caches are on SSD; other service bind mounts, downloads and libraries are on the striped HDD array. subgraph SSD["SSD / SAMSUNG 860 EVO / 1 TB"] Root["sdc3 / ext4 root"]:::infraStorage Docker["/var/lib/docker
/var/lib/containerd"]:::infraService - Cache["/home/jay/data
service caches"]:::infraService + Cache["/home/jay/data
PostgreSQL + service caches"]:::infraService Root --> Docker Root --> Cache end @@ -55,8 +57,11 @@ flowchart TB - Either HDD failure loses the array, including application state; [backup coverage](backups.md#coverage) is explicit, not all of `/data`. - SSD cache paths: `/home/jay/data/{backrest/cache,jellyfin/cache,wardrowbe/ollama,wardrowbe/rembg}`. -- `/data/` holds service bind mounts; application-specific mappings live on each service page. -- Wardrowbe binds: `/data/wardrowbe/{postgres,uploads,redis}`; SSD models/caches above. +- SSD PostgreSQL paths: `/home/jay/data/{authentik/postgres,gitea/db,paperless-ngx/postgres,wardrowbe/postgres,ctq/postgres}`. +- `/data/` holds other service bind mounts; application-specific mappings live on each service page. +- Wardrowbe uploads/Redis remain at `/data/wardrowbe/{uploads,redis}`; PostgreSQL, models and caches are on SSD. +- All five PostgreSQL databases were cold-copied on 2026-10-27 without version changes; original bind directories and CTQ's old named volume are retained but stale. Do not switch back after new writes without a verified reverse copy/restore. +- Immich was removed and was not migrated. Only CTQ's explicit storage layout changed: its named volume was already on SSD. ## RAID / mounts @@ -104,7 +109,7 @@ Snapshot: driver `local`, no options; `/var/lib/docker/volumes//_data` on | `jellyfin_config` | Jellyfin `/config` | | `notes_static` | Builder `/site-output`; web `/usr/share/nginx/html` | | `dozzle_dozzle_data` | Dozzle `/data` | -| `ctq_ctq_postgres_data` | CTQ PostgreSQL `/var/lib/postgresql/data` | +| `ctq_ctq_postgres_data` | Retained pre-cutover CTQ PostgreSQL copy; no current consumer | | `havox_src` | Havox web/sync `/git` | - `jellyfin_cache`, `notes_notes_static` and monitoring volumes had no shown running consumer; **not evidence they are safe to delete**. diff --git a/zensical.toml b/zensical.toml index d0f1d68..cb4f9c7 100644 --- a/zensical.toml +++ b/zensical.toml @@ -1,6 +1,6 @@ [project] site_name = "Jupiter Notes" -site_url = "https://notes.umbra.mom/" +site_url = "https://docs.umbra.mom/" site_description = "University notes & personal notes" extra_javascript = [ "javascripts/mathjax.js",