Separated worker tasks from app http work #12
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
+ npm run dev-start uses Procfile_dev
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey Hunter,
Last week, I'd threatened to update you on my efforts to break lib/app into separate http api (web) and worker pieces: and here is a naive attempt, though one that appears to deploy on heroku.
My purpose with this is to increase the chance you will provide informed guidance on how your demo app would best be expanded to suit the requirements of a horizontally spreading app with an arbitrary depth of async workers -- possibly with your own bare bones branch that I could work from. That's sort of what I was after with lib/worker, but I expect there would be some logical relating made between several worker processes and their task sets.