As an administrator I'd like to deploy radiator-cms in a subfolder

[monkeydom]

In a deployment scenario where we want to run everything on one domain, we'd like to run the cms e.g. at https://radiator.mydomain.com/manage/

Nuxt generally supports that and adding something along the lines of

  // potentially run in a subfolder (e.g. /manage/ in the default radiator installation)
  router: {
    base: process.env.NUXT_ROOT || '/'
  },

to the nuxt config gets us mainly there. However, some links still lead to / so inner app link generation needs to use this information everywhere instead of just doing hrefs with '/something/'

nuxt router docs

So the idea would be to then serve the cms using an nginx proxy conf like this:

# Proxy requests to "cms" port 3000
location /manage {
	proxy_set_header X-Real-IP $remote_addr;
	proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
	proxy_buffering off;
	proxy_set_header Host $http_host;
	proxy_request_buffering off; # Disable any internal buffering
	proxy_pass http://cms:3000;
	proxy_set_header Upgrade $http_upgrade;
	proxy_set_header Connection "upgrade";
}