Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Enable sqlalchemy as celery result backend if no result backend is set up #17881

Closed
mvdbeek opened this issue Apr 2, 2024 · 1 comment · Fixed by #17949
Closed

Enable sqlalchemy as celery result backend if no result backend is set up #17881

mvdbeek opened this issue Apr 2, 2024 · 1 comment · Fixed by #17949
Assignees
@davelopez
Labels
area/backend area/database Galaxy's database or data access layer

Comments

@mvdbeek
Copy link
Member

mvdbeek commented Apr 2, 2024

Might be a little tricky since that logic would probably need to live in gravity ?
@mvdbeek mvdbeek added area/database Galaxy's database or data access layer area/backend labels Apr 2, 2024
@mvdbeek mvdbeek changed the title Enable postgres as celery result backend if no result backend is set up Enable sqlalchemy as celery result backend if no result backend is set up Apr 2, 2024
@bernt-matthias
Copy link
Contributor

Why not just hardcode it in the config + docs for production? Analogous to what we do with the galaxy database, which defaults to sqlite of I remember correctly.

@davelopez davelopez mentioned this issue Apr 9, 2024
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@davelopez davelopez

Labels
area/backend area/database Galaxy's database or data access layer
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Replace sample Celery result_backend in config davelopez/galaxy
3 participants
@mvdbeek @bernt-matthias @davelopez