this post was submitted on 18 Apr 2025
60 points (95.5% liked)

Selfhosted

61425 readers
584 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
 

My current picks are Woodpecker CI and Forgejo runners. Anything else that's lightweight and easy to manage?

you are viewing a single comment's thread
view the rest of the comments
[–] possiblylinux127@lemmy.zip 2 points 1 year ago (1 children)
[–] Clearwater@lemmy.world 3 points 1 year ago (1 children)

First of all, I actually do prefer Forgejo Actions over Woodpecker. Once set up, my only problem with it (so far) is almost certainly caused by my infrastructure and isn't inherent to FA itself. Pecker, on the other hand, is quite a bit easier to set up and better documented, but I had that issue where it would disconnect from Forgejo and need a few buttons pressed to fix.

This one is just FA being weird:

If you want to deploy the Runner using Docker, the documentation is poor at best. From both a security and documentation standpoint, having it in its own VM is better, but you can do Docker. You just have to read and figure out more on your own. Reading through the example deployments from the documentation will eventually lead you to something along the lines of this (which I copy-pasted from my deployment rather than search for again):

forgejo-runner:
  image: code.forgejo.org/forgejo/runner:6.3.1
  restart: always
  user: 1000:1000
  environment:
    - DOCKER_HOST=tcp://dind:2376
  volumes:
    - runner_cache:/data
  depends_on:
    - dind
  command: >-
    bash -ec '
    forgejo-runner create-runner-file --name runner --instance https://${DOMAIN} --secret ${RUNNER_SECRET};
    sed -i -e "s|\"labels\": null|\"labels\": [\"docker:docker://docker.io/node:22-bookworm\", \"ubuntu-latest:docker://ghcr.io/catthehacker/ubuntu:act-latest\"]|" .runner ;
    forgejo-runner generate-config > config.yml;
    sed -i -e "s|^  network: \"\"$|  network: host|" config.yml ;
    sed -i -e "s|^  envs:$$|  envs:\n    DOCKER_HOST: tcp://dind:2376\n    CONTAINER_HOST: tcp://dind:2376|" config.yml ;
    forgejo-runner --config config.yml daemon
    '

You don't actually need to do this since you could edit the two config files yourself and bind them to the container. This is just how you automatically generate those files... And it's dumb, but it works and it means you don't have to keep track of those files.

This one is probably just my infrastructure: https://lemmy.world/comment/16093731

If you do go for FA in Docker (or Podman) and need some help, just ask. I'll post more of my compose and explain my decisions.

[–] possiblylinux127@lemmy.zip 2 points 1 year ago (1 children)

My general understanding of all of this is that the Forgejo ecosystem is young and needs time to mature. I'll probably just stick with Woodpecker for now but thanks for the explanation.

[–] Clearwater@lemmy.world 1 points 1 year ago

I agree. Forgejo itself is stable and I love it. Gitea never gave me trouble and that carried over.

Actions is just a bit hard to setup, at least for me, when I tried. We'll get there one day. (I believe the big thing is really just documentation.)