[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.

[GeekShadow]

hmm, we could make a self-signed certificate and integrate it into Nightingale right ?

[rsjtdrjgfuzkfg]

(10-04-2013, 08:11 AM)GeekShadow Wrote: hmm, we could make a self-signed certificate and integrate it into Nightingale right ?

Yes, but we need a host; ilikenwf's hosting we're on here restricts certificates to only those purchased by the same hosting company.