Creating and managing databases

Databases are in your game server's Databases tab, if your plan includes them. At the top you see how many you have and how many it allows. The owner can create them and see the credentials, and so can anyone who was given the Databases right when it was shared.

Create a database

1. 1

   Press Create database and enter a name: letters, digits and _, 3 to 48 characters. The server prefix goes in front.

2. 2

   If there is more than one, choose the Database type: PostgreSQL for software that supports it (LuckPerms, for example), MySQL/MariaDB for plugins that only know MySQL (CoreProtect, for example).

3. 3

   Under Access from, choose where people may sign in from (below), and press Create.

Host, port, database, user and password are then in the list, each ready to copy, plus a ready URI and JDBC line for plugins that ask for one line. Enter them in the plugin's configuration.

Where people may sign in from

Only from the game server

Only your server and your account's client area can reach the database.

From anywhere

Any address may try; the password protects the database.

Specific addresses

Up to 50 IP addresses or ranges such as 203.0.113.0/24, one per line, such as your own computer. MySQL/MariaDB only knows single addresses for IPv6.

The client area always may, so that managing it here works. Some database servers cannot turn sign-ins away by address; the database then says Not enforced, and only the password protects it.

Managing the database

Manage opens the database itself, with four areas. Everything runs with the database's own login, never with more rights.

• Tables: tables and views with row count and size. Page through, sort by any column, edit rows, insert them and delete them by holding. Views and tables without a primary key are read only.
• SQL: one statement per run, at most 15 seconds, up to 500 rows in the result. Read only is on until you switch it off; only then does a statement change anything.
• Back up: Export downloads the whole database as an SQL file, compressed as .sql.gz if you like. Import takes an .sql or .sql.gz file of up to 2 GB and runs it statement by statement. At the first error the import stops and names the line; whatever ran before stays in the database.
• Access: the credentials, where sign-ins may come from, Generate a new password (the old one stops working at once) and Delete database, both confirmed by holding.

Good to know

• The server's backups keep its files; the databases live on their own database servers. Back them up under Back up, or with Export everything, which takes every database along as an .sql file.
• Exports, imports, SQL statements that change something, edited rows, access and new passwords are listed in the server's Activity.
• So that nobody overloads the database servers, there are limits per person and database: 30 SQL statements and 120 row changes a minute, 6 exports and 3 imports in 10 minutes, and only one export or import at a time.

A website's databases

A website has the same Databases tab with the same management. Instead of “Only from the game server” you choose Only from the website there; MySQL/MariaDB suits most PHP applications such as WordPress, PostgreSQL for example Nextcloud.