Actually implement the OT_PERMISSION_MAY_FULLSCRAPE mechanics and add a config file entry

1 files changed, 6 insertions, 1 deletions

diff --git a/opentracker.conf.sample b/opentracker.conf.sample
index 7b35369..ba8497f 100644
--- a/opentracker.conf.sample
+++ b/opentracker.conf.sample
@@ -119,7 +119,6 @@
 #
 # access.stats_path stats
 #
-# II
 #      If opentracker lives behind one or multiple reverse proxies,
 #      every http connection appears to come from these proxies. In order to
 #      take the X-Forwarded-For address instead, compile opentracker with the
@@ -128,6 +127,12 @@
 # access.proxy 10.0.1.23
 # access.proxy 192.0.0.0/8
 #
+#      Symmetrically, if you have restricted the access to fullscrapes with
+#      the WANT_RESTRICT_FULLSCRAPE compile option, this is how you bless ip
+#      addresses to fetch fullscrapes
+#
+# access.fullscrape 10.1.1.23
+#
 
 # III) Live sync uses udp multicast packets to keep a cluster of opentrackers
 #      synchronized. This option tells opentracker which port to listen for