-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document current restriction of single worker #125
Labels
documentation
Improvements or additions to documentation
Comments
I guess in the meantime we should configure 1 worker in the image: Line 19 in 5c93944
|
Also pretty easy to allow a |
easybe
added a commit
that referenced
this issue
Sep 12, 2024
We currently do not fully support multiple workers. For more info, see: #125 This configuration can be overridden by setting the `GUNICORN_CMD_ARGS` environment variable.
easybe
added a commit
that referenced
this issue
Sep 12, 2024
We currently do not fully support multiple workers. For more info, see: #125 This configuration can be overridden by setting the `GUNICORN_CMD_ARGS` environment variable.
easybe
added a commit
to husqvarnagroup/goosebit
that referenced
this issue
Sep 12, 2024
We currently do not fully support multiple workers. For more info, see: UpstreamDataInc#125 This configuration can be overridden by setting the `GUNICORN_CMD_ARGS` environment variable.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the in-memory cache gooseBit should not be deployed with multiple workers currently.
This limitation should be documented until it is addressed (if required).
The text was updated successfully, but these errors were encountered: