Biigle served on subdirectory of domain?

[cywhale]

I want to serve Biigle on subdirectory of domain, i.e. https://mydomain/biigle/, for example.
By using proxy_pass in NGINX or rewrite rules, such as

upstream biigle {
  server 127.0.0.1:8008;
}

location \biigle {
  rewrite ^/biigle(.*)$ /$1 break;
  proxy_pass https://biigle;
}

location ~ ^/(assets|vendor|storage|doc)($|/) {
    proxy_pass https://biigle;
}

I can get initial layouts. But if internally routes to login/logout/search ..., no surprise got 404.
Is there any other way can do this? Thanks.

[mzur]

I'm not an expert in NGINX as reverse proxy but shouldn't this be enough?

upstream biigle {
  server 127.0.0.1:8008;
}

location /biigle/ {
  proxy_pass https://biigle/;
}

You shouldn't need a rewrite or an extra location for assets|vendor|... as this is handled by the webserver of the BIIGLE Docker container.

You also need to configure the APP_URL to the correct URL (with subdirectory) but this does not affect regular links in the application.

[mzur]

My bad, the TrustProxies middleware is disabled by default. Try to add this to the dockerfile:

RUN sed -i 's/\/\/ \\Biigle/\\Biigle/' app/Http/Kernel.php

[cywhale]

Thanks. I can confirm that app/Http/Kernel.php and trustedproxy.php have been modified/added following your suggestions by checking these files in docker container. But the results remain the same: I can get only initial layout well, but when clicking other links, the window location push https://mydomain/(routing) and then get 404.

I copied a test.include into /etc/nginx/conf.d/ by add COPY in web.dockerfile to debug:

    add_header x-uri "$uri" always;
    add_header x-NGINX-request_uri $request_uri always;
    add_header x-host $host always;
    add_header http-host $http_host always;
    add_header X-Real-IP $remote_addr always;
    add_header X-Forwarded-For $proxy_add_x_forwarded_for always;

I get confused about different proxy_set_header configuration would get weird response header:

1. When set proxy_set_header Host $host; proxy_set_header X-Forwarded-Host $host;
   ==> http_host = x_host = mydomain, and x-uri is /index.php. The result is described as aboving (only initial is good):

2. When set proxy_set_header Host "mydomain/biigle"
   ==> http_host = "mydomain/biigle", but x-host becomes "example.com", x-uri becomes "/" (NOT /index.php).
   So this setting "mydomain/biigle" not work and got 400 error.

[mzur]

It turns out that running a Laravel application in a subfolder is quite hard. Laravel is not made for this. I created an experimental setup with a reverse proxy and a subfolder. It works somewhat (except the initial login redirect, and the logo and icon font which are loaded via CSS). New are the ASSET_URL and a forceRootUrl hack.

I suggest you use a subdomain instead of a subdirectory.

[cywhale]

Yeah, I'll try and at least I had a working Biigle setting on ' \ '. It use a subdomain, indeed, and for our limited IP/server resources, so that I consider move it to subdirectory by upstreaming. Anyway, you really give me a big hand, thanks a lot.

[mzur]

You're welcome. And last time I checked, NGINX could handle several domains (even with SSL) so you can use the same IP and server for multiple subdomains.