Minimize configuration changes required to run dev server inside a container

[koyadume]

Clear and concise description of the problem

At this moment it requires to adjust a number of configuration parameters in order to run dev server inside a container vs running it directly on your local setup. I believe many of these adjustments can be eliminated by following few things -

base

• If I am specifying a value for this config parameter, it means my dev server will be running behind a proxy because that is the only scenario where I need to use a non default value for this config. In such scenarios we can set the value of server.host property to 0.0.0.0 so that one need not to specify this explicitly.
• (Optional) server.port can be set to 80 so that one need NOT to adjust this while running application in development vs production modes inside a k8s cluster.
• Dev server should always serve index.html file at / instead of value of base config parameter. This will eliminate need of defining different url rewrite rules while running an application in development vs production modes inside a k8s cluster.

hmr - Use location.port on the browser side for hmr.clientPort which will set it to correct value no matter dev server is running behind a proxy or not. This will eliminate the need of specifying hmr.clientPort when dev server is running behind a proxy.

The whole idea is that developers should focus on writing the code instead of figuring out appropriate values for different configurations parameters to run an application across different types of setups (local development, remote development (on a k8s cluster), production etc).

Suggested solution

Mentioned in the problem description

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[sapphi-red]

related: #4116

[bluwy]

• If I am specifying a value for this config parameter, it means my dev server will be running behind a proxy because that is the only scenario where I need to use a non default value for this config. In such scenarios we can set the value of server.host property to 0.0.0.0 so that one need not to specify this explicitly.

Not sure if this best as as base can now be set as ./ to generate relative paths in builds (embedded deployments).

• Dev server should always serve index.html file at / instead of value of base config parameter. This will eliminate need of defining different url rewrite rules while running an application in development vs production modes inside a k8s cluster.

This could be confusing for non-proxy setups though.

hmr - Use location.port on the browser side for hmr.clientPort which will set it to correct value no matter dev server is running behind a proxy or not. This will eliminate the need of specifying hmr.clientPort when dev server is running behind a proxy.

I believe #8650 resolved this.

Perhaps better documentation is needed as and if we plan so we should follow #4116

[koyadume]

Not sure if this best as as base can now be set as ./ to generate relative paths in builds (embedded deployments).

I believe purpose of the base property to set the value of html <base> tag or achieving equivalent effect. This tag comes into picture only when html is downloaded and so I am of the opinion that index.html should not be served on any uri other than root (/) uri.

This could be confusing for non-proxy setups though.

Can you explain how this could be confusing non-proxy setup?

[bluwy]

I mean for usual Vite usage (ootb from the template), if someone sets base I think it's fair that the expect index.html to be served from /base/index.html instead from the root. Hence it would be confusing if not. At least it would break a lot of current setups which can be avoided.