You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Without binding to a specific IP, there's no way to take advantage of TUN/TAP virtual devices for encrypted networking (or preventing external access).
The text was updated successfully, but these errors were encountered:
@jamiesonbeckerSCC_INSTANCE_IP is not the IP address on which the scc-broker server binds itself; it's the IP address which the scc-broker uses to advertise itself to the cluster; so other instances will use this IP address when they want to connect to the scc-broker; it's mostly used when running the instance inside a container to allow it to be referenced by others using a single consistent public IP.
This feature is not currently exposed by any component of SCC (you could do it on scc-broker using SOCKETCLUSTER_OPTIONS env variable but it's tricky because it needs to be a JSON object).
PRs to expose this feature directly with a single env var would be welcome but it should be done consistently across both scc-state and scc-broker - Following naming conventions for env vars for different instance types.
Is it possible to specify an IP as an env var, a passed argument to
node server
, etc to bind to for scc-state, scc-broker, etc?I think this is what I'm looking for in scc-broker, but it doesn't seem to have a parallel in scc-state:
https://github.com/SocketCluster/scc-broker/blob/master/server.js#L9
Without binding to a specific IP, there's no way to take advantage of TUN/TAP virtual devices for encrypted networking (or preventing external access).
The text was updated successfully, but these errors were encountered: