Referring to "recipes" for naming #12

Closed
opened 2021-11-09 17:11:08 +00:00 by decentral1se · 4 comments
Owner

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

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

Yes, fantastic 🚀

Yes, fantastic 🚀
Author
Owner

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`).
Owner

Remaining:

  • Change HTML title
  • Change heading
  • Change "About" page
Remaining: - [ ] Change HTML title - [ ] Change heading - [ ] Change "About" page
ej-mitchell self-assigned this 2022-03-24 13:30:57 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/recipes.coopcloud.tech#12
No description provided.