-
Notifications
You must be signed in to change notification settings - Fork 17
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
Move workers to que-go for Heroku #16
Comments
I would like to work on this. |
Go for it @aswinmprabhu : ) |
@alexdor are we constrained to use que-go? Actually there are many other good background job processing libraries. Is only que-go supported on heroku? |
I've only seen que-go to be recommended by Heroku https://devcenter.heroku.com/articles/que-go In theory it just need to run as a separate app (according to this https://devcenter.heroku.com/articles/background-jobs-queueing#process-model) so in theory we could just extract the worker to a separate go app and run that |
Okay, got it! |
@alexdor is there any particular IRC channel like gitter, slack or so, where i can discuss with you and other contributors? |
Hm, as far as I know there isn't one, maybe the slack that is listed on ossn (https://ossn.club/faq-page) but I wouldn't consider it an official channel. Maybe @bacharakis has created one that I don't know You can always reach out to me on the email that is listed on my gh profile |
The workers should be moved to que-go so we could deploy the app in Heroku and leverage the workers there. There are some instructions here https://devcenter.heroku.com/articles/que-go
The text was updated successfully, but these errors were encountered: