added how to update your lantern automatically

opsec/darknetlantern/index.html

@@ -616,6 +616,43 @@ server {
 
 </pre></code>
 <img src="17.png" class="imgRz">
+<p>Since v1.0.1, you can now automate the updating of your lantern instance despite the www/participants folder changing (thanks to the changes made to .gitignore):</p>
+<pre><code class="nim">
+[ Datura ] [ /dev/pts/28 ] [~]
+→ /usr/bin/torsocks /usr/bin/git -C /srv/darknet-lantern/ pull
+
+warning: redirecting to http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/darknet-lantern/
+remote: Enumerating objects: 24, done.
+remote: Counting objects: 100% (24/24), done.
+remote: Compressing objects: 100% (19/19), done.
+remote: Total 19 (delta 14), reused 0 (delta 0), pack-reused 0 (from 0)
+Unpacking objects: 100% (19/19), 2.06 KiB | 421.00 KiB/s, done.
+From http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/darknet-onion-webring
+   5928fd3..dc0c2ef  main       -> origin/main
+Updating 5928fd3..dc0c2ef
+Fast-forward
+ README.md                                                                                          |  37 ++++++++++++++++++++++++++++++++-----
+ scripts/lantern.py                                                                                 |   6 ++++--
+ www/participants/lantern.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/banner.png | Bin 14119 -> 0 bytes
+ www/participants/lantern.nowhevi57f4lxxd6db43miewcsgtovakbh6v5f52ci7csc2yjzy5rnid.onion/banner.png | Bin 8952 -> 0 bytes
+ www/participants/zhd7yf675dav6njgc7yjwke2u5cq7d5qim2s7xwa2ukxfzubrguqmzyd.onion/banner.png         | Bin 20935 -> 0 bytes
+ 5 files changed, 36 insertions(+), 7 deletions(-)
+ delete mode 100644 www/participants/lantern.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/banner.png
+ delete mode 100644 www/participants/lantern.nowhevi57f4lxxd6db43miewcsgtovakbh6v5f52ci7csc2yjzy5rnid.onion/banner.png
+ delete mode 100644 www/participants/zhd7yf675dav6njgc7yjwke2u5cq7d5qim2s7xwa2ukxfzubrguqmzyd.onion/banner.png
+
+</pre></code>
+<p>You can automatically perform that git pull using cronjobs like so:</p>
+<pre><code class="nim">
+[ Datura ] [ /dev/pts/28 ] [~]
+→ crontab -e
+
+#lantern
+*/3 0 * * * python3 /srv/darknet-lantern/scripts/uptimechecker.py
+0 0 * * * /usr/bin/torsocks /usr/bin/git -C /srv/darknet-lantern/ pull
+
+</pre></code>
+<p>That way it'll update your lantern software once a day, at midnight.</p>
 
 
 				</div>
@@ -627,7 +664,7 @@ server {
 	    <div class="container">
 			<div class="row">
 				<div class="col-lg-8 col-lg-offset-2">
-          <h2><b> How to participate in the webring ? (WIP)</b></h2> </br> </br>
+          <h2><b> How to participate in the webring ?</b></h2> </br> </br>
 <p>In order to participate in the webring that i am running, the only requirements i have is that your webring instance should have the core functionnalities (you list links you didn't verify yet, you also list the ones you verified, and you list the other webring participants), you should bring some new onion links i don't already have, and you shouldn't list porn links.</p>
 <p><u>Sidenote:</u> you are free to fork the project, and change how the front-end looks to customize it, <b>but the CSV format (especially the columns order and their titles, and the values format) and the paths</b>(ex: http://URL.onion/participants/URL.onion/verified.csv) <b>those NEED to remain the same to be able to remain compatible with the other lantern instances.</b> </p>