[Git][qa/jenkins.debian.net][master] i386.reproduce.debian.net: run on a public port to allow external workers

[Holger Levsen (@holger)]

Holger Levsen pushed to branch master at Debian QA / jenkins.debian.net


Commits:
44c310c4 by Holger Levsen at 2024-12-29T17:38:22+01:00
i386.reproduce.debian.net: run on a public port to allow external workers

Signed-off-by: Holger Levsen <holger at layer-acht.org>

- - - - -


2 changed files:

- hosts/infom07-i386/opt/etc/rebuilderd-worker.conf
- + hosts/infom07-i386/opt/etc/rebuilderd.conf


Changes:

=====================================
hosts/infom07-i386/opt/etc/rebuilderd-worker.conf
=====================================
@@ -1,5 +1,5 @@
 ## The rebuilderd to connect to
-endpoint = "http://127.0.0.1:8484"
+endpoint = "http://i386.reproduce.debian.net:8484"
 ## The server would either allowlist our key or require a signup secret
 #signup_secret = "your_signup_key"
 


=====================================
hosts/infom07-i386/opt/etc/rebuilderd.conf
=====================================
@@ -0,0 +1,40 @@
+## Configuration for http daemon
+#[http]
+## The address to bind to. This is 127.0.0.1:8484 by default.
+bind_addr = "i386.reproduce.debian.net:8484"
+## If you use a reverse proxy, use this header instead of the actual connecting ip.
+## Make sure the reverse proxy has filters in place to prevent spoofing issues.
+#real_ip_header = "X-Real-IP"
+## Set a default endpoint for rebuildctl. This is especially useful for the sync timer.
+#endpoint = "http://127.0.0.1:8484"
+
+## A random cookie for administration is generated at startup and written to /var/lib/rebuilderd/auth-cookie
+## You can set this to a fixed value here. Use `pwgen -1s 32` to generate one.
+## rebuildctl is searching for this cookie in ~/.config/rebuilderd.conf, /etc/rebuilderd.conf and
+## /var/lib/rebuilderd/auth-cookie in that order.
+#[auth]
+#cookie = "INSECURE"
+
+## The auth cookie above is only used for the default endpoint.
+## You can use different endpoints with `rebuildctl -H https://rebuilder.example.com status`,
+## In that case you need to configure a section below if you want to attach a cookie.
+#[endpoints."https://rebuilder.example.com"]
+#cookie = "INSECURE"
+
+## IMPORTANT: in production, make sure either `authorized_workers` or `signup_secret` is configured.
+#[worker]
+## If we have a fixed set of workers we can allow-list the keys here.
+#authorized_workers = ["key1", "key2"]
+## If we want to spawn new workers dynamically we can configure a sign up secret below.
+## Use `pwgen -1s 32` to generate one.
+#signup_secret = "INSECURE"
+
+#[schedule]
+## Configure the delay to automatically retry failed rebuilds in hours. The
+## default is 24h, this base is multiplied with the number of rebuilds, so the
+## first retry would happen after 24h, the second retry would happen 48h after the
+## first retry and the third retry would happen 72h after the second retry. There
+## is no upper limit of retries, if you can't afford frequent retries it's
+## recommended to set this to a high value like 168 (1 week) or higher.
+## Successful rebuilds are not retried.
+#retry_delay_base = 24



View it on GitLab: https://salsa.debian.org/qa/jenkins.debian.net/-/commit/44c310c485466ce2736330d7137ae24981c3dd8b

-- 
View it on GitLab: https://salsa.debian.org/qa/jenkins.debian.net/-/commit/44c310c485466ce2736330d7137ae24981c3dd8b
You're receiving this email because of your account on salsa.debian.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/qa-jenkins-scm/attachments/20241229/3b770195/attachment-0001.htm>