To follow https://git.coopcloud.tech/coop-cloud/recipes naming and to avoid ambiguity with "apps" vs. "recipes". Think we discussed this before at some point but never made a ticket. Maybe recipes.coopcloud.tech for this repository name? Or "recipes-catalogue" or whatevs.
To follow https://git.coopcloud.tech/coop-cloud/recipes naming and to avoid ambiguity with "apps" vs. "recipes". Think we discussed this before at some point but never made a ticket. Maybe `recipes.coopcloud.tech` for this repository name? Or "recipes-catalogue" or whatevs.
Love it! And maybe we can seize this moment to specify that recipes.coopcloud.tech loads this catalogue, recipes.coopcloud.tech/recipes.json loads the JSON from coop-cloud/recipes? Could use a Path routing rule in Traefik to achieve that, I think.
Love it! And maybe we can seize this moment to specify that `recipes.coopcloud.tech` loads this catalogue, `recipes.coopcloud.tech/recipes.json` loads the JSON from coop-cloud/recipes? Could use a `Path` routing rule in Traefik to achieve that, I think.
I'm being a bit chaotic as usual but this repo is now called recipes.coopcloud.tech and I guess it will live on https://recipes.coopcloud.techas the nicely designed catalogue web UI (and https://recipes.coopcloud.tech/recipes.json will be the machine-readable format forabra`).
I'm being a bit chaotic as usual but this repo is now called `recipes.coopcloud.tech` and **I guess** it will live on https://recipes.coopcloud.tech` as the nicely designed catalogue web UI (and https://recipes.coopcloud.tech/recipes.json will be the machine-readable format for `abra`).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
To follow https://git.coopcloud.tech/coop-cloud/recipes naming and to avoid ambiguity with "apps" vs. "recipes". Think we discussed this before at some point but never made a ticket. Maybe
recipes.coopcloud.techfor this repository name? Or "recipes-catalogue" or whatevs.Love it! And maybe we can seize this moment to specify that
recipes.coopcloud.techloads this catalogue,recipes.coopcloud.tech/recipes.jsonloads the JSON from coop-cloud/recipes? Could use aPathrouting rule in Traefik to achieve that, I think.Yes, fantastic 🚀
I'm being a bit chaotic as usual but this repo is now called
recipes.coopcloud.techand I guess it will live on https://recipes.coopcloud.techas the nicely designed catalogue web UI (and https://recipes.coopcloud.tech/recipes.json will be the machine-readable format forabra`).Remaining: