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.

  • diecknet@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    2
    ·
    9 hours ago

    I self-host web apps and use Forgejo. I got all my docker compose files in one repo. Works for both: off the shelf apps and self created. For self created apps I use separate repos with the code and Forgejo Actions that build the Docker image and push it to the Forgejo registry. But I don’t deploy the containers with Forgejo Actions. For deployment I use Komodo. Whenever a change to the Docker Compose repo happens, it will re-deploy changed docker compose files. When I initially set it up, this guide here helped me a lot.

    Updates via renovate-bot (also runs in Forgejo Actions).