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

docs: version warning and drop --ignore-env-version

Browse Source
This commit is contained in:
decentral1se
2025-08-29 17:03:04 +02:00
parent 34ade7e58c
commit 395b52691f
2 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/maintainers/handbook.md
View File

@ -413,7 +413,7 @@ You can also add release notes for the next release into a special file `release
!!! warning "Watch out for old versions of `abra` 🚧" !!! warning "Watch out for old versions of `abra` 🚧"
This feature is only available in the > 0.9.x series of `abra`. This feature is only available in the >= 0.9.x series of `abra`.
## How do I know whether to accept version upgrades when running `abra recipe upgrade <something>`? ## How do I know whether to accept version upgrades when running `abra recipe upgrade <something>`?

12
docs/operators/handbook.md
View File

@ -512,7 +512,7 @@ abra app secret insert localhost ssl_key v1 localhost.key -f
!!! warning "Watch out for old versions of `abra` 🚧" !!! warning "Watch out for old versions of `abra` 🚧"
This feature is only available in the > 0.10.x series of `abra`. This feature is only available in the >= 0.10.x series of `abra`.
It is possible to specify a remote recipe in your `.env` file: It is possible to specify a remote recipe in your `.env` file:
@ -532,7 +532,7 @@ $ABRA_DIR/recipes/mygit_org_myorg_cool-recipe
!!! warning "Watch out for old versions of `abra` 🚧" !!! warning "Watch out for old versions of `abra` 🚧"
This feature is only available in the > 0.10.x series of `abra`. This feature is only available in the >= 0.10.x series of `abra`.
If you `abra app new`/`abra app deploy`/`abra app upgrade`/`abra app rollback`, If you `abra app new`/`abra app deploy`/`abra app upgrade`/`abra app rollback`,
the version that is deployed will be written to your app `.env` file. You can the version that is deployed will be written to your app `.env` file. You can
@ -553,13 +553,13 @@ TYPE=custom-html:1.7.1+1.27.2
This `.env` version is then used as the recipe checkout version for **all** This `.env` version is then used as the recipe checkout version for **all**
`abra` operations afterwards unless you specify otherwise on the command-line `abra` operations afterwards unless you specify otherwise on the command-line
with `[version]` `--chaos/-C` or `--ignore-env-version/-i`. with `[version]` `--chaos/-C` or `--latest/-l`.
## How is the new deployment version determined? ## How is the new deployment version determined?
!!! warning "Watch out for old versions of `abra` 🚧" !!! warning "Watch out for old versions of `abra` 🚧"
This feature is only available in the > 0.10.x series of `abra`. This feature is only available in the >= 0.10.x series of `abra`.
### `.env` version ### `.env` version
@ -569,7 +569,7 @@ deployment overview.
This `.env` version is then used as the recipe checkout version for **all** This `.env` version is then used as the recipe checkout version for **all**
`abra` operations afterwards unless you specify otherwise on the command-line `abra` operations afterwards unless you specify otherwise on the command-line
with `[version]` `--chaos/-C` or `--ignore-env-version/-i`. with `[version]` `--chaos/-C` or `--latest/-l`.
### `abra app deploy` ### `abra app deploy`
@ -592,7 +592,7 @@ The version is chosen using the following priority logic.
1. deployed app 1. deployed app
1. recipe catalogue (if undeployed) 1. recipe catalogue (if undeployed)
Use `--ignore-env-version/-i` to deploy the latest release version or commit. Use `--latest/-l` to deploy the latest release version or commit.
In all cases 3-5, the app `.env` version is **ignored** as a version candidate. In all cases 3-5, the app `.env` version is **ignored** as a version candidate.