Skip to content
VORQUL
VorqulPanel / Databases

Databases and Adminer

Database management in a hosting panel is mostly about two things: not handing out root, and having a dump from before the thing that broke.

VorqulPanel manages MariaDB databases: creating databases and users with least-privilege grants, scheduling dumps with retention, and providing an integrated Adminer instance reachable only through panel authentication. The panel’s own data lives in SQLite, so MariaDB is needed only for hosted applications.

Engine
MariaDB / MySQL
Web client
Adminer, panel-gated
Grants
Least privilege per site
Backups
Scheduled dumps + retention

Databases and users

Creating a database creates a matching user with grants scoped to that database only. No application on the server gets credentials broader than the thing it is supposed to touch, which is the difference between one compromised site and all of them.

Passwords are generated, shown once, and stored hashed where the panel needs to reference them. Rotation is a single action.

Adminer

Adminer is bundled and served through the panel, which means it is behind the panel’s authentication rather than sitting at a predictable URL waiting to be scanned. It is a common enough entry point in compromised servers that leaving it publicly reachable is worth avoiding.

It can be disabled entirely if you prefer to connect over SSH.

Dumps and retention

  • Scheduled logical dumps per database
  • Retention policy by count or age
  • Manual dump before risky operations
  • Download and restore from the panel
  • Compressed storage with checksums

The panel’s own storage

VorqulPanel keeps its own state in SQLite - one file, no separate service, no credentials to manage. This is deliberate: a control panel that requires a working database server before it can tell you why your database server is not working has a bootstrapping problem.

Frequently asked questions

Related pages