I’ve been trying to figure this part out for a few days. I have my own Forgejo instance and a website each running in separate containers on a Raspberry Pi. I also have the forgejo runner installed in another docker container. I followed some guides to set up forgejo actions, but all the guides end with a simple example that basically just runs the “ls” command.
I tried running ‘docker compose up’ inside my workflow, but it fails with “docker: command not found”. So how do you use the workflow to actually update the website in the other container?
I think I’d prefer keeping everything in docker but I’d be okay with making the workflow run some script on the host machine if needed.
ZeroGravitas@lemmy.dbzer0.com
nykula@piefed.social 3 hours ago
I have podman-compose on host. A single compose.yaml declares all images that should run and depend on each other. Then there’s a single .env file for config. A systemd user service runs
podman-compose upwith that .env file. A cron job periodically runs podman-compose pull, stops the systemd service, backups volumes and starts the systemd service back again. For the web app I write, its CI builds a Docker image and pushes it to the Codeberg registry, from which podman-compose picks it up. It’s very far from instant deploy, but works for my needs.