gunrunner20
gunrunner20
I can just say I second this feature request, but additionally it would help me a lot if also universal folder paths could be excluded, like "*/archive". Currently just specific...
Same here on Win10. (Had another error with just "NODE_ENV=..." already, and installed cross-env to solve this) ``` > npm run build > [email protected] build > cross-env NODE_ENV=production && run-s...
> > Same issue, any fix for this? > > For me the issue went away after I rebooted my nginx proxy container. Same here. I added another sub domain...