-
Notifications
You must be signed in to change notification settings - Fork 2
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
Configure Sidekiq->SSL->Redis #107
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, thanks so much!
@xuanxu That didn't fix it, unfortunately. It still errors, but now somewhat more specifically. The service errors when starting up because of this: |
@mpadge that's weird, are you sure the last commit was deployed? |
That looks like a previous deployment from when I merged main into ropensci, last commit should be |
Aha. @maelle and I couldn't figure out yesterday how to trigger a deployment from the web interface. Any tips there? |
In the "Deploy" tab should be a section for "Manual deploys" at the bottom of the page. Just enter the name of the branch (in this case 'ropensci') and click the "Deploy branch" button. |
Yeah, that's what we tried, but just get "Item could not be created: Unauthorized". I think "ropensci" is just the name of the GitHub branch, but it's something else on Heroku? |
No, there is nothing else, the name of the GitHub branch is enough. I have deployed that way sometimes without problems. I guess you don't have permissions to deploy. The owner have to add you as collaborator. You can see who the owner is in the "Access" tab. |
I found out why - the app was connected to GitHub via @maelle's GitHub login, so only she can deploy. Seems there's no way to allow multiple people to deploy that way. And that means we'll have to just wait until auto-deploy tomorrow. If you hear nothing further from me here, it means that everything is working again. Thanks for your help! |
ropensci branch deployed! 🚀 |
And it works again! Thanks! and ping @maelle with the good news |
This PR should fix the error caused by the update of the Heroku SSL certificate.
https://devcenter.heroku.com/articles/connecting-heroku-redis#connecting-from-sidekiq