Closed xezon closed 7 months ago
sorry for the late reply, the preferred way to run the project locally is using yarn dev
which I'd expect to work fine even on Windows.
When it comes to the browser HTTPS errors when ENABLE_LOCAL_HTTPS
is set to true, this flag shouldn't really be used in production mode, only in development and then a self-signed HTTPS certificate is used. The browsers may still "complain" that the certificate is invalid, but they should allow you through by clicking "proceed anyway" or a similar button that would be visible on the error page
For the best windows development experience I'd recommend using WSL https://ubuntu.com/desktop/wsl which should remove any environment-specific incompatibilities this project has, given it is being developed and hosted on UNIX environments
Using
Windows 10 yarn v1.22.19 node-v18.12.0-x64
I searched for NODE_ENV error title:
https://stackoverflow.com/questions/11928013/node-env-is-not-recognized-as-an-internal-or-external-command-operable-comman
I added & symbol to package.json as per stackoverflow comments:
It then builds and starts like so:
Opening https://localhost:3000/ in Firefox reports:
Opening https://localhost:3000/ in Chrome reports:
Perhaps you can make it possible to build on Windows right out of the box.
And for the SSL error, unclear to me how to open http page. Browsers do not allow this. They want to open https page, perhaps because adalite still poses as a https page when it should not?
Attempting to launch with ADALITE_ENABLE_HTTPS=true will fail.