Hi Vivek, thanks for your feedback - glad the UPS continues to work great
for your team :-)
As stated in [1], it's "only" against different MySQL/MariaDB flavors,
using EAP (not WildFly)
Thanks again for helping us testing our release.
-Matthias
[1]
On Tue, Mar 17, 2015 at 10:30 AM, Vivek Pandey <vivek.pandey(a)pinelabs.com>
wrote:
I was able to migrate my test setup to 1.0.3 successfully, running
UPS
1.0.2 on wildfly 8.1 and Postgres 9.3.
Thanks
*From:* aerogear-dev-bounces(a)lists.jboss.org [mailto:
aerogear-dev-bounces(a)lists.jboss.org] *On Behalf Of *Matthias Wessendorf
*Sent:* Tuesday, March 17, 2015 1:50 PM
*To:* AeroGear Developer Mailing List
*Subject:* Re: [aerogear-dev] [Vote] UPS 1.0.3 release
Hi Vivek,
that's right, here are the steps you need to run:
https://github.com/aerogear/aerogear-unifiedpush-server/tree/1.0.3/migrator
feel free to test that on your test/dev environment. For any heads-up of
successful migration, or errors, we are more than thankful!
Cheers,
Matthias
On Tue, Mar 17, 2015 at 7:52 AM, Sébastien Blanc <scm.blanc(a)gmail.com>
wrote:
Hi Vivek,
Yes the migrator also works for 1.0.2 => 1.0.3 (without any data loss)
Sebi
Envoyé de mon iPhone
Le 17 mars 2015 à 07:37, Vivek Pandey <vivek.pandey(a)pinelabs.com> a
écrit :
Hi Guys,
Thanks for the 1.0.3 release.
I am wondering if we can use the migrator to migrate 1.0.2 database schema
without any data loss ?
Vivek
*From:* aerogear-dev-bounces(a)lists.jboss.org [
mailto:aerogear-dev-bounces@lists.jboss.org
<aerogear-dev-bounces(a)lists.jboss.org>] *On Behalf Of *Jay Balunas
*Sent:* Friday, March 13, 2015 11:11 PM
*To:* AeroGear Developer Mailing List
*Subject:* Re: [aerogear-dev] [Vote] UPS 1.0.3 release
Great job everyone! Lets get this release out the door!
On Mar 13, 2015, at 11:00 AM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
@docs: updates are now live:
https://staging.aerogear.org/docs/unifiedpush/ups_userguide/index/#schema
also, here is the promised staging repo:
https://repository.jboss.org/nexus/content/repositories/jboss_releases_st...
happy testing
On Fri, Mar 13, 2015 at 10:56 AM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
Hi,
we tagged for UPS 1.0.3, and I did upload the JAR files to NEXUS, but I am
not yet able to create a staging repo for that (I notified our ops team).
However, for testing the server, all we really need are the WAR files. I
have uploaded the distribution files to GH, as a pre-release:
https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.0.3
NOTES
1. We no longer support H2 database. You need MySQL/Postgres for tests.
2. The JPA provider no longer creates the DB schema for you
If you don't have MySQL installed, it's trivial to use it via Docker:
docker run --name unifiedpushDB -p 3306:3306 -e MYSQL_USER=unifiedpush -e
MYSQL_PASSWORD=unifiedpush -e MYSQL_DATABASE=unifiedpush -e
MYSQL_ROOT_PASSWORD=supersecret -d mysql
Now, once the DB is up, you need to run the migrator against the empty
database to create the schema. The migrator is included in the dist file,
and instructions are here
<
https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.0.x/migrat...
DB setup for EAP/WildFly works as usual, see
https://aerogear.org/docs/unifiedpush/ups_userguide/index/#gendbds
Once that is all done, install the WARs to your application container:
https://aerogear.org/docs/unifiedpush/ups_userguide/index/#deploy
Let me know about this release, and if there are no complains by
Wednesday, I will push the bits to maven central and mark the pre-release
as a real release
Oh, this is most-likely the last release of the 1.0.x series
-Matthias
PS: I am now updating the docs, to reflect the changes and new requirements
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
------------------------------
This message may contain privileged and confidential information and is
solely for the use of intended recipient. The views expressed in this email
are those of the sender and not of Pine Labs. The recipient should check
this email and attachments for the presence of viruses / malwares etc. Pine
Labs accepts no liability for any damage caused by any virus transmitted by
this email. Pine Labs may monitor and record all emails.
------------------------------
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf
------------------------------
This message may contain privileged and confidential information and is
solely for the use of intended recipient. The views expressed in this email
are those of the sender and not of Pine Labs. The recipient should check
this email and attachments for the presence of viruses / malwares etc. Pine
Labs accepts no liability for any damage caused by any virus transmitted by
this email. Pine Labs may monitor and record all emails.
------------------------------
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev