toolshed/organising
7
1
Fork 0
Code Issues 100 Pull Requests Releases Activity

Consider migrating Recipes to own Gitea organization #569

New Issue
Closed
opened 2024-02-06 14:10:30 +00:00 by basebuilder · 7 comments
basebuilder commented 2024-02-06 14:10:30 +00:00
Copy Link

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

Related to point 5 is coop-cloud/organising#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
Author
Copy Link

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.
3wordchant commented 2024-04-02 22:59:03 +00:00
Owner
Copy Link

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
Author
Copy Link

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
Owner
Copy Link

@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
basebuilder added this to the (deleted) milestone 2024-04-15 07:06:22 +00:00
decentral1se commented 2024-10-21 15:42:12 +00:00
Owner
Copy Link

Your feedback please!

https://pad.local-it.org/5JBUdyfkQauR5yhJ_IR2xA?both

(Going for the "easy fix" for now with a cosmetic rename!)

Your feedback please! > https://pad.local-it.org/5JBUdyfkQauR5yhJ_IR2xA?both (Going for the "easy fix" for now with a cosmetic rename!)
decentral1se commented 2025-01-03 07:41:03 +00:00
Owner
Copy Link

OK, gonna try the opposite now: moving the non-recipes to their own organisation. So, let's move over to this one to track: #666

OK, gonna try the opposite now: moving the non-recipes to their own organisation. So, let's move over to this one to track: https://git.coopcloud.tech/toolshed/organising/issues/666
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
abra
Everything to do with abra
abra-gandi
Abra Gandi plugin
awaiting-feedback
Ping/pong on comms
backups
bug
Something is not working
build
Go build related issues
ci/cd
Getting the robots into the mix
community organising
Opening this thing up
contributing
Contributors stuff
coopcloud.tech
Our main website
democracy
Democratic decision making
design
Design thinking required
documentation
Let's write things together
duplicate
This issue or pull request already exists
enhancement
New feature
finance
Money things
funding
Anything related to grant funding
good first issue
Easy start with development
help wanted
Need some help
installer
Installation related issues
kadabra
performance
Performance related
proposal
Large change which requires feedback & decisin making
question
More information is needed
recipes.coopcloud.tech
Our recipes catalogue
security
Securing our shit
test
Unit or integration test suite
wontfix
This won't be fixed
No Label
awaiting-feedback
community organising
recipes.coopcloud.tech
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant aadil abra-bot ammaratef45 Apfelwurm carla cas coopcloud cyrnel decentral1se fauno iexos jade jmakdah2 joe-irving kawaiipunk knoflook kolaente lambdabundesverband linnealovespie moritz notplants p4u1 pharaohgraphy renovate-bot ripclap simon sixsmith trav val yksflip
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/organising#569
No description provided.
Delete Branch "%!s()"

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?