Default WEB_CONCURRENCY to N CPU cores in dev

I was noticing in development that the server was hanging and I'd often
receive gunicorn critical worker timeouts.

Author: nickjj

.env.example

@@ -60,10 +60,8 @@ export ALLOWED_HOSTS="*"
 #export PORT=8000
 
 # How many workers and threads should your app use? WEB_CONCURRENCY defaults
-# to the server's CPU count * 2. That is a good starting point. In development
-# it's a good idea to use 1 to avoid race conditions when debugging.
+# to the server's CPU count * 2. That is a good starting point.
 #export WEB_CONCURRENCY=
-export WEB_CONCURRENCY=1
 #export PYTHON_MAX_THREADS=1
 
 # Do you want code reloading to work with the gunicorn app server?

CHANGELOG.md

@@ -16,6 +16,7 @@ Changelog](https://keepachangelog.com/en/1.0.0/).
 
 - Convert `SECRET_KEY` into a required env var
 - Add `required: false` to `depends_on` in `docker-compose.yml` (requires Docker Compose v2.20.2+)
+- Adjust `WEB_CONCURRENCY` to default to N number of CPU cores instead of 1 in development
 - Rename `docker-compose.yml` to `compose.yaml` to stick to the official Docker Compose spec
 
 #### Languages and services