Set a sensible default for MAX_PROC env var
didimitrie opened this issue · 1 comments
didimitrie commented
Step 0:
- I've read the contribution guidelines!
Expected Behaviour
How things should actually work!
You should not have a server eating up all your ram.
Actual Behaviour
What's actually going on!
Node spawns as many child processes as there are cores available, as the MAX_PROC env var is commented out by default.
Proposed Solution (if any)
Set MAX_PROC to 1 in .env-base, and uncomment the line.
didimitrie commented
fixed in #161