MySQL databases

A real database for your plugins. Credentials, where they work, and what deletion does.

Creating one

Under Databases you create one. How many is your plan's business. You immediately get host, port, database name, user and password.

The user has rights on exactly that one database and no other. The number of simultaneous connections is capped, so a misconfigured connection pool cannot take the server down for everybody else.

Putting it into a plugin

Most plugins ask for exactly these five values. Enter them as they appear in the interface.

host: mysql.citexnode.de
port: 3306
database: cn_xxxxxxxx
username: cn_xxxxxxxx
password: (from the interface)

The shape of it. Your real values are under Databases on your instance.

Connecting from home

Same host, same port, same credentials. HeidiSQL, DBeaver, TablePlus or your IDE's MySQL plugin connect straight to it.

Host: mysql.citexnode.de
Port: 3306
User: cn_xxxxxxxx
Password: (from the panel)

The database name is the same as the user name.

Turn SSL on in your client if it offers it. Your password never crosses the wire in the clear either way, but your queries and your data do until you switch SSL on.

The password is yours alone. It is usable from anywhere in the world, so if it gets away from you, delete the database and create a new one.

Deleting

Delete the database and the schema and its user really go. Delete the instance and its databases go with it.

Both are final. A backup of your server does not contain the database; that lives elsewhere.