Upgrading from 1.5.2 > 2.x ?

[Steve Harman]

We'd like to update out 1.5.2 to 2.x   Is there an upgrade guide I could jump on please?

Basically I'd like to backup our existing install including Redis, install 2.x and test -but be able to roll-back to 1.5.2 and the previous database if things didn't work out.  ;-)

Many thanks,

Steve

[Tyson]

I think that the redis schema is compatible - 1.5.2 and 2.0.0 should store PSPs and DPs in the exact same way. 1.5.2 probably ignores hash keys it doesn't recognize. I'd recommend backing up a redis snapshot anyway, and making sure you could set up a new redis instance with that snapshot

In terms of schema changes, The new APIs just add a self-contained redis key for the list of service names from 2.0 onward, and nothing else. It doesn't affect 1.x

The most important change for 2.0 is the HTTP response output format change.

https://github.com/uniqush/uniqush-push/releases

• improvement Changed the response format of most APIs from logs to JSON. This allows clients to reliably parse results and errors from the API response. This will break clients that parse the old format

• improvement Add new APIs for listing the subscriptions of a subscriber and for listing the services exist. (Self contained, will require /rebuildpspset whenever you switch from 1.5.2 to 2.0.x, will be unaffected, use of this doesn't affect other APIs)
  

There's also a bug fix for APNS, which affects how apns payloads are rendered

• improvement Remove Go's default HTML escaping of JSON payloads, for APNS. The APNS servers now render payloads with characters such as '"' properly.