First-run setup status + admin-form prefills
GET /setup/status
Returns whether the system still needs first-run setup, plus
read-only deployment info (DB host/port, storage backend) and
any prefill values the admin’s deploy environment provided via
AA_SETUP_DEFAULT_* env vars. Anonymous access — this is the
first thing a brand-new install renders.
Responses
Section titled “ Responses ”Setup status + defaults
object
True when no user with the system.admin capability exists.
Read-only view of how the running process was configured at boot. Shown on the setup page so the admin can confirm the installation target before creating an admin account.
object
Example
postgresExample
5432Example
artist_alleyFs | s3
Example
fsPrefills harvested from AA_SETUP_DEFAULT_* env vars at boot.
Empty strings mean “no prefill”; the form leaves those fields
blank.
object
Example
artist-alleyExample
587Example
starttlsTrue when the install serves its public read surface to anonymous visitors. The frontend reads this to decide whether a signed-out visitor may stay on a public route or must be sent to the sign-in page; the server enforces the same setting independently, so this field is a rendering hint and never the access decision.
It rides on this endpoint because the frontend already calls it first on every navigation, before it knows whether a session exists — so the flag is available at the moment the routing decision is made, without a second request.
Unexpected server error
object
Human-readable error summary
Example
the request could not be completed