forked from toolshed/docs.coopcloud.tech
		
	docs: moar wording
This commit is contained in:
		@ -522,6 +522,10 @@ And after a deployment of version `1.7.1+1.27.2` of the `custom-html` recipe.
 | 
			
		||||
TYPE=custom-html:1.7.1+1.27.2
 | 
			
		||||
```
 | 
			
		||||
 | 
			
		||||
This `.env` version is then used as the recipe checkout version for all `abra`
 | 
			
		||||
ops afterwards unless you specify a version on the command-line (`[version]`),
 | 
			
		||||
use `--chaos/-C` or `--ignore-env-version/-i`.
 | 
			
		||||
 | 
			
		||||
## How is the new deployment version determined?
 | 
			
		||||
 | 
			
		||||
!!! warning "This is only available in the currently unreleased version of `abra`"
 | 
			
		||||
@ -532,9 +536,9 @@ If you `abra app deploy`/`abra app upgrade`/`abra app rollback`, the version
 | 
			
		||||
that is deployed will be written to your app `.env` file. This is shown in the
 | 
			
		||||
deployment overview.
 | 
			
		||||
 | 
			
		||||
This `.env` version is then used as the recipe checkout version for all `abra`
 | 
			
		||||
ops afterwards unless you specify a version on the command-line (`[version]`),
 | 
			
		||||
use `--chaos/-C` or `--ignore-env-version/-i`.
 | 
			
		||||
This `.env` version is then used as the recipe **checkout version** for all
 | 
			
		||||
`abra` ops afterwards *unless* you specify a version on the command-line
 | 
			
		||||
(`[version]`), use `--chaos/-C` or `--ignore-env-version/-i`.
 | 
			
		||||
 | 
			
		||||
### `abra app deploy`
 | 
			
		||||
 | 
			
		||||
@ -553,7 +557,7 @@ selected. This is done to reduce unwanted upgrades (we do not automatically
 | 
			
		||||
choose the latest release).
 | 
			
		||||
 | 
			
		||||
Use `--ignore-env-version/-i` to deploy the latest release version or commit.
 | 
			
		||||
In all cases 3-5, the app `.env` version is **ignored**.
 | 
			
		||||
In all cases 3-5, the app `.env` version is **ignored** as a version candidate.
 | 
			
		||||
 | 
			
		||||
### `abra app upgrade`
 | 
			
		||||
 | 
			
		||||
@ -563,9 +567,9 @@ The app must be deployed already to proceed.
 | 
			
		||||
* a specific upgrade (`abra app upgrade 1.7.1+1.27.2`)
 | 
			
		||||
* force re-upgrade (same version, `abra app upgrade --force`)
 | 
			
		||||
 | 
			
		||||
In all cases, the app `.env` version is **ignored** because the "source of
 | 
			
		||||
truth" for the app deployment is the live deployment of the app. The app `.env`
 | 
			
		||||
will be shown however in the deployment overview.
 | 
			
		||||
In all cases, the app `.env` version is **ignored** as a version candidate
 | 
			
		||||
because the "source of truth" for the app deployment is the live deployment of
 | 
			
		||||
the app. The app `.env` will be shown however in the deployment overview.
 | 
			
		||||
 | 
			
		||||
### `abra app rollback`
 | 
			
		||||
 | 
			
		||||
@ -575,6 +579,6 @@ The app must be deployed already to proceed.
 | 
			
		||||
* a specific downgrade (`abra app rollback 1.7.1+1.27.2`)
 | 
			
		||||
* force re-downgrade (same version, `abra app rollback --force`)
 | 
			
		||||
 | 
			
		||||
In all cases, the app `.env` version is **ignored** because the "source of
 | 
			
		||||
truth" for the app deployment is the live deployment of the app. The app `.env`
 | 
			
		||||
will be shown however in the deployment overview.
 | 
			
		||||
In all cases, the app `.env` version is **ignored** as a version candidate
 | 
			
		||||
because the "source of truth" for the app deployment is the live deployment of
 | 
			
		||||
the app. The app `.env` will be shown however in the deployment overview.
 | 
			
		||||
 | 
			
		||||
		Reference in New Issue
	
	Block a user