Consolidating infra on coopcloud-* servers #387
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/organising#387
Loading…
x
Reference in New Issue
Block a user
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?
Gathering issues from the various repos as I merge stuff:
Do we still want to do this migration?
Can't read either of those issues now 😭
Oh darn, that is sadness, fixed that for now and turned back on the in-repo issue tracker (from the settings!).
thank youuuuu
back to the original question:
Yes! Seems like fairly vital pre-handing-things-over-to-the-federation tidying. I can take a swing this week.
We may wan't to upgrade the server resources as the gitea/drone setup is struggling quite a bit atm imho. Reviews of large PRs are dog slow on the UI and gitea regularly falls over when it sees a couple of parallel PRs. The drone builds used to be faster, would be nice to have them zippier again. Something to discuss when we get there.
I guess local-it could definetly sponsor some drone-runner (or maybe woodpecker?) power!
2024 State of The Co-op Cloud Infra:
swarm-0.coopcloud.techswarm-0.coopcloud.techswarm-0.coopcloud.techswarm-0.coopcloud.techswarm-0.coopcloud.techswarm.autonomic.zoneswarm.autonomic.zoneswarm.autonomic.zoneAs far as I know, nobody outside Autonomic has asked for access to
swarm-0.coopcloud.tech, but should be fine to share that with other federation members if anyone wants?Lastly, the helo@coopcloud.tech and noreply@coopcloud.tech email boxes are hosted on mail.autonomic.zone; think it's fine to share domain-level admin access to that to any federation members who are interested.