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 1 week ago
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 1 week 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.