Community Recipes simplification #688

New Issue

ineiti · 2026-03-05T10:45:39Z

ineiti commented

2026-03-05 10:45:39 +00:00

The current sign-up for recipes makes it difficult to have your own recipes. Some reasons you might not want to sign up on https://git.coopcloud.tech/coop-cloud :

testing recipes, and not wanting to commit to support them for a longer time
forking an existing recipe and keeping updated with the original recipe

I see value in curated recipes on https://git.coopcloud.tech/coop-cloud, but there is also value in an easier onboarding process. I can think of two possibilities:

something like crates.io or npm.org where everybody can sign up and publish their new recipe
extending abra app new to accept an URL with git@ and https:// protocols

Now that I think about it, I like 2. very much: the default abra app new appname can go to git@git.coopcloud.tech/coop-cloud/appname, which is the curated list of recipes. But if I want to add a recipe to my project, I can then use abra app new git@cloudforge.org/ineiti/danu/coop/node and create a new app for a danu-node.

The current sign-up for recipes makes it difficult to have your own recipes. Some reasons you might not want to sign up on https://git.coopcloud.tech/coop-cloud : - testing recipes, and not wanting to commit to support them for a longer time - forking an existing recipe and keeping updated with the original recipe I see value in curated recipes on https://git.coopcloud.tech/coop-cloud, but there is also value in an easier onboarding process. I can think of two possibilities: 1. something like crates.io or npm.org where everybody can sign up and publish their new recipe 2. extending `abra app new` to accept an URL with `git@` and `https://` protocols Now that I think about it, I like `2.` very much: the default `abra app new appname` can go to `git@git.coopcloud.tech/coop-cloud/appname`, which is the curated list of recipes. But if I want to add a recipe to my project, I can then use `abra app new git@cloudforge.org/ineiti/danu/coop/node` and create a new app for a danu-node.

👍 1 ❤️ 1

decentral1se commented

2026-03-05 11:23:59 +00:00

extending abra app new to accept an URL with git@ and https:// protocols

You can just clone your own recipe to $ABRA_DIR/recipes and then abra app new will do what you want. I would welcome a patch to clone directly from a URL. This would then be some sort of "syntactic sugar" on that manual workflow? Good Idea ™️

The current sign-up for recipes makes it difficult to have your own recipes

Probably under-documented, but you can already avoid it: https://docs.coopcloud.tech/operators/handbook/#remote-recipes abra will try to respect local tags that are not present in the catalogue. There may be edge-case, please let us know how you get on and report issues. I'd love to make it more visible how you can not rely on git.coopcloud.tech. This has been an open issue for ages: #139

> extending abra app new to accept an URL with git@ and https:// protocols You can just clone your own recipe to `$ABRA_DIR/recipes` and then `abra app new` will do what you want. I would welcome a patch to clone directly from a URL. This would then be some sort of "syntactic sugar" on that manual workflow? Good Idea ™️ > The current sign-up for recipes makes it difficult to have your own recipes Probably under-documented, but you can already avoid it: https://docs.coopcloud.tech/operators/handbook/#remote-recipes `abra` will try to respect local tags that are not present in the catalogue. There may be edge-case, please let us know how you get on and report issues. I'd love to make it more visible how you can not rely on git.coopcloud.tech. This has been an open issue for ages: https://git.coopcloud.tech/toolshed/organising/issues/139

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/organising#688