summaryrefslogtreecommitdiff
path: root/examples
diff options
context:
space:
mode:
Diffstat (limited to 'examples')
-rw-r--r--examples/travelynx.conf21
1 files changed, 19 insertions, 2 deletions
diff --git a/examples/travelynx.conf b/examples/travelynx.conf
index c7c4f89..fdcd03e 100644
--- a/examples/travelynx.conf
+++ b/examples/travelynx.conf
@@ -35,14 +35,31 @@
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
+ # geoip_ok => 1, # <- either this
+ # proxy => 'socks://...', # <- or this
},
},