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

Missing documentation on how to set connection_kwargs params. #330

Closed
slyapustin opened this issue Sep 28, 2022 · 4 comments
Closed

Missing documentation on how to set connection_kwargs params. #330

slyapustin opened this issue Sep 28, 2022 · 4 comments

Comments

@slyapustin
Copy link
Contributor

What is the right way to specify connection_kwargs?

Based on the changelog - it was implemented a while ago, but there are no examples on how to set that and no mentions in the docs.

I'm happy to submit PR, but I can't figure out how to set them on my own 🤔

1.3.0 (2017-04-07)

  • Change the format of connection arguments to be a single dict called
    connection_kwargs rather than individual options, as they change by
    connection type. You will need to change your settings if you have any of
    socket_connect_timeout, socket_timeout, socket_keepalive or
    socket_keepalive_options set to move them into a connection_kwargs dict.
@carltongibson
Copy link
Member

connection_kwargs will just be passed to the underlying library no?

@slyapustin
Copy link
Contributor Author

@carltongibson How it should look in the CHANNEL_LAYERS configuration?

CHANNEL_LAYERS = {
    "default": {
        "BACKEND": "channels_redis.core.RedisChannelLayer",
        # how to pass `socket_connect_timeout`, `socket_timeout` and etc?
    }
}

@slyapustin
Copy link
Contributor Author

This might be relevant to #331

@carltongibson
Copy link
Member

This should be resolved by #370.

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

No branches or pull requests

2 participants