|Name : builds.sr.ht
|Version : 0.36.4
||Vendor : obs://build_opensuse_org/home:jfita
|Release : lp150.3.1
||Date : 2019-01-26 10:31:50
|Group : Productivity/Networking/Web/Servers
||Source RPM : builds.sr.ht-0.36.4-lp150.3.1.src.rpm
|Size : 0.76 MB
|Packager : (none)
|Summary : Build service for sr.ht
|Description : |
The master server is a standard sr.ht web service and can be installed as such.
However, it is important that you configure two Redis servers - one that the
runners should have access to, and one that they should not. Insert connection
details for the former into build.sr.ht\'s configuration file under the redis
key. Each build runner will also need a local redis instance running. In an
insecure deployment (all services on the same server) you can get away with a
single Redis instance.
We suggest using an SSH tunnel to share the slave Redis instance between job
runners and the master server, but you can use any method you prefer. If you
use an SSH tunnel, you will likely want to use a reverse tunnel initiated from
the master server, so the slaves are unable to SSH into the master server.
RPM found in directory: /mirror/ftp5.gwdg.de/pub/opensuse/repositories/home:/jfita:/sr.ht/openSUSE_Leap_15.0/noarch