For RHMAP 3/4, the Studio was originally part of a single jar/war (millicore). It did have a jsp for delivering the index.html (which wrote a bunch of inline javascript) The studio was then decoupled from the war file as a separate war (fh-studio). However, it still had an index.jsp, but called back to the 'core' to get some of the info needed for that. This was eventually refactored into a node.js express app (fh-ngui) and deployed completely separately. It still made calls back to the core to get some config/user info. The main benefit I found was the UI could be progressed at a faster pace as the local development tooling could be tailored better. (just run the UI server & hook up to an existing core somewhere) However, it introduced overhead with the addition of a new deployable component.

This was all in a pre-containers world, but it was migrated to a container world (on openshift). We never went as far as nginx serving static content, but I could see that as a logical progression. It would probably mean a smaller footprint overall.

On 30 January 2018 at 19:40, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > Hi, > > right now, we have the static resources of the admin ui build to a JAR file > and a "node tgz". Currently, in the community, we use the bundled JAR and > deployed to the UPS WAR file. So far, so good > > For our modularization I was thinking at different options: > > * WildFly Swarm w/ just static (WAR) resources > * Node.js/Express app > * Ngnix container, just serviing the content > > I've tested 1) I was wondering if we might - for some better resource > utilization might just go w/ Ngnix, and deploy the static resources of the > admin UI to there? > > How do other think about breaking the UPS down to different technologies and > aspects? > > -Matthias > > [1] https://github.com/aerogear/unifiedpush-admin-ui > > -- > Matthias Wessendorf > > github: https://github.com/matzew > twitter: http://twitter.com/mwessendorf > > -- > You received this message because you are subscribed to the Google Groups > "Aerogear" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to aerogear+unsubscribe(a)googlegroups.com. > To post to this group, send email to aerogear(a)googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/aerogear/CAAg5f2Qi6Fwj5FPq-VdBEw3Ro_ pq4FwqJpPiyGbmj0cEJrfv7Q%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- David Martin Red Hat Mobile Twitter: @irldavem IRC: @irldavem (#aerogear) -- You received this message because you are subscribed to the Google Groups "Aerogear" group. To unsubscribe from this group and stop receiving emails from it, send an email to aerogear+unsubscribe(a)googlegroups.com. To post to this group, send email to aerogear(a)googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/ msgid/aerogear/CADvBQ45yhH_-%2BZ2gKsU-agjv2ucngsgUgo66- dQ7MdyoMuDinw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.