Skip to content
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

Document Redis SSL configs #370

Merged

Conversation

bbrowning918
Copy link
Contributor

There is ongoing discussion and help in #235 and #330 (are there more?) about how to specify extra config for the connections to Redis, particularly SSL related.

The example provided is how we got Heroku to behave with it's self-signed certs on 4.1.0. Hopefully it will be helpful and answer a common question.

@bbrowning918
Copy link
Contributor Author

😞 oh

Copy link
Member

@carltongibson carltongibson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this @bbrowning918 👍

(I need to look at what happened to the CI...)

@justuswilhelm
Copy link

May I suggest that there could be a typo in the README as it is right now? (not mentioning the missing restructured text code block)

Right now it says something like the following, which is not a valid dict.

   "hosts":[
        "address": "rediss://user@host:port",  // "REDIS_TLS_URL"
        "ssl_cert_reqs": None
    ]

I reverted to using my own helper for now. It's too bad testing deployments on Heroku is so time consuming.

@bbrowning918
Copy link
Contributor Author

@justuswilhelm In hindsight I did not do a great job 'copy-pasting' our config from memory. Thank you for noticing that and the rst syntax mistake.

@carltongibson
Copy link
Member

I tweaked it, but happy to take any improvements.

@bbrowning918 bbrowning918 deleted the 235-ssl-and-connection-kwargs branch December 9, 2023 17:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants