P7A-174: proxy node domain to Next.js

[pspanja]

• node.example.dev.php82.ez goes to Next.js (port 3000)
• example.dev.php82.ez goes to Ibexa

[amalija-ramljak]

I would prefer to keep the socket version of forwarding.

It enables having more than one project active at the same time on the local machine without having to also think about which pm2/nextjs process is up and has to be shut down. Instead, you'd just configure a free port for each project in its config once and use a make command inside the project to handle that pm2 process without having to check for other projects and shut another one down first. This is less of a hassle if you always use the dev watched build, so its at least open in your tab and you already know what to kill, but to me it would still make it a bit of a pain to switch projects - and this is just from the frontend dev's POV.

Another case for it is using the production build while testing someone's work or working on the backend or just in general needing the web while not working on the frontend assets - in the usual stack, you do a static dev build instead of watching the files, and you dont worry about running that command every time you have to work on the site without changes to the frontend assets. The assets are just there until you have to rebuild them, and no need to start any process every time just to open the web. From what I figured, that's not something we get with next's dev command?

[amalija-ramljak]

What exactly does this do?