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
{{ message }}
This repository has been archived by the owner on Jan 9, 2019. It is now read-only.
To make life easier for everyone when Port forwarding or having just the Server part 22007 (the websockets and the API) run on a single port and optionally have the Web Interface 22006. So the web interface would run on one machine as a single access point for control and all of the other machines have the APIs running for Access.
Also add the availability to add other machines to access from the single interface.
You define the Server IP, Server Com Port and Admin Login and it gets added to the Interface Group.
Oh, that's what I suggested (in #80) as well. I wish I had some time to try and implement some things myself, but I have a lot of things to work on at the moment...
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
To make life easier for everyone when Port forwarding or having just the Server part 22007 (the websockets and the API) run on a single port and optionally have the Web Interface 22006. So the web interface would run on one machine as a single access point for control and all of the other machines have the APIs running for Access.
Also add the availability to add other machines to access from the single interface.
ref: #51
The text was updated successfully, but these errors were encountered: