The AeroGear UnifiedPush Server is a server that allows sending push notifications to different (mobile) platforms and has support for:
Project Info | |
---|---|
License: | Apache License, Version 2.0 |
Build: | Maven |
Documentation: | https://aerogear.org/push/ |
Issue tracker: | https://issues.jboss.org/browse/AGPUSH |
Mailing lists: | aerogear-users (subscribe) |
aerogear-dev (subscribe) |
The easiest way to get started is running our plain
Linux container:
mvn clean install -DskipTests && docker run -p 18081:8080 -it aerogear/ups:plain
then go to http://localhost:18081/
to use the UPS.
For our on-premise version, and more infos on database setup, please consult our user guide!
For your convenience, we do have an easy way of launch different configurations of the UPS, using our Docker compose files
For more details about the current release, please consult our documentation.
We have a list of users in our wiki. If you are using the UnifiedPush Server, please add yourself to the list!
Build the project:
mvn clean install
and start the latest build, locally, like docker run -p 18081:8080 -it aerogear/ups:plain
The Unified Push Server can be configured with either System Properties (passed to the Java commandline) or Environment Variables. The two options have different formats and the following list describes them using System Property Name
/Env Var Name
: Purpose
.
- custom.aerogear.apns.push.host/CUSTOM_AEROGEAR_APNS_PUSH_HOST: Custom host for sending Apple push notifications. Can be used for testing
- custom.aerogear.apns.push.port/CUSTOM_AEROGEAR_APNS_PUSH_PORT: Custom port for the Apple Push Network host
- custom.aerogear.fcm.push.host/CUSTOM_AEROGEAR_FCM_PUSH_HOST: Custom host for sending Google Firebase push notifications. Can be used for testing
- ups.realm.name/UPS_REALM_NAME: Override Keycloak Realm
- ups.auth.server.url/UPS_AUTH_SERVER_URL: Override Keycloak authentication redirect
- aerogear.metrics.storage.days/AEROGEAR_METRICS_STORAGE_DAYS: Override the number of days the metrics are stored (default is 30 days)
The content of the Release Process is valid for this project as well. However, to build the full distribution
bundle, you need to fire off the release like:
## prepare the release and define the TAG and adjust the versions:
mvn release:prepare -Dtag=x.y.z.Final -Darguments=-Dgpg.passphrase=$MY_SECRET_PASS_PHRASE -Pdist,test
## run the actual release process and load the artifacts to JBoss Nexus
mvn release:perform -DperformRelease=true -Darguments=-Dgpg.passphrase=$MY_SECRET_PASS_PHRASE -Dgpg.useagent=true -Pdist,test
If you would like to help develop AeroGear you can join our developer's mailing list, join #aerogear on Freenode, or shout at us on Twitter @aerogears.
Also takes some time and skim the contributor guide
We are available on Sonarcloud.io if you want to help us reduce our technical debt or improve our test coverage check us out there. It's a great way to get involved with your first PR. Check out the excellent guide on running SonarQube locally for more information.
Join our user mailing list for any questions or help! We really hope you enjoy app development with AeroGear!
If you found a bug please create a ticket for us on Jira with some steps to reproduce it.