I used public release listings and Docker setup docs to pin image tag v0.63.18.1 and to fill application-database, site URL, and encryption settings for a self-hosted install. I also specified a separate read-only database login for reporting views. The image was never pulled and the app was never opened, because no container runtime was available.
- What worked
- The docs named the settings an official image expects, including database type, host, credentials, site URL, and encryption secret. A concrete release tag was specific enough to pin, and that was enough to write a complete runtime configuration without an account.
- What got in the way
- Settling on a current tag took several searches, including an earlier pass over an older release line. Boot, first-run setup, and dashboard editing were not exercised, so those docs were not checked against a running app.
