Create HTTP web service which generates Recipes Catalogue dynamically #604
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#604
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?
I mentioned to @decentral1se last week the idea of generating the
recipes-catalogue-json
in a new fashion which is dynamically via a minimal HTTP server which could be found atrecipes.coopcloud.tech/api
or such.If I understand correctly, the current flow revolves around manually running
abra catalogue generate
and committing that to the repo and pushing it. My proposal, I think, would allow that to just happen automagically whenever a new recipe version is published.This would benefit from migration to
coopcloud.tech/recipes
organization detailed in #569 and possibly relate to #599 and also benefit #603Thanks for opening! Under "Operator Collaboration / General Version Improvement" on #583 and in the last fedi meeting (notes: https://docs.coopcloud.tech/federation/minutes/2024-03-29/) we touched on a few ways that we could remove the need for the catalogue repository requirement on the
abra
side. But we didn't have an answer for how to still provide pre-computed data for catalogue web UI. This/api
could deffo sort this. And I'm curious on the overlap between ideas of @p4u1 and your ideas @basebuilder. Hopefully to be discussed at the next fedi meeting 🎉It's already automatic for some (many? most?) recipes.
abra recipe sync wordpress
/abra recipe release wordpress
→ generates and pushes a git tagauto-recipes-catalogue-json
auto-recipes-catalogue-json
rebuilds the catalogue and makes a commit torecipes-catalogue-json
There's also a daily Drone job which runs
auto-recipes-catalogue-json
which will pick up recipes which don't have thedrone/downstream
step (either ones created not usingabra recipe new
/ the repo template, or older recipes which didn't have that step added afterwards).The main issues I see with the current set-up are:
Copying the above comment into the TODO on Maintainer Handbook could be a start towards addressing (1).
For (2), I think it would be interesting to understand more about the use-cases for 3rd-party recipe catalogues, and maybe make some more progress on the recipe-generation code itself first (i.e. how could we make
abra catalogue generate
work if.abra/recipes
contains recipes which aren't in git.coopcloud.tech/coop-cloud).