Support multiple app catalogues #139
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#139
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
So folks don't have to rely on https://recipes.coopcloud.tech.
Will support using own set of releases, recipes etc.
Could support multiple? "official" / "custom" / etc. Unsure.
#321 is related.
Some points while they're flying around in my head:
This could fit into #303 perhaps? You could specify which catalogue you want to target and read from there? This might be easy to specify a new catalogue but not multiple?
We could support
~/.abra/cataogues.d/...
where people can just clone in some directory that has a convention ofcatalogue.json
or something. Then askabra
to merge all those files and present the catalogue internally? How do we deal with conflicting versions though?abra
still internally polls git.coopcloud.tech for the recipes listing to build the catalogue onabra catalogue generate
and also elsewhere, i believe. this would need a investigation to see how to consolidate catalogue reading into once place that is then pluggable for new catalogues? Unknown.Some hardcoded stuff
5739758c3a/pkg/config/env.go (L23-L26)
😬Like from the high level, we need:
whatever)
recipes
can override anything to do with that with --chaos at all times.Re-discussed this with @p4u1 again today and #303 definitely seems like a prerequisite for getting this done because we need to be able to define the alternate catalogues URLs (Git or otherwise).