Configuring Soketi Docker Container

[soketi]

Configuring Soketi Docker Container

[rennokki]

Hi @Purtl, let's break it down.

Starting with 0.13 or so, pws got rebranded to soketi. I think you're still using the old version (which was kept for reverse compatibility issues like this one 😁). So I'm going to refer to the last version of soketi to answer your questions.

PUSHER_APP_KEY (this one I tried to set for the container, but nothing happened)
PUSHER_APP_SECRET
PUSHER_APP_ID
PUSHER_HOST
PUSHER_PORT

I do indeed believe that the configuration can be hard to find. I will be working on this to make the configuration easier. What you want to configure is the array driver. In Docker, you can run the app by giving environment variables values:

docker run -p 6001:6001 -e DEFAULT_APP_ID=some-id -e DEFAULT_APP_KEY=some-key -e DEFALT_APP_SECRET=some-secret quay.io/soketi/soketi:0.17-16-alpine

PUSHER_AUTH_ONLY (I completely made this one up for enforcing the Auth connections behavior mentioned earlier)
PUSHER_AUTH_TIMEOUT (for the auth connections timeout)
PUSHER_PING_PONG_TIMEOUT (the ping pong timeout)

These ones are not configurable and I don't think they will be configurable in the future. We stick to the Pusher protocol and the authentication is always on, the timeout for authentication is undefined and the Ping-Pong timeout is set to the protocol definition (120 seconds).

PUSHER_SCHEMA

This is defined on whether you configure it with SSL or not. In your SDK/client configuration, you might want to enable it in production and eventually use non-SSL in development.

[Purtl]

Hi!
Sorry for the long response time. I got everything to work! Thank you so much!