Explaination of nginx (proxy) templates

Post Reply
dpeca
Site Admin
Posts: 163
Joined: Fri Jun 19, 2020 9:59 am
Explaination of nginx (proxy) templates

Post by dpeca »

  • caching template - will cache html output to server disk, i'm not sure how and when purge is done
  • default template - the same as hosting template, exists only for compatibility purposes
  • force-https template - the same as hosting template, but it will always redirect visitors from http to https
  • force-https-legacy template - the same as force-https template, but will pass requests for not-existent static files to Apache - see why
  • force-https-public template - the same as force-https template, but docroot will be public_html/public/ instead of public_html/ (mostly used in Laravel projects)
  • force-https-webmail-phpmyadmin template - the same as force-https template, but will allow static files for /webmail/ and /phpmyadmin/
  • hosting template - default template, it will not pass requests for not-existent static files to Apache - see why
  • hosting-legacy template - the same as hosting template, but it will pass requests for not-existent static files to Apache - see why
  • hosting-public template - the same as hosting template, but docroot will be public_html/public/ instead of public_html/ (mostly used in Laravel projects)
  • hosting-webmail-phpmyadmin template - the same as hosting template, but will allow static files for /webmail/ and /phpmyadmin/
  • private-hosting template - will put http-auth on domain, but you must first execute in SSH: htpasswd -c /etc/nginx/.htpasswd YourDesiredUsername
  • private-force-https template - the same as private-hosting template, but it will redirect visitors from http to https

Tags:


Post Reply