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.

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

Expose progress ("interior parcel" count) to Celery #9

Open
mojodna opened this issue Jun 9, 2015 · 2 comments
Open

Expose progress ("interior parcel" count) to Celery #9

mojodna opened this issue Jun 9, 2015 · 2 comments
Assignees

Comments

@mojodna
Copy link

mojodna commented Jun 9, 2015

...ultimately exposing it to the web interface.

@joehand
Copy link
Member

joehand commented Jun 11, 2015

For those who are familiar with Celery, is a custom state the best way to update progress (as in the example in that section)?

@mojodna
Copy link
Author

mojodna commented Jun 11, 2015

Possibly? Depends how the front-end intends to consume progress. It might make more sense to persist progress in the Django models and update it either with direct db calls (which might be manageable by watching the custom state) or via an API call.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants