Consolidating infra on coopcloud-* servers #387
Closed
opened 2023-01-22 08:47:43 +00:00 by decentral1se
·
9 comments
Labels
Clear labels
abra
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
design
documentation
duplicate
enhancement
fedi
fedi-infra
finance
funding
good first issue
help wanted
installer
legal
performance
proposal
question
security
test
wontfix
Everything to do with abra
Ping/pong on comms
Something is not working
Go build related issues
Getting the robots into the mix
Opening this thing up
Contributors stuff
Our main website
Design thinking required
Let's write things together
This issue or pull request already exists
New feature
Democratic decision making
Money things
Anything related to grant funding
Easy start with development
Need some help
Installation related issues
Performance related
Large change which requires feedback & decisin making
More information is needed
Securing our shit
Unit or integration test suite
This won't be fixed
No labels
documentation
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
BornDeleuze
Brooke
carla
cas (Cassowary)
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
iexos
jade (Jade Ambrose)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
moosemower
moritz
notplants
oxaliq (sorrel)
p4u1
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
renovate-bot (Comrade Renovate Bot)
ripclap
simon
sixsmith (Sixsmith)
stevensting
trav (Trav Fryer)
val (val (he/him))
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/organising#387
Reference in New Issue
Block a user
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.
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.
I think we just need to document this somewhere on the fedi docs and it's good to close?
The situation has vastly improved with https://git.coopcloud.tech/toolshed/coop-cloud-apps also.
2025 State of The Co-op Cloud Infra:
swarm-0.coopcloud.techswarm-0.coopcloud.techswarm-0.coopcloud.techswarm-0.coopcloud.techswarm-0.coopcloud.techswarm-0.coopcloud.techswarm-0.coopcloud.techswarm-0.coopcloud.techswarm-1.coopcloud.techswarm-1.coopcloud.techYeah I'd say we're groovy, slap this in the docs and run?