<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 23, 2014 at 1:51 PM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Wed, Oct 22, 2014 at 6:13 PM, Karel Piwko <span dir="ltr"><<a href="mailto:kpiwko@redhat.com" target="_blank">kpiwko@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi All,<br>
<br>
I'd like to know your opinion on following changes to UnifiedPush<br>
Server. They are both focused on improving customization process for the<br>
cartridge.<br>
<br>
Just in short, current update process now:<br>
1/ Clone official git repository of cartridge<br>
2/ Extract wars and do the modifications or build ones<br>
3/ Package wars<br>
4/ Push cartridge to your own repository<br>
5/ Create cartridge from your own repository<br>
<br>
Whereas, I'm proposing:<br>
1/ Create cartridge from official repository<br>
2/ Clone git repository for gear created by Openshift (by default if rhc<br>
is used)<br>
3/ Modify some files there we expose for user modification<br>
4/ Push back to make changes live<br>
<br>
What particular configuration elements I'm interested to have<br>
externalized?<br>
<br>
1/ Ability to load keycloak.json from external location<br>
<br>
=> This allows user to create cartridge and modify it prior the first<br>
access. This allows users to configure it to be consumable by other<br>
services automatically, e.g. they can add developer users, roles, etc.<br></blockquote><div><br></div></span><div>hrm, in theory, yeah, that could be possible. Perhaps Stian or abstractj have an idea here</div></div></div></div></blockquote><div><br></div><div>we could have our real in a JSON file, so that it is easy/easier to import it into an existing KC server, to run UPS against that</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
2/ Externalize GCM/APNs locations<br>
<br>
=> Now, URLs are hardcoded in GCM/APNs JARs. </blockquote><div><br></div></span><div>yes, they are considered stable APIs :) </div><div><br></div><div>We are not going to 'externalize' these URLs </div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If they would be loaded<br>
from external location (defaults can still be hardcoded), this allows<br>
user to easily check business logic that queries data in UPS and not<br>
sending any messages. Also allows to put proxy in between UPS and<br>
APNs/GCMs.<br>
<br>
Both these will significantly reduce QE overhead. However, I believe<br>
they are valuable for other as well.<br>
<br>
Feedback and tomatoes (I prefer plum ones) are welcomed.<br>
<br>
Thanks,<br>
<br>
Karel<br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</blockquote></span></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</font></span></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>