docs: Adds local recipe mode to operator and maintainers handbook

docs/abra/hack.md

@@ -440,10 +440,6 @@ Happy Hacking 🫂
 
 We maintain a fork of [godotenv](https://git.coopcloud.tech/toolshed/godotenv) because we need inline comment parsing for environment files. You can upgrade the version here by running `go get git.coopcloud.tech/toolshed/godotenv@0<COMMID>` where `<commit>` is the latest commit you want to pin to. See [`abra#391`](https://git.coopcloud.tech/toolshed/abra/pulls/391) for more.
 
-### `docker/cli`
-
-We maintain a fork of [docker-cli](https://git.coopcloud.tech/toolshed/docker-cli/) because we needed to [patch port exposing](https://git.coopcloud.tech/toolshed/docker-cli/commit/2fbb22f65866ac97b47e4d47d8f855fee8c98e2a) to fix this [bug](https://github.com/docker/cli/issues/2407). Once the fix was upstreamed we can remove this fork again.
-
 ### `docker/client`
 
 A number of modules in [pkg/upstream](https://git.coopcloud.tech/toolshed/abra/src/branch/main/pkg/upstream) are copy/pasta'd from the upstream [docker/docker/client](https://pkg.go.dev/github.com/docker/docker/client). We had to do this because upstream are not exposing their API as public.

docs/maintainers/handbook.md

@@ -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

docs/operators/handbook.md

@@ -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` 🚧"