Disable Heroku workers, since they can't actually run tasks #263
Conversation
Deploying geoinsight with
|
| Latest commit: |
edaafbe
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b6e78e6b.geoinsight.pages.dev |
| Branch Preview URL: | https://heroku-worker.geoinsight.pages.dev |
annehaley
left a comment
annehaley
left a comment
There was a problem hiding this comment.
If we don't use workers, where will tasks be run? They need to run in an environment where the tasks extras are available.
|
@annehaley I'm happy to discuss this. However, the Heroku slug size has a hard limit of 500MB, so we can't install the extra dependencies there. I think this is generally an unfortunate result of the mismatch between the research community (which doesn't care about packaging or optimizing code redistribution size) and the web engineering community (which needs to care about maintaining sane package sizes, to support more advanced deployment automation). |
annehaley
left a comment
annehaley
left a comment
There was a problem hiding this comment.
After a dicsussion with @brianhelba, we have decided to move our asynchronous tasks to an EC2 worker instead of a Heroku worker.
No description provided.