Configuration
Verlign stores configuration in a local JSON file and supports environment variable overrides.
Config file
Location: ~/.verlign/config.json
Permissions: 0600 (read/write for owner only)
{
"apiKey": "your-api-key",
"apiUrl": "https://api.verlign.com"
}Fields
| Field | Description | Default |
|---|---|---|
apiKey | Your Verlign API key (set by verlign login) | — |
apiUrl | API endpoint URL | https://api.verlign.com |
The config file is created automatically when you run verlign login. You can also edit it manually.
Environment variables
Environment variables override config file values:
| Variable | Description |
|---|---|
VERLIGN_API_KEY | API key for authentication |
API_URL | Base URL for the Verlign API |
Troubleshooting
Docker is not running
Error: Docker is not runningStart Docker Desktop (or the Docker daemon) and try again. The CLI checks Docker availability by running docker info.
Permission denied on config file
Error: EACCES: permission deniedThe config file at ~/.verlign/config.json must be owned by your user with 0600 permissions:
chmod 600 ~/.verlign/config.jsonWrong API URL
If you are using a self-hosted Verlign instance, set the apiUrl field in your config file or the API_URL environment variable to point to your server.
Container fails to start
Make sure:
- Docker has enough resources allocated (memory, disk)
- You can pull images from
ghcr.io(check network/proxy settings) - The codebase path exists and is readable
Last updated on