An alternative approach (inspired by https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html) could be to generate a systemd unit for each package deployment with a Compose app, so that we could use systemctl restart with the name of the package deployment (but with slashes converted to underscores). This would be much more complex to implement, but it would enable us to use systemd for ordering and supervising Compose apps. I'm not sure that is a very salient benefit for the PlanktoScope project at the moment, though.
Currently, the only programmatic way to restart the Docker containers of a Compose app provided by a package deployment is to guess the names of the containers and pass them to the
docker restartcommand, e.g. as in https://github.com/PlanktoScope/PlanktoScope/blob/e3dbfc7ed25da6c0cd5e3159cf6880f3e3abda38/software/node-red-dashboard/flows/adafruithat.json#L7519 . It would be simpler, cleaner, and easier to run ahost restart-apporhost restart-deplsubcommand which automatically does all that work for us, for a given package deployment name.An alternative approach (inspired by https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html) could be to generate a systemd unit for each package deployment with a Compose app, so that we could use
systemctl restartwith the name of the package deployment (but with slashes converted to underscores). This would be much more complex to implement, but it would enable us to use systemd for ordering and supervising Compose apps. I'm not sure that is a very salient benefit for the PlanktoScope project at the moment, though.