-
Notifications
You must be signed in to change notification settings - Fork 1
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
Celery Progress Bar #41
Comments
This issue is stale since it has been open for 10 days without any activity. If the 'Stale Issue' label hasn't been removed or a comment made on the issue, it will be closed after 5 days of inactivity. |
The celery bar feature cannot be implemented just yet because it depends upon installing A PR has been submitted to initiate the process of updating the package. |
This issue can now be closed since an alternative caching solution was implemented. Refer to issue #60 |
3 environment variables will need to be added to the config vars in Heroku. CELERY_BROKER_URL
CELERY_RESULT_BACKEND
CELERY_BACKEND_URL |
Addresses the following: - Removal of redundant templates - Updates to development settings/config Linked Issue: #41
This issue is stale since it has been open for 10 days without any activity. If the 'Stale Issue' label hasn't been removed or a comment made on the issue, it will be closed after 5 days of inactivity. |
The results could be scraped more quickly using Python's
multiprocessing
module.The app is also a good candidate to implement a progress bar.
Tutorial / Package: Celery Progress Bar with Django
The text was updated successfully, but these errors were encountered: