Register your interest here if you’d like to join a team of smaller instance admins backing each other up. So if it’s the middle of the night or we’re on vacation, someone we trust from the federation of small instance administrators can secure our sites if we’re unavailable.
Idea, make that time zone UTC. People around the world have no idea of what “MT” is and even if we had to pick a US timezone (which no, we shouldn’t) MT is probably the least known one.
good idea thanks. done.
I got around to filling in the form
helllll ya
Hi,
Can you explain logistically how this works. Eg: You are my ‘backup’. A vulnerability is deiscovered requiring lemmy to be updated.
What is the process that occurs?
P
I’m replying from the balcony of my cruise ship so I’m unable to give this response the detail it deserves. And, we’d need to decide this as a group. But essentially as my backup, if there’s an incident requiring a prompt action and I’m unreachable, you’d have credentials to do the needful.
Maybe we use a shared spreadsheet to track instance statuses including an in/out status for the primary admin. So if there’s a new vulnerability, it’s unpatched on the instance and the primary is out, the backup or the backup to the backup handles it.
Interesting. I use docker compose so would be able to assist other people using a similar setup. I feel there would need to be a document that specifies what to do and what is expected if something goes wrong.
definitely, and since we’ve realized we’re running the same images, it may not be a bad idea to team up around similar deployments. For instance I might as well standardize on the easy deploy project. I’m using ansible now but modified it to use ubergeek’s arm64 images. might as well just use his whole project.
I will somehow post how to do things do you can see how it works before you decide. Its pretty basic.
