[aerogear-dev] Push Server Admin UI packaging

[Kris Borchers]

I would say a separate repo makes sense here because of the separate build process. The only way I would want them combined, and maybe we do this later, is if the server build could trigger the client's grunt build. I'm pretty sure we could figure this out but probably not worth the time to dig into right now.

On Jun 27, 2013, at 7:35 AM, Lucas Holmquist <lholmqui at redhat.com> wrote:

> Currently i've started to develop the push server admin ui in a repo here:https://github.com/lholmquist/aerogear-unified-push-server-admin-ui  ( be sure to look at the ember repo ;) )
> 
> my question is how should we package it with the push server.  Should we keep developing the UI in a separate branch and then update the servers "web" directory with the "dist" directory( currently i'm using grunt to copy the non dist directory to the web directory of the server during development ) when we do a "release" of the admin UI,
> 
> or do we want to include all the unminified stuff in the "web" directory of the server.
> -- There are 2 options here:
> ---- just develop in the push server repo
> ---- develop in a separate repo and then copy unminified stuff over
> 
> 
> I kind of like the develop in a separate repo and copy over the dist directory for "releases"  but in a read me or something,  tell the developer how to modify  the console if the want to
> 
> 
> 
> thoughts?
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130627/4f8b26a2/attachment.html