10-04-2013, 07:33 AM
(This post was last modified: 10-04-2013, 07:34 AM by rsjtdrjgfuzkfg.)
We have to release a new release until January 14th, 2014, or we will lose the opportunity to update existing Nightingale installations. Google code stops the download feature at that day; and thus we will not be able to push new update xmls.
Starting the discussion here, where shall we host our update xmls now? We need a place where everyone involved in the update is able to post xml files to and that supports HTTPS for download. Self-signed certificates are sufficient if we bundle the certificate into NG (not sure how that works, but it should work).
If we do not publish a update with new update urls, all users will be stuck at the current release.
For the technical part, I created issue 218.
Starting the discussion here, where shall we host our update xmls now? We need a place where everyone involved in the update is able to post xml files to and that supports HTTPS for download. Self-signed certificates are sufficient if we bundle the certificate into NG (not sure how that works, but it should work).
If we do not publish a update with new update urls, all users will be stuck at the current release.
For the technical part, I created issue 218.
Songbird/Nightingale Community Developer and German Translator