Db
Saphira Linux databaseDragon
Relational databases on infrastructure you control: choose SQLite, MariaDB or PostgreSQL, understand the access you need, and keep your data where it belongs.
Management without the repetitive mechanics
The database packages are available now, and their normal documentation remains the right reference for operating them. We intend to publish simple database-management helpers, particularly around MariaDB, but those helpers are not yet a released public Saphira feature. This page does not invent commands or present unfinished automation as something you can install today.
What future helpers should make simpler
The aim is to let an administrator express an intention such as “give this application server access to this database” and have the repetitive mechanics remain clear and recoverable underneath it.
- Create and safely remove databases and database users.
- Change credentials, grant and revoke privileges, and inspect current access.
- Choose which databases a user may use and whether access is local or remote.
- Allow an intended IPv4 host, IPv6 host or both, then remove obsolete access.
- Coordinate database permissions with the corresponding nftables exposure without changing unrelated firewall policy.
Getting started
Choose SQLite when the application wants a local embedded relational database. Choose MariaDB for the conventional web and application-server role, or PostgreSQL when that is what the application is built for. Start with local access where possible, then add specific remote users, database permissions and nftables rules only when another host genuinely needs them.