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
Staring channels servers independently could help to prevent a crash in in all servers. Also could help to host a channel server in a host and the launcher, signing and entrance in another host.
The text was updated successfully, but these errors were encountered:
You mean hosting some servers in different machines (like launcher server in one, sign server in another and so on)?
If you mean this then it could be possible but it would require some kind of server getting data asynchronously from more than 1 server at a time
I have considered modifying channelserver to use a port range (54001-54999) and if a port fails, it'll try to spin up the server on the next port. The only issue I forsee with this is users having to use port triggering instead of only mapping 8 or so channelserver ports. This would also simplify the config by having the port field be an override and blank by default. If there's any interest in applying it this way, I will implement it.
Also, as suggested in OP, the individual servers can be commented out to not be booted. This is actually not uncommon as it lets servers be able to run a single entranceserver that points to a separate instance that only runs channelservers in order to run client testing more efficiently or run different database instances/channelserver code.
Staring channels servers independently could help to prevent a crash in in all servers. Also could help to host a channel server in a host and the launcher, signing and entrance in another host.
The text was updated successfully, but these errors were encountered: