Datica Secure Console
The Secure Console offers interactive command-line access to your environment's database services, using the corresponding shell. These map out as follows:
- PostgreSQL:
psql
- MySQL (Percona):
mysql
- MongoDO:
mongo
Opening a Secure Console
Using the CLI’s console command and the name of the database service (found in The Platform dashboard):
datica -E "<your_env_name>" console <database name>
For example, for a database named db01
:
datica -E "<your_env_name>" console db01
Using the Console With Code Services
The console can also be used with code services, but a command needs to be specified. For example, to run bash
on a code service named app01
:
datica -E "<your_env_name>" console app01 bash
Take note: the secure console runs in a copy of your code service's container - not one of the application's running containers. This means that any local filesystem changes will not be reflected in the containers for your running application. If there's a post-deploy local filesystem change regularly required, a post-build script is a good solution.
Console vs SSH
The secure console is not SSH, and is quite limited. It is a temporary tunnel, and can at times close abruptly. To enable SSH to your environment’s containers, a VPN is required.