I have a project on Forgejo and I’ve needed to set up a runner for compilation but I’ve been very confused so far on how everything works.
All I’ve been able to do is make a runner and connect it to my Forgejo instance, but I didn’t really know what to do from there.
Where are you located? If in the UK, BargainHardware has pretty good deals when they get a bunch of the same HDD model in stock.
I was having a lot of trouble keeping port forwarding stable before this change with protonvpn too. Probably the best change I’ve seen with gluetun so far!
Yes, if a port is set in the port forwarding section for the qbittorrent preferences in the webui (once one is set it stays until changed), the green globe means it’s working.
To enable port forwarding with gluetun see the port forwarding section in the gluetun wiki on their github page. It’s pretty clear what you need to do there.
For port forwarding with qbit, gluetun’s v3.40.0 release introduced an environment variable that allows the running of a script whenever the VPN changes port (see PR https://github.com/qdm12/gluetun/pull/2399). If you take a look at the PR some people shared commands to put under the env variable VPN_PORT_FORWARDING_UP_COMMAND.
So all you need to do is put that new environment variable in the environment section, take one of the example commands that uses the qbitorrent API to change the port when needed, and it should be all.
To test if port forwarding works qbittorrent will display a little green planet in the bottom bar, and if port forwarding is not working, a fire (to say it’s firewalled).
How exactly does stuff get broken? Never rly had a problem bumping up the version in docker. The only issue has been the playstore version taking longer to push updates sometimes for the mobile apps.