-
-
Notifications
You must be signed in to change notification settings - Fork 101
FAQs
Yes, there are different ways to do this. One way is to simply add the TLS settings in Nginx config of Perlite. If you use Docker, you can do this in the perlite.conf (make sure to rebuild the image after changing this file). You also need to adjust the Dockerfile to copy your certificates into your image. Another way is to setup a reverse proxy to handle the SSL offloading. Some resources:
Yes, but this need to be done by your webserver (nginx). for example you can use Basic Authentication or Mutal (Client Certificate) Authentication.
No, at the moment there is no file or folder specific protection implemented in Perlite.
Yes, If you want to use raw html you can set the following environment variable to false HTML_SAFE_MODE
Because perlite_web is just a default Nginx image that is created when you run docker-compose for the first time. The reason why this is not maintained on docker-hub: this way you can always use the latest official Nginx image without having to wait for a new Perlite image from my side.
You can use the following syntax to provide both, image alt text and size attributes for your embedded images. See Issue #92
Image with size and description
![[docs/Pasted image 202401101247081.png|Description of the image contents|100x100]]
will render as
<img class="images" width="100" height="100" alt="Description of the image content|" src="Demo/Demo Documents/docs/Pasted image 202401101247081.png">Image with description only
![[docs/Pasted image 202401101247081.png|Description of the image content]]
will render as
<img class="images" alt="Description of the image contents" src="Demo/Demo Documents/docs/Pasted image 202401101247081.png">Image with size only
![[docs/Pasted image 202401101247081.png|100x100]]
will render as
<img class="images" width="100" height="100" alt="image not found" src="Demo/Demo Documents/docs/Pasted image 202401101247081.png">