this post was submitted on 18 Nov 2026
53 points (100.0% liked)

Selfhosted

63973 readers
1847 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] diecknet@discuss.tchncs.de 2 points 3 days 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).