Fix potential out of memory issue by setting max workers in backend c…

…ontainer

.env.example

@@ -19,6 +19,7 @@ [email protected]
 FIRST_SUPERUSER_PASSWORD=changethis
 USERS_OPEN_REGISTRATION=False
 MAX_UPLOAD_SIZE=50_000_000
+MAX_WORKERS=4
 
 # llm provider keys. Add only to models that you want to use
 OPENAI_API_KEY=

docker-compose.yml

@@ -66,6 +66,7 @@ services:
     env_file:
       - .env
     environment:
+      - MAX_WORKERS=${MAX_WORKERS}
       - DOMAIN=${DOMAIN}
       - ENVIRONMENT=${ENVIRONMENT}
       - BACKEND_CORS_ORIGINS=${BACKEND_CORS_ORIGINS}

local-deployment.md

@@ -83,5 +83,6 @@ Once the containers are running, you can access various services through the fol
 - **Adminer**: [http://adminer.localhost/](http://adminer.localhost/)
 
 ## Troubleshooting
+- **Out of Memory**: If you are getting the `Worker (pid:14) was sent SIGKILL! Perhaps out of memory?` error, this is due to the number of processes started for the backend container consuming more memory than what is available. You can fix this by decreasing `MAX_WORKERS` in your `.env` file.
 - **Unable to login to Traefik Dashboard**: Ensure that username and password is correct. If you are using zsh, `USERNAME` environment variable corresponds to the real user ID of the shell process, so you shold use your user ID as the username.
 - **Cannot login to Adminer**: Set 'System' to `PostgreSQL` and set the 'server' field should be `db`. The other fields should follow the values in your `.env` file.