2 ms·
I wrote a similar article a few weeks ago (http://syskall.com/dont-run-node-dot-js-as-root/ http://syskall.com/dont-run-node-dot-js-as-root/) but have since the
by olalonde 14y ago
I wrote a similar article a few weeks ago (http://syskall.com/dont-run-node-dot-js-as-root/ http://syskall.com/dont-run-node-dot-js-as-root/) but have since then realized that changing the process' UID brings a lot of unexpected problems and a much simpler solution is to use a higher port and proxy via nginx. For example, if you initialize a logger before starting your HTTP server and changing the process UID, you will might create root owned files and eventually run into permission conflicts.