Databases section
The Databases section (right rail) is a declarative catalog of connections. It only describes connections so a micro can point at them; Aseptic does not start or orchestrate database instances.
A connection
Section titled “A connection”Each connection has: name, engine (postgresql, mysql, mariadb, oracle,
sqlserver, mongodb), host, port, user and password.
Secrets go as ${creds.x} (resolved from settings.local.yml, outside Git), never in
cleartext. See Credentials.
Test does a TCP reachability check: does the host:port respond? It does not
validate credentials or the schema, only that the machine is reachable.
Point a micro at a connection
Section titled “Point a micro at a connection”In a micro’s editor, the database selector (inside the startup configuration) lets you
choose a connection from the catalog. When you select it, its host:port replaces the one
in the URL the micro already declares. See Point at another
DB.
Deleting a connection
Section titled “Deleting a connection”Deleting a connection detaches the micros that had it selected: they go back to their default database (the local URL the micro declares) and Aseptic tells you which ones. That way no selection is left pointing at a connection that no longer exists.
If a reference to a missing connection still shows up — for instance when importing a bundle from another machine — Aseptic does not start that micro: starting it would put it in its local database, which is not the one that was chosen. The Environment check marks it as a failure, and the micro’s selector shows it as a connection not found.
From the CLI
Section titled “From the CLI”aseptic db list, db save, db delete, db test <host> <port>. The catalog lives in
.aseptic/databases.yml (versionable).