This makes local development with Vite a little more flexible by providing a few new environment vars.
VITE_SERVER_HOST: This is the hostname used by the project. By default, this is just '0.0.0.0' as it was before.
VITE_SERVER_HMR_HOST: This is used if you want to point Vite's client to a different hostname. This is useful for containerized development, where the internal address might be 0.0.0.0 (allowing the local app to be visible outside the container) but the container has a different external address (hackgreenville.local or similar).
VITE_SERVER_POLLING: In this project, Vite's polling is true by default. You can disable it by setting this to false.
These 2 are for using HTTPS in local development. They should point to certificate and key files on your filesystem.
VITE_HTTPS_CERT
VITE_HTTPS_KEY
For this to work, both must be set and Vite must be able to read both files.
These vars have been added to .env.example as well, just commented out. Their defaults will take effect that way.
This makes local development with Vite a little more flexible by providing a few new environment vars.
VITE_SERVER_HOST: This is the hostname used by the project. By default, this is just'0.0.0.0'as it was before.VITE_SERVER_HMR_HOST: This is used if you want to point Vite's client to a different hostname. This is useful for containerized development, where the internal address might be0.0.0.0(allowing the local app to be visible outside the container) but the container has a different external address (hackgreenville.localor similar).VITE_SERVER_POLLING: In this project, Vite's polling istrueby default. You can disable it by setting this tofalse.These 2 are for using HTTPS in local development. They should point to certificate and key files on your filesystem.
For this to work, both must be set and Vite must be able to read both files.
These vars have been added to
.env.exampleas well, just commented out. Their defaults will take effect that way.Closes #234