Hello. We have django app for which we have "django envs" which can be though of as Rails envs. This allows us to run the app locally against various databases (among other things). We would like to run dramatiq on at least two of these (local) envs, using a local redis instance as both broker and backend. We would like to avoid having these two envs colliding. One idea that came to mind was to do something like:
(we have a separate setting config file for each env, essentially mimicking what happens in Rails.)
and using a different redis db for each env, but we are using the various dbs for other apps (typically sidekiq) and this seems like a suboptimal solution.
Is there a natural (or at least recommended) way to isolate the jobs coming from separate envs (and maybe results as well) ?
Hello. We have django app for which we have "django envs" which can be though of as Rails envs. This allows us to run the app locally against various databases (among other things). We would like to run dramatiq on at least two of these (local) envs, using a local redis instance as both broker and backend. We would like to avoid having these two envs colliding. One idea that came to mind was to do something like:
(we have a separate setting config file for each env, essentially mimicking what happens in Rails.)
and using a different redis db for each env, but we are using the various dbs for other apps (typically sidekiq) and this seems like a suboptimal solution.
Is there a natural (or at least recommended) way to isolate the jobs coming from separate envs (and maybe results as well) ?
Thanks for reading