Database Configuration
How Auvyra chooses and prepares its database.
Choosing an engine
Auvyra loads the adapter named by DATABASE_PROVIDER:
| Engine | Status |
|---|---|
| MongoDB | Supported |
| PostgreSQL | Supported |
| MySQL | Supported |
| MariaDB | Supported |
| SQLite | Supported |
MongoDB is the default. Pick whichever you are happy to run and back up, because every feature works on all of them. SQLite needs no database server, which suits a small station on one machine. An unknown provider stops startup with an error listing what is available.
Each engine has its own setup page: MongoDB, PostgreSQL, MySQL, MariaDB and SQLite.
Why this happens before the wizard
Auvyra needs its database before it can check who you are, so connection details are set in the environment before the web server starts. Credentials therefore never pass through a browser. The setup wizard then verifies the connection for you.
Initialization
On first connection, Auvyra applies pending migrations, which create indexes or tables. Applied migrations are recorded, so this is safe on every start.
To run the same step manually:
pnpm db:initChecking status
Owners can see health, engine version and latency under Database Settings in the dashboard. Connection strings are never displayed.
Moving between engines
Export your station to one file and import it on the new engine. See Moving a Station. Changing DATABASE_PROVIDER by itself does not copy your data.