wizardchen 3cf0be2e97 fix(embed): warn at startup when no signing key is configured ...

Deployments upgraded from the old .env.example keep the published example
SYSTEM_AES_KEY, which SystemHMACKey rejects since v0.8.2. Embed sessions
then fail at request time with no hint at boot.

- Log a [startup-env] warning when no usable signing key is found, and
  surface SYSTEM_SIGNING_KEY in the startup env banner.
- Name SYSTEM_SIGNING_KEY in the embed session 503 error.
- Provision the desktop signing key before printing the banner so the
  desktop build does not warn about a key it is about to create.
- Document the symptoms and fix in troubleshooting.

2026-09-24 20:29:17 +08:00

..

container.go

init commit

2025-08-05 15:08:07 +08:00

server_test.go

feat(system): add server startup time and uptime tracking

2026-06-04 15:48:04 +08:00

server.go

feat(system): add server startup time and uptime tracking

2026-06-04 15:48:04 +08:00

startup.go

fix(embed): warn at startup when no signing key is configured

2026-09-24 20:29:17 +08:00