Databases Reference
Use database commands to install and operate MariaDB, PostgreSQL, Redis, and Memcached on managed servers.
At a Glance
MariaDB Commands
| Command | Use it when you need to... |
|---|---|
mariadb:install |
install MariaDB and initialize application credentials |
mariadb:start |
start the MariaDB service |
mariadb:stop |
stop MariaDB for maintenance |
mariadb:restart |
restart MariaDB after operational changes |
PostgreSQL Commands
| Command | Use it when you need to... |
|---|---|
postgresql:install |
install PostgreSQL and initialize application credentials |
postgresql:start |
start PostgreSQL |
postgresql:stop |
stop PostgreSQL for maintenance |
postgresql:restart |
restart PostgreSQL after operational changes |
Redis Commands
| Command | Use it when you need to... |
|---|---|
redis:install |
install Redis and configure authentication |
redis:start |
start Redis |
redis:stop |
stop Redis for maintenance |
redis:restart |
restart Redis after operational changes |
Memcached Commands
| Command | Use it when you need to... |
|---|---|
memcached:install |
install Memcached |
memcached:start |
start Memcached |
memcached:stop |
stop Memcached for maintenance |
memcached:restart |
restart Memcached after operational changes |
Details
Installation and Credentials
MariaDB, PostgreSQL, and Redis share a credential delivery workflow during installation. After installing the service, you can choose to display credentials on screen or save them to a file (written with 0600 permissions, appending to existing credential files).
Each install command is idempotent: if the service is already installed, DeployerPHP detects it and skips reinstallation. Credentials are only generated on fresh installs, so capture them during the initial installation.
Memcached Installation
Memcached is configured for localhost-only access and does not require authentication. Because of this, memcached:install has no credential output flow. There are no passwords to capture or store.
Lifecycle Commands
All four services share the same start, stop, and restart pattern for runtime control after installation. These are straightforward service lifecycle commands.