Self-deploy: update + tags

[chfritz]

Make it easier for people who self-deploy to update their deployments, i.e., fetch latest docker-compose.yaml and container images, then re-deploy.

Also add human-readable tags to published images.

[chfritz]

• (maybe) also add auto-build-and-publish (via github actions)?

[chfritz]

We can probably use docker compose's merging to maximize sharing between https://github.com/transitiverobotics/transitive/blob/main/cloud/docker-compose.yaml and the docker-compose.yaml file used in self-hosting.

[chfritz]

• add deploy script to transitive repo not necessary now that it pulls most things at run-time
• update instructions to fetch it from github directly
• make it reentrant, i.e., also serve as an update script:
  • don't abort if DB exists, just don't re-write .env in that case
  • refetch the latest version of (the shared part of) docker-compose.yaml
• split cloud/docker-compose.yaml into two parts: one that is shared with deploy and the rest.
  • update dev.sh accordingly

Can we test this in an lxc container?

[chfritz]

Re. lxc:

To run docker inside a container first update the config:

lxc config set u20 security.privileged true
lxc config set u20 security.nesting true

(here u20 is the container name).

Install docker compose plugin: https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository

[chfritz]

Some notes about all the four modes we want to enable with maximum reuse of docker-compose rules: https://github.com/transitiverobotics/transitive/wiki

[chfritz]

Deploy order:

• merge branch
• git fetch && git checkout origin/main
• git tag v1.0.0 && git push --tags
• publish to dockerhub
• if it all worked: commit changes to publish script

[chfritz]

Done in https://github.com/transitiverobotics/private/commit/94ef9900b659f68c00c58266bf453a596d652b11 and 5c92c86