toolshed/docs.coopcloud.tech
3
2
Fork 27
Code Issues 10 Pull Requests 1 Packages Releases Activity

fix: wording, typos
All checks were successful
continuous-integration/drone/push Build is passing
Details

Browse Source
This commit is contained in:
decentral1se
2026-03-21 17:29:43 +01:00
parent db8c54bd11
commit 99bc41a621
1 changed files with 11 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/maintainers/upgrade.md
View File

@ -32,22 +32,24 @@ And in the [`abra.sh`](https://git.coopcloud.tech/coop-cloud/traefik/src/commit/
export TRAEFIK_YML_VERSION=v29
```
If you update teh `traefik.yml.tmpl` with new changes, you **must** increment
If you update the `traefik.yml.tmpl` with new changes, you **must** increment
`TRAEFIK_YML_VERSION`. Otherwise, other Co-op Cloud operators will see an
obscure error message when they try to deploy your new version.
## Backwards compatible environment variable changes
If you add a new environment variable to the `.env.sample` then you create
manual upgrade work for other Co-op Cloud operators. Depending on the
functionality that the environment variable enables or how the recipe is
already configured, it is possible to provide a default which maintains
backwards compatibility. There is hard and fast rule for this and it depends on
the recipe and context.
If you add a new environment variable to the `.env.sample` then you can
potentially create manual upgrade work for other Co-op Cloud operators.
Depending on the functionality that the environment variable enables or how the
recipe is already configured, it is possible to provide a default which
maintains backwards compatibility. There is no hard and fast rule for this and it
depends on the recipe and context.
A typical way to do this, is to provide a default in the `environment` stanza.
For example, providing a default of `false` for `NEW_ENV_VARS` so Co-op Cloud
operators do not need to set `NEW_ENV_VAR=false` in their app `.env` file.
For example, providing a default of `false` for a new fictitous environment
variable called `NEW_ENV_VAR` so other Co-op Cloud operators do not need to set
`NEW_ENV_VAR=false` in their app `.env` file (unless they want to change it).
```yaml
environment: