Skip to content
This repository has been archived by the owner on Jan 29, 2025. It is now read-only.

RFC: Support Redis celery broker #213

Closed
wants to merge 1 commit into from

Conversation

zachmullen
Copy link
Contributor

@zachmullen zachmullen commented Oct 10, 2024

As written, the change here in the _HerokuMixin is backwards incompatible and will break any installations using CloudAMQP rather than the Redis addon. If we wanted a backward compatible version of this, we'd need fallback logic (likely in a @property) to check for either environment variable (with some order of precedence we could decide on).

For local development, no code changes are needed in this library to support using redis as the broker.

Note also that this PR doesn't go as far as to enable a celery results backend. If we switch to Redis, it's officially more suitable as a result backend than AMQP, but that's a more controversial change than I want for the scope of this RFC.

"""

# Assume AMQP.
CELERY_BROKER_URL = values.Value("amqp://localhost:5672/")
CELERY_BROKER_URL = values.Value("redis://localhost:6379/0")
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resonant dev environments always set this value, so the default isn't really important.

@brianhelba
Copy link
Contributor

All these changes have been moved here: kitware-resonant/cookiecutter-resonant#213

@brianhelba brianhelba closed this Jan 29, 2025
@brianhelba brianhelba deleted the redis-celery-broker-support branch January 29, 2025 17:41
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants