this post was submitted on 18 Apr 2025
61 points (96.9% liked)

Selfhosted

46168 readers
477 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 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
[–] DasFaultier@sh.itjust.works 28 points 4 days ago (2 children)

The Forgejo guys have built this themselves, so I'm aiming to use that (I don't just yet, because I can't find the time).

[–] danb@feddit.uk 6 points 4 days ago

Just to contrast with some of the other comments regarding this, i've have a pretty good experience with this. Was fairly simple to setup up some docker-based runnings following their admin guidance. Have set up a couple (One for Codeberg, one for my own Forgejo instance) each via a seperate LXC container on my home lab. Has been relatively simple to administer so far.

The actions format may take some getting used to if not familiar with GitHub's own actions CI, which if closely emulates, but most of my projects were coming from GitHub anyway.

[–] whereisk@lemmy.world 7 points 4 days ago (1 children)

I’ve tried it with forgejo, the recommended implementation involves spinning a temporary vm to run the integration and deployment processes, quite resource heavy and slow comparatively to the vm I have that’s running forgejo.

I think there’s an option to have the forgejo server itself run the commands without spinning up vms, but it’s not recommended due to security considerations as they’re running with the same privileges as the server - not a concern if you are the only developer connecting to a private instance of forgejo but something to keep in mind.

[–] BrightCandle@lemmy.world 3 points 4 days ago

Its quite complicated to setup as well, just went through the instructions and its a long way from just add to docker and run unfortunately. Would be nice to be able to just get a runner in the same or different docker and it just works easily without a lot of manual setup in Linux of directories and users and pipes etc.