Manage a database
The per-database page — connection details, the application it belongs to, users, tables, exports and deletion.
Every database has its own page, reached from Manage in the list or by clicking its name. It is one screen: what to connect with at the top, what is inside it in the middle, and the way to delete it at the bottom.
The heading carries the facts you usually want first: the name, the engine as a badge, the on-disk size and how long ago it was created.
Connection details
Host, Port, Database, Username and Password, each with a copy button, plus Copy connection string for the whole URL in one go.
The password is masked here, and stays masked — it is shown in full exactly once, in the dialog that appears when the database or the user is created. The copy button still copies the real value, so you rarely need to see it.
Install phpMyAdmin is a shortcut: it takes you to the application create form with phpMyAdmin preselected, so the browser-based client ends up as a proper application on this server, with its own domain and SSL, rather than something bolted onto the panel.
Used by
Which application owns this database — or a warning that none does.
Not linked to an application, so no backup includes it.
That is the whole consequence, and it is worth taking seriously: OSS Panel's backups run per application, so an unlinked database is in no backup at all. Attach to an application fixes it in one step.
Users
Who may sign in, and from where.
Each user shows its name, a badge for its connection scope — This server only, an address, or Anywhere — and its connection string with the password masked. The ⋯ menu on the row is where you remove a user.
Adding a user
A second user is the right answer when something else needs access with different reach: a reporting job on another host, or a migration tool you want to revoke afterwards without disturbing the application.
Click Add user on the Users tab.
Name the user and choose where it may connect from — the same three options as the create form, with the same consequences. The dialog states the rule plainly: a strong password is generated for you and shown once when the user is created.
Click Add user, then copy the password from the dialog that follows. It is not shown again.
Tables
A read-only count and listing of what is in the database. A brand-new database
shows 0 — the tables appear once an application has run its migrations or an
installer. This tab is for confirming that something landed, not for editing;
for that, install phpMyAdmin.
Exports
A copy of the database, made now and kept on this server.
Export now runs a dump. It appears in the list within a few seconds marked Ready, with its age and size, a download button and a delete button. The list screen's Last export column reflects the newest one.
An export on the same disk is not a backup
The panel says so under the list: these files are kept on this server, next to the database itself. Download a copy somewhere else — a file on the same disk will not survive a disk failure.
Nothing deletes exports for you either, so they accumulate until you remove them. For scheduled, off-server copies, link the database to an application and use backups.
Deleting a database
The red card at the bottom: removes the database, everything in it, and its users.
It is immediate and it is not recoverable from inside the panel. Take an export first and download it, or make sure a backup exists — then delete.
Deleting the database does not delete the application that used it. If you are tearing down a whole site, delete the application from its own page and check this list afterwards for anything left behind.