docs: Adds local recipe mode to operator and maintainers handbook

docs/abra/trouble.md

@@ -105,4 +105,4 @@ $ git clone https://git.coopcloud.tech/coop-cloud/MyCoolRecipe.git ~/.abra/recip
 
 ## "only updates to Labels are allowed"
 
-See [Packaging handbook » What does "only updates to Labels are allowed" mean](maintainers/handbook/#what-does-only-updates-to-labels-are-allowed-mean).
+See [Packaging handbook » What does "only updates to Labels are allowed" mean](/maintainers/handbook/#what-does-only-updates-to-labels-are-allowed-mean).

docs/federation/resolutions/in-progress/035.md

@@ -3,16 +3,16 @@ title: "Resolution 035: Budget 016: Sutty Website Proposal"
 ---
 
 - Topic: Budget 016: Sutty Website Proposal
-- Date: 2026-01-16
-- Deadline: 2026-01-30
+- Date: 2026-02-12
+- Deadline: 2026-02-26
 - Size: Large
 
 ## Summary
 
 Budget 016 proposes to:
 
-1. Compensate Sutty and Co-op Cloud community members `@edu` & `@eli` 250 USD according to their own proposed compensation.
-1. Compensate `@diatom` for up to 10 hours to participate in the generative process as Co-op Cloud community delegate.
+1. Compensate Sutty and Co-op Cloud community members `@edu` & `@eli` 250 USD (500 USD total) each according to their own proposed compensation.
+1. Compensate `@diatom` for up to 30 hours to participate in the generative process as Co-op Cloud community delegate.
 
 Please see [the full proposal text](https://vvvvvvaria.org/~decentral1se/cc/CoopCloud-2025WebsiteProposal-Sutty.pdf) for more details. See `Capítulo 3 > Resources estimations` for the section regarding financial estimations. The Co-op Cloud community and federation are to be consulted during this process for decision making around choosing a new website proposal. `@diatom` agrees to be a bridge between the work of `@edu`/`@eli` and the Co-op Cloud community.
 
@@ -28,6 +28,6 @@ Please join `#coop-cloud-new-website:autonomic.zone` to participate in this proc
 
 The budget total is:
 
-* 250 USD (216 EUR)
-* 10 hrs * 20 EUR = 200 EUR
-* **Total**: 416 EUR
+* 500 USD (423 EUR)
+* 30 hrs * 20 EUR = 600 EUR
+* **Total**: 1023 EUR

docs/federation/resolutions/in-progress/037.md

@@ -0,0 +1,26 @@
+---
+title: "Resolution 037: Adopt alakazam as an official project in the Co-op Cloud Federation"
+---
+
+- Topic: Resolution 037: Adopt alakazam as an official project in the Co-op Cloud Federation
+- Date: 12-02-2026
+- Deadline: 26-02-2026
+- Size: medium
+
+## Summary
+
+We want to adopt the abra wrapper Alakazam (https://git.coopcloud.tech/moritz/alakazam) , which is used by KolliCloud (https://kollicloud.de) as an official project in the Co-op Cloud Federation
+
+## Details
+
+As we already disscussed on our Meetup and the Alakazam workshop at 39C3 end of 2025, we want to adopt the abra wrapper Alakazam (https://git.coopcloud.tech/moritz/alakazam), which is used by KolliCloud (https://kollicloud.de) as an official project in the Co-op Cloud Federation. This way, we want to start collaborative effort on teaching, writing docs, writing tests.
+
+This includes the following (in the long run):
+
+* tranfering the Alakazam repository to https://git.coopcloud.tech/toolshed
+* creating a space in the docs for alakazam and moving the contents of the readme and the nessecary contents of https://wiki.local-it.org/s/kollicloud-wiki/doc/installation-wVp2LfBbg7
+* get others to try alakazam (future Kite-Flying sessions for this)
+* write tests for alakazam
+* implement the option to use more than one deployment of the same application in one instance
+* migrate alaconnect.yml files for the recipe (we have to figure out how multiple instances would allow this in regards to the multiple same apps in one instance)
+* migrate the features (that makes sense) into abra

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

docs/operators/tutorial.md

@@ -262,7 +262,6 @@ abra app deploy <nextcloud-domain>
 ```
 abra app ps -w <nextcloud-domain>     # status check
 abra app logs <nextcloud-domain>      # logs trailing
-abra app errors -w <nextcloud-domain> # error catcher
 ```
 
 Your new `traefik` instance will detect that a new app is coming up and generate TLS certificates for it. You can see what `traefik` is up to using the same commands above but replacing `<nextcloud-domain>` with the `<traefik-domain>` you chose earlier (`abra app ls` will remind you what domains you chose :grinning:).

mkdocs.yml

@@ -96,7 +96,6 @@ nav:
           - federation/resolutions/index.md
           - "Draft":
               - federation/resolutions/index.md
-              - federation/resolutions/draft/035.md
           - "Passed":
               - federation/resolutions/passed/001.md
               - federation/resolutions/passed/002.md
@@ -136,6 +135,8 @@ nav:
               - federation/resolutions/stalled/030.md
           - "In Progress":
               - federation/resolutions/index.md
+              - federation/resolutions/in-progress/035.md
+              - federation/resolutions/in-progress/037.md
       - "Minutes":
           - federation/minutes/index.md
           - "Recently":