Server Configuration
The server component is delivered with a dotenv file. This file describes all the environment values one can configure to influence the way the server runs. Where defaults are this is also documented inside the file. These values need to be created/overruled as environment values before the server starts. Depending how the server component runs there are specific ways to do this:
- For RPM/DEB based: a systemd unit file is deployed that will read the dotenv file. consult the unit file for the exact location of the doting file.
- For OCI Container based: Both Podman and Docker provide several ways to load env's from files and even separate some out as secrets.
- For Kubernetes based: create a config-map that contain all the envs. Also one can use the secrets facility of Kubernetes.
Note: which of the envs need to be regarded as secrets is up to the administrator
Initial Admin User
There is a special procedure to be followed to create the first system administrator:
-
When the server starts up for the first time (so with an empty database) or when the env INIT is true, the admin user is (re)created in the database with the username and email address from the env's and a randomly generated password.
-
After this you can use the command cq user password on this user to change the password to something you known. A verification code will be send to the admin user's email address and needs to be entered using the cq user verify command