compose up -d leaves NATS on its old config when only the bind-mounted
nats.conf changed, so the 8 MB max_payload never applied on upgrades.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- PUBLIC_SERVER_URL and TRUSTED_HOSTS left at .env.example's sample
(control.example.com, any RFC 2606 name) are ignored with a startup
warning: links follow the forwarded headers and devices download from
the server URL they already use. .env.example ships them empty and
deploy.sh clears sample values from an existing .env.
- The screen host is built from its own folder so .cargo/config.toml's
+crt-static applies; the shipped exe imported VCRUNTIME140.dll and died
without output on devices without the Visual C++ runtime ("the screen
host gave no answer"). The build now refuses an exe with CRT imports.
- A failed screen host probe is retried with backoff (30 s up to 10 min)
and the inventory is republished once it answers; the warning and the
reason carry the exit code.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docker-compose.yml gains a postgres service (EXECUTER-DB-00001, official
image pinned by major and digest like NATS, INTERNAL network only, no host
port, pg_isready health check, shm_size, runs as PUID:PGID, data in
${STACK_BINDMOUNTROOT}/${STACK_NAME}/Postgres/Data). It is in the "postgres"
Compose profile; COMPOSE_PROFILES in .env turns it on, and the backend waits
for it healthy (depends_on required: false, so SQLite and external databases
start without it). The backend defaults to DATABASE_PROVIDER=postgres with
DATABASE_CONNECTION_STRING and DATABASE_PASSWORD from .env.
docker-compose.postgres-port.yml publishes a host port, opt-in through
POSTGRES_BIND.
deploy.sh decides the database: what .env names when the operator set it;
else SQLite when API/Data/app.db exists (written to .env, with a note on how
to move); else the bundled Postgres, its password generated into .env (and
exported), never regenerated over an existing database. COMPOSE_PROFILES
follows. The decisions are functions that scripts/tests/Test-DeployDatabase.sh
runs on fixtures without Docker. Compose 2.20.2+ is checked; a new .env is
mode 600. New-LocalSecrets.ps1 generates the password for a new .env and
keeps an existing .env's database settings on -Force.
README: deploy, secrets, Compose, database providers, Postgres backups and
pg_restore, and Moving from SQLite to Postgres (migrate-database).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scripts/tests/Test-Branding.ps1 reads each exe's first RT_GROUP_ICON and
compares its frames byte for byte with assets/icons/app.ico, and checks the
version resource names description, product, company, copyright and
version. README: where the icon lives, how executables get it, how to
regenerate it; ImageMagick is no longer a prerequisite.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scripts/tests/Test-Versioning.ps1 (plain asserts, no Pester): the version
rules against canned git describe output and the limits, then a scratch
SHA-256 repository with a bare origin walked through the seed: calendar
tags ignored, no release tag refused, v0.1.0 plus a breaking change
releases 1.0.0, a re-run of the tagged commit is 1.0.0 again, builds after
it are 1.0.0.N, docs alone release nothing, a fix 1.0.1, a feat 1.1.0, a
branch other than main is refused.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>