simon/docs.coopcloud.tech
0
0
Fork 0
forked from toolshed/docs.coopcloud.tech
Code Pull Requests Activity

docs: mooooooar version handling wording

Browse Source
This commit is contained in:
decentral1se
2025-01-02 16:18:17 +01:00
parent 2f7d23b208
commit e9861c5d55
1 changed files with 16 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
docs/operators/handbook.md
View File

@ -545,13 +545,14 @@ with `[version]` `--chaos/-C` or `--ignore-env-version/-i`.
This is the most flexible command so it can be hard to follow. It is possible This is the most flexible command so it can be hard to follow. It is possible
to deploy the following kinds of versions with `abra app deploy`: to deploy the following kinds of versions with `abra app deploy`:
1. latest release version (standard `abra app deploy`) 1. latest recipe version (standard `abra app deploy`)
2. version retrieved from the app `.env` (`TYPE=custom-html:1.7.1+1.27.2`) 2. version retrieved from the app `.env` (`abra app deploy` + `TYPE=custom-html:1.7.1+1.27.2`)
3. latest commit (`--chaos/-C` / no released recipe versions) 3. latest commit (`--chaos/-C` / `abra app deploy` + no released recipe versions)
4. latest commit with unstaged changes (`--chaos/-C`) 4. latest commit with unstaged changes (`abra app deploy --chaos/-C`)
5. recipe version or Git hash (`abra app deploy 1.7.1+1.27.2`) 5. recipe version or Git hash (`abra app deploy 1.7.1+1.27.2`)
The app `.env` version is used as the recipe checkout version. The app `.env` version is always used as the recipe checkout version if
present.
For 2), if the app **is undeployed** and there is an app `.env` version For 2), if the app **is undeployed** and there is an app `.env` version
present, then it will be used. This is the *only time* the app `.env` version present, then it will be used. This is the *only time* the app `.env` version
@ -569,9 +570,11 @@ The app must be deployed already to proceed.
* a specific upgrade (`abra app upgrade 1.7.1+1.27.2`) * a specific upgrade (`abra app upgrade 1.7.1+1.27.2`)
* force re-upgrade (same version, `abra app upgrade --force`) * force re-upgrade (same version, `abra app upgrade --force`)
The app `.env` version is used as the recipe checkout version. However, it is The app `.env` version is always used as the recipe checkout version if
otherwise **ignored** for the version candidate. The "source of truth" for the present.
version candidate is the live deployment of the app.
However, it is otherwise **ignored** for the version candidate. The "source of
truth" for the version candidate is the live deployment of the app.
### `abra app rollback` ### `abra app rollback`
@ -581,6 +584,8 @@ The app must be deployed already to proceed.
* a specific downgrade (`abra app rollback 1.7.1+1.27.2`) * a specific downgrade (`abra app rollback 1.7.1+1.27.2`)
* force re-downgrade (same version, `abra app rollback --force`) * force re-downgrade (same version, `abra app rollback --force`)
The app `.env` version is used as the recipe checkout version. However, it is The app `.env` version is always used as the recipe checkout version if
otherwise **ignored** for the version candidate. The "source of truth" for the present.
version candidate is the live deployment of the app.
However, it is otherwise **ignored** for the version candidate. The "source of
truth" for the version candidate is the live deployment of the app.