Pam (NAS)
Synology DS1517+, on the home network at 192.168.1.16 (SSH alias nas)
and also on the tailnet as pam (100.109.83.48). 7 TB volume, about 1 TB used
(2026-10-23). Intel Atom C2538, 4 cores, 15 GB RAM, no GPU (no /dev/dri, no Quick
Sync), so nothing here can hardware-transcode video.
Tailscale runs in userspace mode (--tun=userspace-networking): inbound tailnet
connections are forwarded to localhost ports, so TCP services (SMB 445, Garage 3900,
Jellyfin 8096) work over the tailnet, but they see the client as 127.0.0.1.
Docker runs via Synology’s Container Manager (docker lives at
/usr/local/bin/docker, not on the default $PATH; the nas SSH user has
passwordless sudo scoped to that one binary, not general root).
What’s actually running
Section titled “What’s actually running”Active — a monitoring stack (Compose project infra, now tracked in
docker-infra/monitoring
at /volume1/docker/docker-infra/monitoring/docker-compose.yml, deployed
automatically on push via Gitea Actions - see that repo’s README. This
is the one service directory in docker-infra that deploys to Pam instead
of Lana, since Pam has no git access: the workflow pushes the compose
file over SSH rather than pulling. The old untracked copy at
/volume1/docker/monitoring/infra/ has been renamed aside
(infra.superseded-by-vps-infra-git - name predates this repo’s own
rename, left as-is since it’s just a retired marker), not deleted, in
case anything
still points at it):
- Grafana, running a custom
grafana-lunar-outpostimage withGF_USERS_DEFAULT_THEME=lunar-outpostset by default. This predates — and wasn’t cross-referenced by — the Lunar-Outpost design system repo’s own “already shipped” table; worth adding it there as a sixth canonical surface. - InfluxDB 2, bucket
homeassistant, orghome— this is where Home Assistant’s metrics land for long-term storage and the Grafana dashboards read from.
Both on the infra_default Docker network, restart: unless-stopped,
exposed on the LAN at :3000 (Grafana) and :8086 (InfluxDB).
Active — Garage, a small S3-compatible
object store (Compose project garage, tracked in
docker-infra/garage,
deployed on push the same way monitoring is). A single node, one copy of each
object, with the RAID 6 volume as the redundancy. Data lives in
/volume1/docker/garage/{meta,data}.
- S3 API on
:3900, reachable on the LAN and the tailnet; every request needs an access key. The admin API (:3903) is bound to localhost. - One bucket so far,
game-backups, for the backups AMP makes on the Cheryl. Its key (amp-backups) can read and write that bucket only. - Synology’s Docker won’t create a missing bind-mount directory, so the deploy workflow makes the data directories itself.
Active — Jellyfin (Compose project jellyfin,
tracked in docker-infra/jellyfin,
deployed on push like Garage; replaced Plex 2026-10-28). Host networking on :8096, config in
/volume1/docker/jellyfin/config, the library mounted read-only. Direct play only, because the
CPU can’t transcode 4K or HEVC. It runs as the DSM user arr (1028:100); see the ACL notes
below.
The media share (/volume1/media/{tv,movies}) is the library, and since 2026-11-17
also holds the downloads (/volume1/media/usenet). The arr stack
runs on Pam (Compose project arr, config in /volume1/docker/arr/config) as the DSM user
arr, which has read/write on media only; Jellyfin reads it. Until then Sonarr and Radarr
on old Cheryl wrote it over SMB.
Synology ACLs vs containers. Inside a container no uid is in administrators, so:
- The
dockershare’s inherited ACL (write for administrators and Container Manager only) makes a non-root container’s bind mounts read-only. Jellyfin’s folder has its own entry,user:arr:allow:rwxpdDaARWc--:fd--, added bydeploy-jellyfin.yml.synoacltool -enforce-inheritremoves explicit entries like that one; don’t run it there. - The
mediashare admits onlyadministratorsandarr, so any other uid can’t even list it. That’s why Jellyfin runs asarr. synoacltoolworks without sudo on folders thenasuser can change, but not on a share’s root (owned by root); thenasuser’s sudo coversdockeronly.
Stopped, but present — a second constellation of containers, all
exited about 5 weeks before this was last checked (uniform timing suggests
a NAS reboot or mass stop, not per-project retirement), corresponding to
repos in ~/dev on the Mac:
solar_*(solar_ha_control, solar_decision_engine, solar_modeling, solar_forecast, solar_extractor, solar_dashboard, solar_timescaledb) — the solar-energy-optimizer project. Has its own TimescaleDB, separate from the InfluxDB above.comfort_air_*(comfort_air_ha_runner, comfort_air_engine, comfort_air_extractor) — the comfort-air-controller project.household-ai-scheduler,household-ai-discord,ollama-embeddings— the household-ai-advisor project, including a Discord bot.
Whether these are meant to be running again or were deliberately stopped is unconfirmed from the outside — worth checking before assuming either way.
Pam is home-automation compute and metrics storage, the media library and Jellyfin server, and since Garage was added, the backup target for Cheryl’s game servers. It is still not a backup destination for Lana or Krieger. Lana currently has no offsite/off-box backup path at all; Garage is the obvious place for one (a second bucket and key, plus a tailnet ACL rule letting Lana reach Pam on 3900).
Gaps to fill in
Section titled “Gaps to fill in”- Whether the stopped
solar_*/comfort_air_*/household-ai-*stacks should be running, and if so, why they aren’t. - DSM version: confirmed 7.3.1 (via
/etc/VERSIONon the NAS). What else (if anything) runs outside Docker — file shares, Synology’s own packages, etc. — is still unconfirmed. - Grafana now authenticates via Authentik SSO (
GF_AUTH_GENERIC_OAUTH_*env vars inmonitoring/docker-compose.ymlpoint atauth.spelvin.dev). A comment in that file says “same pattern as Synology DSM,” implying DSM’s own login has also been switched to Authentik SSO — not independently confirmed on the NAS itself, worth checking directly. - The credentials embedded in the
infrastack’s container env (Grafana/InfluxDB admin passwords, an InfluxDB API token) turned up in plain text during this audit — worth rotating regardless of whether they’re otherwise exposed anywhere.