Hosting Perlite for "mydomain.com/perlite/..." or "mydomain.com/perlite/lang/..."

[dumbc0re]

Hello. Need help. I have two machines, one with YunoHost with NGINX and one for Perlite. I need requests from my domain to go to several different copies of Perlite with different languages for example:
https://domain.com/en/perlite/...
https://domain.com/de/perlite/...
Instead of:
https://de.domain.com/
https://en.domain.com/
To avoid making separate subdomains for each. How do I configure Perlite and nginx for this task? Thanks in advance.

[secure-77]

Hi,
please take a look at this wiki entry

[dumbc0re]

Hi, please take a look at this wiki entry

Hmm. Strange, I changed the parameters, the custom port 8811 address works, but /perlite gives a 404 error. (Im used Docker version)

[dumbc0re]

Hi, please take a look at this wiki entry

Hmm. Strange, I changed the parameters, the custom port 8811 address works, but /perlite gives a 404 error.

After changing the settings, refreshing the page also results in a 404 error.

VID_20250829_165053_494.mp4

[dewillepl]

you need to edit your perlite.conf and add separate location blocks for each language path (e.g. /en/perlite/, /de/perlite/)
something like this

location /en/perlite/ {
    root /var/www/perlite-en;
    index index.php index.html;
    try_files $uri $uri/ /index.php;
}

[dumbc0re]

location /en/perlite/ {
    root /var/www/perlite-en;
    index index.php index.html;
    try_files $uri $uri/ /index.php;
}

I tried it, but the situation remains the same. When I went to the path /en/perlite, it showed a page with the Perlite interface, but completely blank, and it disappeared after going to any other page like "MyIP:Port/Documents..."

[secure-77]

Hi, please take a look at this wiki entry

Hmm. Strange, I changed the parameters, the custom port 8811 address works, but /perlite gives a 404 error. (Im used Docker version)

First of all you need to have one perlite instance running for each vault / language.

If you are using Docker in the backend you need to have two perlite docker containers running (one for every language) and an enxtra nginx as reverse proxy.. The (reverse proxy) nginx will handle the URL requests and pass them to the right docker container. In the docker containers you can use the default nginx config, but probably each container need to expose a different port to your host.

You can have a look at something like this: https://diptochakrabarty.medium.com/nginx-reverse-proxy-using-docker-8c3d0f00b27b
(instead of using nginx as a loadbalancer you just need to setup it as described above with different location directives)

[dumbc0re]

If you are using Docker in the backend you need to have two perlite docker containers running (one for every language) and an enxtra nginx as reverse proxy.. The (reverse proxy) nginx will handle the URL requests and pass them to the right docker container. In the docker containers you can use the default nginx config, but probably each container need to expose a different port to your host.
You can have a look at something like this: https://diptochakrabarty.medium.com/nginx-reverse-proxy-using-docker-8c3d0f00b27b (instead of using nginx as a loadbalancer you just need to setup it as described above with different location directives)

Okay, I created two separate containers on one PC with default settings. I have another device running YunoHost, which runs Nginx with an HTTPS connection. Below are screenshots of the Nginx configurations and their results. The problem is most likely with my configuration on the YunoHost side, but I don't know how to fix it.

[secure-77]

ok, this looks already good, now you only need two more settings in the perlite container.

in the docker-compose.yml set the URI variable

  - URI_PATH=/de/

then stop and start the containers again, so the new compose file get loaded

docker compose down
docker compose up -d

the second setting (unfortunate) you need to adjust in the container itself. I will check if I can improve this in the next version but for now you can use the following command to set the variable uriPath to /de/ in the perlite.js

docker exec perlite sed -i "s|var uriPath = '/'|var uriPath = '/de/'|g" /var/www/perlite/.js/perlite.js

you can check if its correct with the following

docker exec perlite head -15 /var/www/perlite/.js/perlite.js

one more thing what I recognized, you need to adjust your reverse proxy setting to the following (take note of the trailing slash after the port)

location /de/ {
            proxy_pass http://localhost:8280/;
        }

[dumbc0re]

ok, this looks already good, now you only need two more settings in the perlite container.

I decided to delete two containers and create a new one based on perlite:build. HTTP requests without /de/ work fine. However, when using a domain or subdomain, the display break, as in the previous screenshot. The new configurations are below.

[secure-77]

Not sure what exactly is the problem but some things are not working as intended. Maybe its something related to your include conf./yunohost_panel.conf.inc or another proxy setting. But also http://localhost:8280/de/ should not work any more if everything is correct configured (it should show the white page without any styles)

For troubleshooting try to:

1. lunch only one perlite and perlite_web container with the uriPath settings (/de/)
2. put something else for the default route (/), like the default nginx html page
3. only set the really necessary settings in the reverse proxy
4. check the network tab in the browser debug console to see how the path for the css and js files look like

Here are my settings, which are working fine:

Reverse Proxy Config

/etc/nginx/sites-available/default

server {
        listen 80 default_server;
        listen [::]:80 default_server;

        root /var/www/html;

        index index.html index.htm index.nginx-debian.html;

        server_name _;

        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                try_files $uri $uri/ =404;
        }

        location /de/ {
                proxy_pass http://localhost:8280/;
        }

}

perlite_web config

Perlite/web/config/perlite.conf

default, no changes

perlite compose config

services:
  perlite:
    image: sec77/perlite:latest
    container_name: perlite
    restart: unless-stopped
    environment:
      - NOTES_PATH=Demo
      - HIDE_FOLDERS=docs,private,trash
      - HIDDEN_FILE_ACCESS=false
      - LINE_BREAKS=true
      - URI_PATH=/de/
      - ABSOLUTE_PATHS=false
      - ALLOWED_FILE_LINK_TYPES=pdf,mp4
      - DISABLE_POP_HOVER=false
      - SHOW_TOC=true
      - SHOW_LOCAL_GRAPH=true
      - HOME_FILE=README
      - FONT_SIZE=15
      - HTML_SAFE_MODE=true
      - TEMP_PATH=/tmp
      - SITE_TITLE=Demo
      - SITE_TYPE=article
      - SITE_URL=
      - SITE_IMAGE=
      - SITE_DESC=
      - SITE_NAME=Perlite
      - SITE_TWITTER=https://x.com/
      - SITE_LOGO=perlite.svg
      - SITE_HOMEPAGE=https://perlite.secure77.de/
      - SITE_GITHUB=https://github.com/
    volumes:
      - ./perlite/Demo:/var/www/perlite/Demo:ro

  web:
    image: nginx:stable
    container_name: perlite_web
    restart: unless-stopped
    ports:
      - 8280:80
    volumes:
      - ./web/config/perlite.conf:/etc/nginx/conf.d/default.conf:ro
    volumes_from:
      - perlite
    depends_on:
      - perlite

setting uriPath

This you need to execute every time after the perlite container has started
docker exec perlite sed -i "s|var uriPath = '/'|var uriPath = '/de/'|g" /var/www/perlite/.js/perlite.js

this is how it should look like

also try to refresh the browser with cleaned cache (open developer console, switch to the network tab and click, disable cache)

[dumbc0re]

Got it, thanks for the help. Unfortunately, I was unable to configure a proxy on YunoHost so that it could work as a layer. Sorry for wasting your time.