Consider migrating Recipes to own Gitea organization #569

New Issue

basebuilder · 2024-02-06T14:10:30Z

basebuilder commented

2024-02-06 14:10:30 +00:00

So instead of: https://git.coopcloud.tech/coop-cloud/wordpress
It wold be https://git.coopcloud.tech/recipes/wordpress

I think this would achieve a few things:

Drive home point that- these things are decoupled from the CC tools and are useful as standalone commons code
Clearly delineate the Co-op Cloud apps, tools, websites from recipes
Minimize number of repos to grok what CC is, for those wanting to contribute to CC the project (beyond recipes)
Makes the URL more explicit in what it is (a la REST naming conventions)
Perhaps minimize code that does the recipes list generation by just querying Gitea for that recipes organization
The branding name association of coop-cloud will be unaffected as that's in the domain name.

So instead of: `https://git.coopcloud.tech/coop-cloud/wordpress` It wold be `https://git.coopcloud.tech/recipes/wordpress` I think this would achieve a few things: 1. Drive home point that- these things are decoupled from the CC tools and are useful as standalone commons code 2. Clearly delineate the Co-op Cloud apps, tools, websites from recipes 3. Minimize number of repos to grok what CC is, for those wanting to contribute to CC the project (beyond recipes) 4. Makes the URL more explicit in what it is (a la REST naming conventions) 5. Perhaps minimize code that does the recipes list generation by just querying Gitea for that recipes organization 6. The branding name association of `coop-cloud` will be unaffected as that's in the domain name.

👍 1 👀 1

basebuilder added the

community organising

awaiting-feedback

recipes.coopcloud.tech

labels 2024-02-06 14:14:10 +00:00

decentral1se commented

2024-02-06 14:26:42 +00:00

Related to point 5 is #377 which probably would be solved by this. I'm kind out of ideas about how to fix this recipe list generation, so, tbh, this would make that easier.

I really shudder to think of the amount of churn this would cause... 🙈 Perhaps if we renamed the current coop-cloud org to recipes then Gitea would handle the re-direct? Then creating a new separate coop-cloud organisation again afterwards? Probably something breaks anyway.

Related to point 5 is https://git.coopcloud.tech/coop-cloud/organising/issues/377 which probably would be solved by this. I'm kind out of ideas about how to fix this recipe list generation, so, tbh, this would make that easier. I really shudder to think of the amount of churn this would cause... 🙈 Perhaps if we renamed the current `coop-cloud` org to `recipes` then Gitea would handle the re-direct? Then creating a new separate `coop-cloud` organisation again afterwards? Probably something breaks anyway.

basebuilder commented

2024-02-06 15:20:33 +00:00

I really shudder to think of the amount of churn this would cause... 🙈

Perhaps with a 301 redirect rule in proxy (if Gitea doesn't support it) and then make abra have a --ff-redirect flag could work?

Perhaps if we renamed the current coop-cloud org to recipes

I was thinking about this while out for a walk. Yah maybe renaming Gitea does some undocumented (by my search) redirect 🤔 we make new org named tools or something.

> I really shudder to think of the amount of churn this would cause... 🙈 Perhaps with a 301 redirect rule in proxy (if Gitea doesn't support it) and then make `abra` have a `--ff-redirect` flag could work? > Perhaps if we renamed the current `coop-cloud org` to recipes I was thinking about this while out for a walk. Yah maybe renaming Gitea does some undocumented (by my search) redirect 🤔 we make new org named `tools` or something.

decentral1se referenced this issue

2024-03-29 09:09:05 +00:00

New abra release planning #583

decentral1se referenced this issue

2024-03-29 09:09:14 +00:00

Performance issue with retrieving recipes #377

basebuilder referenced this issue

2024-04-02 09:04:00 +00:00

Create HTTP web service which generates Recipes Catalogue dynamically #604

basebuilder referenced this issue

2024-04-02 09:04:49 +00:00

Retiring recipes #603

3wordchant commented

2024-04-02 22:59:03 +00:00

Huge support for this plan @basebuilder, I previously opened this as #377 before that was renamed / refocused on performance problems.

Perhaps with a 301 redirect rule in proxy (if Gitea doesn't support it)
Yah maybe renaming Gitea does some undocumented (by my search) redirect

Gitea does HTTP redirects from moved repos (or probably renamed orgs?) by default, but:

Sad news, Gitea doesn't handle either transferring a repo or renaming an org very well with SSH connections - Gitea: Unauthorized in both cases.
#377-15011

RE @decentral1se's comment in #256 (#256-20291), I think moving SSH remotes is "not too bad" on reflection, a bash one-liner should do it for those of us who don't want to drop our whole .abra/recipes dir, redownloading it should work for the rest.

BUT!

Any way anyone can think of to migrate Drone configs (and ideally build history) en masse? 🤔

Huge support for this plan @basebuilder, I previously opened this as #377 before that was renamed / refocused on performance problems. > Perhaps with a 301 redirect rule in proxy (if Gitea doesn't support it) > Yah maybe renaming Gitea does some undocumented (by my search) redirect Gitea does HTTP redirects from moved repos (or probably renamed orgs?) by default, but: > Sad news, Gitea doesn't handle either transferring a repo or renaming an org very well with SSH connections - Gitea: Unauthorized in both cases. > [#377-15011](https://git.coopcloud.tech/coop-cloud/organising/issues/377#issuecomment-15011) RE @decentral1se's comment in #256 ([#256-20291](https://git.coopcloud.tech/coop-cloud/docs.coopcloud.tech/pulls/256#issuecomment-20291)), I think moving SSH remotes is "not too bad" on reflection, a bash one-liner should do it for those of us who don't want to drop our whole `.abra/recipes` dir, redownloading it should work for the rest. BUT! Any way anyone can think of to migrate Drone configs (and ideally build history) en masse? 🤔

❤️ 1

basebuilder commented

2024-04-03 05:47:28 +00:00

Perhaps it would be not so much effort to make something like:

$ abra migration 001

Which would then useful for future cases of "good idea, but oh noes, this will suck for Reason X" ??

Perhaps it would be not so much effort to make something like: ``` $ abra migration 001 ``` Which would then useful for future cases of *"good idea, but oh noes, this will suck for Reason X"* ??

decentral1se commented

2024-04-04 08:51:39 +00:00

@basebuilder pure gold! ~/.abra/migrations perhaps which could then be BASH SCRIPTS to be executed. We could have some UI to say "check this shit yall before running because we are about to do shit on your local" and point to the file?

@basebuilder pure gold! `~/.abra/migrations` perhaps which could then be **BASH SCRIPTS** to be executed. We could have some UI to say "check this shit yall before running because we are about to do shit on your local" and point to the file?

🚀 1

decentral1se referenced this issue from coop-cloud/docs.coopcloud.tech

2024-04-04 08:54:38 +00:00

wip: docs: march resolutions #256

basebuilder added this to the Project Gitea Re-organisation milestone 2024-04-15 07:06:22 +00:00

Sign in to join this conversation.