I don’t know how Woodpecker works, but I have a lot of experience with Gitlab runners. You can startup a runner locally, as it doesn’t need to be publicly accessible from the internet. Only the Gitlab instance needs to be accessible for the runner, as the runner actively fetches new jobs from there and pushes the results again.
If Woodpecker works similarly, you could just deploy the runner locally while you’re actively developing and your computer is running anyway, if you don’t want to pay for a VPS.
I don’t know how Woodpecker works, but I have a lot of experience with Gitlab runners. You can startup a runner locally, as it doesn’t need to be publicly accessible from the internet. Only the Gitlab instance needs to be accessible for the runner, as the runner actively fetches new jobs from there and pushes the results again.
If Woodpecker works similarly, you could just deploy the runner locally while you’re actively developing and your computer is running anyway, if you don’t want to pay for a VPS.
That’s how it works that I can see. I run it and woodpecker just waits for an event like a push or whatever to your repo and then it runs the jobs.
As someone who runs gitlab as well I much prefer woodpecker CI to github/forgejo actions. Personal preference entirely though.