5c1e002233
* fix: use NODE_ENV when starting from docker image When starting from `pnpm run start`, NODE_ENV is fixed to production, causing problems like #186. So, I added `start_docker`, a process dedicated to docker, and started from it. The process is exactly the same as `start` except that NODE_ENV is not overwritten. * fix: align execution name with others * Change: command name to match review