Configuration file
vidoc login writes the configuration file. The default location is:
To use a different file, set
VIDOC_CONFIG_FILE, or give -c <path> to vidoc scan, vidoc ci, or vidoc export.
The file is YAML:
Each profile must have
token or token_env. If the file does not agree with this format, the CLI stops and shows the fields to fix.
Keep the key in an environment variable
vidoc login stores the key as plain text. To keep the key out of the file, use token_env:
- Run
vidoc config create-profile <name>. - For the storage of the key, select Environment Variable.
- Type the name of the variable. The default is
VIDOC_TOKEN_<NAME>. - Set the variable in your shell or your secret manager.
Profiles
A profile holds one API address and one API key. Use profiles when you work with more than one project or more than one Vidoc installation.
To use a profile for one command only, give
-p <name> or set VIDOC_PROFILE:
Environment variables
In a CI pipeline, you can use
VIDOC_TOKEN and VIDOC_API_URL without a configuration file.
Precedence
When a value has more than one source, the CLI uses the source that is highest in this table.
If the configuration file exists and does not have the selected profile, the CLI stops with the error
Profile "<name>" not found in config file.
Self-hosted: if no source sets the API address, the CLI uses the Vidoc Cloud API
https://api.vidoc.dev. Always set the address of your installation, in the profile or in VIDOC_API_URL.Related pages
Install and log in
Install the CLI and create an API key.
CI/CD pipelines
Use environment variables in CI.

