WIP feat: introduce local recipes #742

What happens with a local recipe that doesn't exist in the catalogue? It would be good to write some integration tests indeed that don't just test the direct functionality but also how a local recipe behaves with all the usual commands (abra app deploy, upgrade, etc.). It would be good to adjust some existing tests and make the recipe local and see what explodes.

Thanks, sounds good to me! People have asked for it also several times. What happens with a local recipe that doesn't exist in the catalogue? It would be good to write some integration tests indeed that don't just test the direct functionality but also how a local recipe behaves with all the usual commands (`abra app deploy`, `upgrade`, etc.). It would be good to adjust some existing tests and make the recipe local and see what explodes.

pkg/recipe/recipe.go

						
				@ -133,0 +128,4 @@

					sshURL := ""

					dir := ""

					local := false

					if strings.HasPrefix(name, "./") {

decentral1se commented

2026-02-02 14:29:37 +00:00

This needs a docs patch for https://docs.coopcloud.tech/maintainers/handbook/ to explain how you create a "local only" recipe. We have too often created features which go undiscovered for years 🙃 Docs might help avoid this...

pkg/recipe/recipe.go

						
				@ -133,0 +129,4 @@

					dir := ""

					local := false

					if strings.HasPrefix(name, "./") {

						dir = path.Join(config.ABRA_DIR, name)

decentral1se commented

2026-02-02 14:27:42 +00:00

we should also check if the local recipe dir exists.

ammaratef45 commented

2026-02-02 14:37:05 +00:00

The feature makes sense to me, unsure from reading the code but it seems like local recipes will use whatever exists in the directory, so it won't look for a release tag

I wonder if local recipes should also be expected to be a git directory but without the need for a remote (one can exist but abra won't need it)

wdyt?

The feature makes sense to me, unsure from reading the code but it seems like local recipes will use whatever exists in the directory, so it won't look for a release tag I wonder if local recipes should also be expected to be a git directory but without the need for a remote (one can exist but abra won't need it) wdyt?

👍 1

continuous-integration/drone/pr Build is failing

Details

This pull request has changes conflicting with the target branch.

pkg/app/app.go

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u local-recipes:p4u1-local-recipes

git checkout p4u1-local-recipes

Sign in to join this conversation.

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/abra#742

Allow edits from maintainers