I started working on the SkySpy Server-Service (that is a mouthful!) tonight.
The plan (although things may change):
1) The service runs in the background and does all the non-visual stuff that ssServer does now - GW comm, WU Update, Mini-web site, DB update.
2) A Small app will configure the service/show the latest sensor readings in real-time if you leave it running on your desktop. This is optional - except for initial setup. Might be good to let you know if your sensors are working OK and if communications are happening in a timely manner.
3) The database will work in one of two modes:
3a) The service will be able to use stand-alone database tables (no MySQL database install required). This mode does not allow external programs to read the database tables: Data is for the exclusive use of the service.
3b) The service will be able to use a local or remote MySQL database engine (but not mine). Login credentials will be stored in the registry. You can do what you like with the data in the tables.
4) All configuration information will be stored in the registry. Update it with the small setup app.
5) Absolutely No Promises, but I am looking at a Cumulus interface. If it turns out to be a pain, this will be the first thing to get tossed overboard.
Wow! Very
Not a request for enhancements, just a question relating to potential SkySpy Server-Service configuration(s)...
If you have more than one LCX station/gateways (1 remote - 1 local)...
would it be possible to create/run separate instances of the SSS-S, on the same physical server - each SSS-S instance
having a unique (configurable) service name and associated registry configuration entry?
e.g.
LCX1 Gateway at remote location.
LCX2 Gateway at local location.
Physical Server (running two SkySpy Server-Service instances to handle two LCX Gateways):
SSS-S instance 1 (for LCX1):
registry config = Service name: "
SkySpyServer1", SSS-S listening IP: "192.168.2.100:6005", output to mySQL DB on IP: "192.168.2.100:3306", DB username: "
SSSS_user1", pw="xxxxxx" Database Name: "
LCX1_SkySpyServer1")
SSS-S instance 2 (for LCX2):
registry config = Service name: "
SkySpyServer2", SSS-S listening IP: "192.168.2.100:5080", output to mySQL DB on IP: "192.168.2.100:3306", DB username: "
SSSS_user2", pw="xxxxxx", Database Name: "
LCX2_SkySpyServer2")
If unique service names & configs are a problem, we could always run two servers, (maybe 1 physical, 1 VM) each with their own SSS-S installations.