Ok, maybe i’m just assuming Wappler is setting the config.
When I output $_ENV in my development environment I get the following by default:
1. DEBUG: "server-connect:*"
2. HOME: "/root"
3. HOSTNAME: "..."
4. NODE_ENV: "development"
5. NODE_VERSION: "16.20.0"
6. PATH: "/opt/node_app/node...l"
7. PORT: "3000"
8. PUPPETEER_EXECUTABLE_PATH: "/usr/bin/google-chrome"
9. PUPPETEER_SKIP_CHROMIUM_DOWNLOAD: "true"
10. PWD: "/opt/node_app"
11. REDIS_HOST: "redis"
12. TERM: "xterm"
13. YARN_VERSION: "1.22.19"
So you can see here the NODE_ENV is outputting automatically as ‘development’. Is it fair to assume that when a target is set to staging, or production that Wappler should also automatically handle this by replacing development with the usage setting from the Project Settings?