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

decentral1se marked this conversation as resolved

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

p4u1 commented

2026-02-08 11:27:30 +00:00

I don't think local recipes should check for git repo. If you want your recipe to be a git repooutside of the recipe catalogue you can already reference that with the full hit URL

For me local recipes should be, just take the files and deploy whatever is there. The upgrade command would then be a no op

Will add documentation in the coming days

I don't think local recipes should check for git repo. If you want your recipe to be a git repooutside of the recipe catalogue you can already reference that with the full hit URL For me local recipes should be, just take the files and deploy whatever is there. The upgrade command would then be a no op Will add documentation in the coming days

👍 1

p4u1 commented

2026-02-13 09:30:42 +00:00

@ammaratef45 @decentral1se I have added documentation toolshed/docs.coopcloud.tech#298

Let's discuss and agree on the feature before I add tests and make abra behave well in all cases

@ammaratef45 @decentral1se I have added documentation https://git.coopcloud.tech/toolshed/docs.coopcloud.tech/pulls/298 Let's discuss and agree on the feature before I add tests and make abra behave well in all cases

❤️ 2

decentral1se commented

2026-02-15 13:50:15 +00:00

Aight, re: toolshed/docs.coopcloud.tech#298 (comment) let's push this out to the next abra release ✅

Aight, re: https://git.coopcloud.tech/toolshed/docs.coopcloud.tech/pulls/298#issuecomment-30601 let's push this out to the next `abra` release ✅

decentral1se referenced this pull request

2026-02-21 23:15:01 +00:00

Don't change recipe checkout on `abra app deploy` if there are unnamed changes #751