Updated the list and closing this, because we don't have active production services left to switch. Except for Mastodon, but that'll be a whole topic unto itself (and as discussed before, likely requires to set up a whole new instance and moving all accounts).
I also took a look at https://gitea.kosmos.org/kosmos/gitea.kosmos.org, I think we can delete the entire repo, it is all specific to the instance we were running on GKE
Nope, a lot of the issues are still valid. But we can close a whole bunch of them now.
That's right, I will move this checklist to the issue instead
Maybe should have moved the response to my question there as well. ;)
As we're importing a database dump, the /home/git/.ssh/authorized_keys file on centaurus will be empty at first, this admin task generates the content of the file with users’ public key. It is then managed by Gitea, so new keys are automatically added, deleted keys deleted, etc
Yes, that's obvious from the original post. But what is this task? It is just English text in your post, but is it a script somewhere? How is it run?
Sounds good!
I think the only thing that is not clear to me is:
Log in, run
Update the '.ssh/authorized_keys' file with Gitea SSH keyson http://gitea.kosmos.org/admin
