Merge branch 'main' into efa-support

1 files changed, 28 insertions, 0 deletions

diff --git a/examples/travelynx.conf b/examples/travelynx.conf
index f8eaac0..fdcd03e 100644
--- a/examples/travelynx.conf
+++ b/examples/travelynx.conf
@@ -35,6 +35,34 @@
 		password => die("Changeme!"),
 	},
 
+	# Settings specific to the DBRIS bahn.de backend.
+	# Their journey endpoint (which is required for checkins) is behind an IP
+	# reputation filter, denying requests from most non-residential IP ranges.
+	# If needed, you can specify either a single SOCKS proxy or a set of
+	# SOCKS proxies here, and thus work around that limitation. If multiple
+	# proxies are specified, travelynx will choose a random one for each
+	# request. Note that DBRIS bahn.de requests to non-journey endpoints
+	# (such as the departure board) are always sent directly and not passed
+	# through the proxy / proxies specified here.
+	# "proxies" takes precedence over "proxy".
+	dbris => {
+		'bahn.de' => {
+			# proxy => 'socks://127.0.0.1:18080', # <- either this
+			# proxies => ['socks://127.0.0.1:18080', 'socks://127.0.0.1:18081'],
+		},
+	},
+
+	# Settings specific to HAFAS backends.
+	# For instance, the PKP backend is hidden behind a GeoIP filter, hence
+	# travelynx only supports it if travelynx.conf either indicates that it
+	# is reachable or specifies a proxy.
+	hafas => {
+		PKP => {
+			# geoip_ok => 1,          # <- either this
+			# proxy => 'socks://...', # <- or this
+		},
+	},
+
 	# These settings control the amount and (re)spawn behaviour of travelynx
 	# worker processes as well as IP, port, and PID file. They are suitable for
 	# up to a few dozen concurrent users. If your site has more traffic, you