-
Notifications
You must be signed in to change notification settings - Fork 103
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
Use proper process manager for backend background services #98
Comments
We are considering Django Q2 to replace Redis RQ. With that, we would be able to use other backend DBs in different scenarios. |
That won't fix the issue. The problem isn't needing a separate Redis instance. The problem is running |
I see what you mean. Yea, switching the engine won't solve the issue you are describing. There are other "services" that are spawned within the container. |
Ah, I'd missed those - those should probably be moved to process manager. |
Running RQ as an unsupervised background process is dangerous, as there's nothing monitoring its availability.
Instead, it should either run as a separate container, or use a proper process manager like
s6
inside the container to watch both processes.The text was updated successfully, but these errors were encountered: