SparkleShare
SparkleShare copied to clipboard
Move notification service to a cloud provider
The previous notification service worked well for a good time but started to get unstable. Maintaining the server and client code, as well as the sysadmin work is a hassle. The current plan is to use a cloud provider for this functionality. The service will be anonymous and will not do any data collection. Suggestions welcome!
Just a note that on the current master (as of today - 01/21/18) the tcp listener service is still working fine in our environment. Tested by simply reverting the one patch.
Good to hear. :)
Since a few weeks I am getting:
11:09:29 | Listener | Trying to reconnect to tcp://notifications.sparkleshare.org:443/ 11:09:29 | Listener | Disconnected from tcp://notifications.sparkleshare.org:443/: Connection refused
Is there eventually an alternative service?
@gerhard-tinned any idea? ^
Thanks @gerhard-tinned, service is back again:
09:25:06 | ListenerTcp | Pinging tcp://notifications.sparkleshare.org:443/ 09:25:06 | ListenerTcp | Received pong from tcp://notifications.sparkleshare.org:443/
@hbons thanks for your great software.