Compare commits
1 Commits
val-patch-
...
doc-local-
| Author | SHA1 | Date | |
|---|---|---|---|
| 06b0da12bf |
@ -496,6 +496,10 @@ You can also add release notes for the next release into a special file `release
|
||||
|
||||
This feature is only available in the >= 0.9.x series of `abra`.
|
||||
|
||||
## Can I hack on a local recipe ignoring any git or version state?
|
||||
|
||||
Yes this is possible! Please have a look at [local recipes](/operators/handbook/#local-recipes) on how to specify a local recipe.
|
||||
|
||||
## How do I know whether to accept version upgrades when running `abra recipe upgrade <something>`?
|
||||
|
||||
### Postgres
|
||||
|
||||
@ -558,6 +558,20 @@ will fetch the remote recipe and create a directory for it under `$ABRA_DIR`
|
||||
$ABRA_DIR/recipes/mygit_org_myorg_cool-recipe
|
||||
```
|
||||
|
||||
## Local recipes
|
||||
|
||||
!!! warning "Watch out for old versions of `abra` 🚧"
|
||||
|
||||
This feature is only available in the >= 0.13.x series of `abra`.
|
||||
|
||||
It is possible to specify a local recipe in your `.env` file:
|
||||
|
||||
```
|
||||
RECIPE=./recipes/my-local-recipe
|
||||
```
|
||||
|
||||
This will look for the recipe in `$ABRA_DIR/<path>`. Local recipe mode will ignore any git state and versioning and just take the recipe as it is.
|
||||
|
||||
## Saving the version to the app `.env` file
|
||||
|
||||
!!! warning "Watch out for old versions of `abra` 🚧"
|
||||
|
||||
Reference in New Issue
Block a user