Operate Web Fleet

First-run setup

Database choice comes before the first administrator. SQLite remains the simplest default; PostgreSQL is available for operators who want an external database.

Development status: the PostgreSQL storage path and browser setup flow are implemented in development; live PostgreSQL parity remains a CP30 battle-hardening gate.

Choose the database first

The ordinary setup flow will present SQLite and PostgreSQL before asking for an administrator email or password. This avoids creating identity data in one database and then casually switching providers underneath it.

Database

● SQLite
  Simplest setup. Web Fleet owns one local database file.

○ PostgreSQL
  Use an existing PostgreSQL server.

[ Continue with SQLite ]

PostgreSQL

Selecting PostgreSQL reveals the connection URL and a connection test. The action remains visibly disabled while the URL is empty.

PostgreSQL URL
postgres://webfleet:password@db.internal:5432/webfleet

[ Test and use PostgreSQL ]

Web Fleet validates the real connection before accepting it. If the provider change requires a process restart, setup stops and displays an explicit restart-required state rather than exposing the administrator form prematurely.

Restart required

PostgreSQL is configured.

1. Stop and start Web Fleet.
2. Reload this page.
3. Create the administrator account.

Create the administrator

After restart the page must explicitly say Create the administrator account. It is not a login screen: no administrator exists yet.

Server-managed configuration

Automated deployments can provide WEBFLEET_DATABASE_URL before first launch. The browser flow remains the default experience for ordinary self-hosters.