Multiple nextJs apps on same TLD - change _next path

[felixhagspiel]

Hello,

I have 2 nextjs websites running on the same domain.

1. Webapp runs on mydomain.com/app, proxied by nginx
2. Website runs on mydomain.com and handles all requests that do not match /app

I have added an assetPrefix and a proxy to handle static assets for both pages, which works.

Unfortunately both apps try to access the mydomain.com/_next - path for things like data, for example mydomain.com/_next/data/7_29Y8lYPZHCAfRAnVhSH/... and I am of course unable to to proxy it to the correct app. I know about basePath, but when I use it, it prepends the locales, so the path for my app would look like mydomain.com/app/en instead of mydomain.com/en/app.

Is there any workaround for this?

I have read this #5602 but it has been closed without a solution for my case.

[felixhagspiel]

I think I just solved it. This article pointed me to the right direction: https://arihantverma.com/posts/2021/07/18/workaround-nextjs-data-urls-same-domain-multiple-apps/

So what I am doing now is using custom build IDs and prefixing them with dashboard- and website-. Then I proxy all requests via nginx to the related apps:

       location ~ ^/(_next/data/dashboard-) {
        proxy_pass http://localhost:3000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
        }

       location ~ ^/(_next/data/website-) {
        proxy_pass http://localhost:3100;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
        }