Since this is wider than this repo, let's keep the ball rolling on compose-stacks/planning#18.
If we do this we can sunset all the *.autonomic.zone repositories and move to this compose-stacks config /coop-cloud-apps env situation. That would make it easier to focus on a single config and keep it up-to-date.
With the caveat that we'll have to take care of manual deployments for a bit if we do this, I'm well up for moving to the monorepo setup. Do we want to maybe have a plan for keeping our CD going? I might have a poke around now...
This is actually what I did in the first iteration of trying out Gitea with Dokku. I found it tricky to manage because you have to setup a user account and a script to do the SSH connection threading. This more connection to the actual host filesystem which is will be problematic for migrations. Unless you see some drawback of this, I would stick with it, the internal SSH server is quite convenient IMHO.