Issue: https://github.com/processone/ejabberd/issues/3191
Fixed in 00abf5d42c
Updating to 20.03 will fix this
I got Gitea to run in a VM, deployed by Chef. I'm running a postgresql server with TLS, cert generated by Let's Encrypt with the DNS auth, using Gandi like we already do for the XMPP server. I have also successfully used the gitea backup command with the postgresql format, it's cool that it's included
Now I'm researching warm standby
Yeah deploying Gitea without Docker makes more sense, I will do that.
Switching to Postgres also sounds good
I looked into running Gitea and Drone using Docker Compose (we're running Drone CI using Docker Compose at 5apps, but for Kosmos we're using Gitea instead of GitHub for auth)
The part that's a bit tricky is running SSH in Gitea on port 22 on the host machine, I won't have time to finish this today but I'm close
Exporting the data is also straightforward:
kubectl cp gitea-server-#{id}:/data ./backup
I have found instructions to perform a MySQL dump from a GKE node to a local file (https://medium.com/@madushagunasekara/export-mysql-db-dump-from-kubernetes-pod-and-restore-mysql-db-on-kubernetes-pod-6f4ecc6b5a64) and did a successful dump.
I'm now looking into exporting the git repositories from the persistent volume
Running in production, closing this one!
We ran into an issue and had to switch the existing user accounts to the LDAP auth source, with the "Authentication Sign-In Name" for each account being the username
Closing this one now that ejabberd has been upgraded and restarted yesterday. The config change in #141 had not been applied, this has been fixed in #142