title: What should letsencrypt certbot-auto's "webroot-path" be for a non-PHP / non-static-files website?
body: <p>In the case you have a website using Apache only (maybe with PHP) that is in:</p>
  
  <pre><code>/home/www/mywebsite/
  /home/www/mywebsite/index.php
  /home/www/mywebsite/style.css
  </code></pre>
  
  <p>then, it's easy to set <code>certbot</code>'s <code>--webroot-path</code>:</p>
  
  <pre><code>./certbot-auto certonly --webroot --webroot-path /home/www/mywebsite/
                          --domain example.com --domain www.example.com --email a@example.com
  </code></pre>
  
  <hr>
  
  <p><strong>Question</strong>: when using a website run by NodeJS
   or Python Flask or Bottle, linked to Apache either with WSGI (mod_wsgi) or simple proxying (I know the latter is not recommended in the case Python)</p>
  
  <pre><code>RewriteEngine On
  RewriteRule /(.*)           http://localhost:5000/$1 [P,L]
  </code></pre>
  
  <p><strong>what should <code>--webroot-path</code> be?</strong></p>
  
  <p>More specifically, if we have:</p>
  
  <pre><code>/home/www/mywebsite/       (Pyton example)
  /home/www/mywebsite/myapp.py
  /home/www/mywebsite/myapp.sqlite
  /home/www/mywebsite/static/style.css
  ...
  </code></pre>
  
  <p>or</p>
  
  <pre><code>/home/www/mywebsite/        (NodeJS example)
  /home/www/mywebsite/myapp.js
  /home/www/mywebsite/myapp.sqlite
  /home/www/mywebsite/static/style.css
  ...
  </code></pre>
  
  <p>then it doesn't make sense to choose <code>--webroot-path</code> as <code>/home/www/mywebsite/</code>, right?</p>
  
  <p>Indeed, I don't want any other program/script like letsencrypt certbot to fiddle with my .py files.</p>
  
  <p>Anyway, what does <code>--webroot-path</code> in <code>certbot</code> do? Will files there be analyzed, parsed?</p>