Databases

Open Databases and choose New database. Pick MariaDB (MySQL compatible, for WordPress and most PHP apps) or PostgreSQL. Your first database of an engine starts your own database server, on your own private network; it can take a minute the first time. Nobody else’s databases share it.

A database is named after you: shop becomes <prefix>_shop.

Give a site or an app its database

Open the site or app and its Database tab. Pick a database or name a new one, then Add database. The app gets DB_HOST, DB_PORT, DB_NAME, DB_USER, DB_PASSWORD and DATABASE_URL, the password sealed, and restarts with them as one revision.

• New password gives it another one.
• Remove takes the variables and the app’s user away, and keeps the database.

Users

On the Users tab, a user has full rights on the databases you pick. Its password is shown once: copy it then. New password makes another.

Connect

Your apps reach the server at the host on the Connect tab, on your private network. It is not reachable from the internet.

Adminer is a web tool for your databases at an address of yours, under a domain you have proved. Only you and your organisation’s people get past the realm’s sign-in; then you sign in with a database user.

Dumps and restores

Every database is dumped each night, and on Dump now, consistently and without locking your site out. Restore last dump puts a database back as it was then.

The dumps sit on the server’s volume, so your operator’s backups keep them with your other volumes: an older dump is in an older restore point.

A dump made elsewhere can replace a database: the DirectAdmin importer does this for you (The velrix command).

Limits

How many databases you may have, and how much space, are your operator’s quotas. Your server’s disk is twice your plan’s database space, for the data and its dumps.