Files
Assistant/docs/CREDENTIALS_AND_SECRETS.md
T
m 03dde8c196
CI / test (pull_request) Successful in 10s
CI / test (push) Successful in 10s
security: load Creator secrets from files
2026-08-16 17:57:32 +03:00

25 lines
1.5 KiB
Markdown

# Credentials and secrets
## Git
Remote is fixed to `https://git.cin.su/m/Assistant.git`.
The repository can be read externally, but a push may require authentication. First let normal Git credential helpers handle authentication. Do not add username/password to the remote URL.
If authentication is not already configured, ask the user for either:
- a Gitea personal access token with the minimum repository scope, or
- username + token/password if their local setup requires it.
Never store it in Git.
## Portainer
Target is `https://docker.cin.su`.
Preferred automation credential: `PORTAINER_API_KEY` supplied outside Git. `PORTAINER_ENDPOINT_ID` may also be required after environment discovery.
Do not guess Portainer credentials and do not search other project source trees for literal passwords. Existing OS/environment secret stores may be used without revealing values.
## Production services
Each privileged runtime gets only its required secret/capability bindings. `commit-runtime` is intentionally isolated from the general Core Runtime.
Creator authentication secrets are stored in the external Docker volume `assistant_core_secrets` and mounted read-only only at `/run/secrets` in `core-runtime`. The production container environment contains `_FILE` paths, not the secret values. Files are owned by runtime uid 100/gid 101 with mode 0400. `CREATOR_USERNAME` is not secret and remains an environment value. Development may continue to use direct environment values, but a direct value and its matching `_FILE` setting must never be configured together.