Add custom idleTimeout env variable

[HijenHEK]

Custom idleTimeout env variable

Current state

timeout is hardcoded in the server and the handler to 120 according to the ws protocol

Why this is important

A Custom idleTimeout is necessary specially in testing environment , some use cases are :

• app still in development
• testing ws with postman
• internal or local production env

Changes :

• added the SOKETI_IDLE_TIMEOUT env variable in cli.ts
• added the idleTimeout as a number in options.ts
• settled the variable as the option indicates with a default of 120, server.ts & ws-handler.ts

Result

SOKETI_IDLE_TIMEOUT=180 node bin/server.js start

[codeautopilot]

PR summary

The Pull Request introduces a new environment variable SOKETI_IDLE_TIMEOUT to customize the idle timeout for WebSocket connections in the soketi server. Previously, the timeout was hardcoded to 120 seconds. This change allows for greater flexibility, especially in testing environments or during development. The default value remains 120 seconds if the environment variable is not set.

Suggestion

Ensure that the documentation is updated to reflect the addition of the new environment variable and provide guidance on how to use it effectively. Additionally, consider adding validation to ensure that the provided SOKETI_IDLE_TIMEOUT value is a positive integer and within a reasonable range to prevent misconfiguration.

Disclaimer: This comment was entirely generated using AI. Be aware that the information provided may be incorrect.

Current plan usage: 35.39%

Have feedback or need help?
Discord
Documentation
[email protected]