Skip to main content

Databases

Databases shows where each application's data lives and how Hosting reaches it. You do not create databases here: one is created and named for each application.

Each application has its own identity​

Every application gets its own database and its own database user on the environment's shared MariaDB server. Each database identity is restricted to its own database. This does not isolate applications' files: an environment maintainer can read sibling configuration files and their database credentials. See SFTP & SSH access.

For each application the page shows:

  • Internal host:port — the address the application uses, reachable from inside the environment. MariaDB is a private service and is never exposed to the internet.
  • Database — the database's own name.
  • Username — the identity's user name.
  • Password — revealed only when you ask for it, with Show password.

Copy a password with the copy control beside it. The page does not keep it visible: hiding it again, or leaving the environment, clears it.

Credentials are per environment

An application's database credentials belong to that environment. A copy you paste into a staging environment is a different database, even when the names look alike. Treat the credentials as secrets: they are enough to read and change everything that application stores.

Run SQL in the browser​

Each application's database panel links to phpMyAdmin, signed in as that application's database user. It opens in its own browser tab and reaches only that application's database — the identity it signs in with does not have access to its siblings.

The cache​

Where an environment runs a Redis cache, its internal address is shown beside the databases. The cache is not a database: treat anything in it as disposable, because it can be lost and rebuilt at any time. It is reachable from inside the environment only.

Restoring a database​

Databases are backed up — see Backups and restores — but a restore is not a self-service action. A database restore is done by us, from the backup track, into a reviewed target.

Next​