ConfigurationRegistriesForgejo
FORGEJO
The forgejo registry lets you configure a self-hosted Forgejo integration.
The forgejo registry lets you configure a self-hosted Forgejo integration.
Variables
| Env var | Required | Description | Supported values | Default value when missing |
|---|---|---|---|---|
DD_REGISTRY_FORGEJO_{REGISTRY_NAME}_URL | 🔴 | Registry URL (e.g. https://forgejo.acme.com) | ||
DD_REGISTRY_FORGEJO_{REGISTRY_NAME}_LOGIN | ⚪ | Forgejo username | DD_REGISTRY_FORGEJO_{REGISTRY_NAME}_PASSWORD must be defined | |
DD_REGISTRY_FORGEJO_{REGISTRY_NAME}_PASSWORD | ⚪ | Forgejo password or personal access token | DD_REGISTRY_FORGEJO_{REGISTRY_NAME}_LOGIN must be defined | |
DD_REGISTRY_FORGEJO_{REGISTRY_NAME}_AUTH | ⚪ | Base64-encoded login:password string | DD_REGISTRY_FORGEJO_{REGISTRY_NAME}_LOGIN/PASSWORD must not be defined | |
DD_REGISTRY_FORGEJO_{REGISTRY_NAME}_CAFILE | ⚪ | Path to custom CA certificate file | ||
DD_REGISTRY_FORGEJO_{REGISTRY_NAME}_INSECURE | ⚪ | Disable HTTPS certificate validation (plain HTTP is selected by the registry URL scheme) | true, false | false |
DD_REGISTRY_FORGEJO_{REGISTRY_NAME}_CLIENTCERT | ⚪ | Path to client certificate file for mTLS | DD_REGISTRY_FORGEJO_{REGISTRY_NAME}_CLIENTKEY must also be defined | |
DD_REGISTRY_FORGEJO_{REGISTRY_NAME}_CLIENTKEY | ⚪ | Path to client key file for mTLS | DD_REGISTRY_FORGEJO_{REGISTRY_NAME}_CLIENTCERT must also be defined |
Examples
Configure
services:
drydock:
image: codeswhat/drydock
...
environment:
- DD_REGISTRY_FORGEJO_PRIVATE_URL=https://forgejo.acme.com
- DD_REGISTRY_FORGEJO_PRIVATE_LOGIN=john
- DD_REGISTRY_FORGEJO_PRIVATE_PASSWORD=doe