[openstack-dev] [horizon] packaging problem production build question

David Lyle dklyle0 at gmail.com
Thu Jan 8 22:11:24 UTC 2015

Bower is not for use in production environments. There will continue to be
two environment setup procedures, as there are today. For production,
deploy Horizon and its dependencies via system packages. For development
and testing leverage bower to pull the javascript resources, much as pip is
used today and continue to use pip for python dependencies.

For those running CI environments, remote access will likely be required
for bower to work. Although, it seems something like private-bower [1]
could be utilized to leverage a local mirror where access or network
performance are issues.


[1] https://www.npmjs.com/package/private-bower

On Thu, Jan 8, 2015 at 2:28 PM, Matthew Farina <matt at mattfarina.com> wrote:

> I've been going over the packaging problem in an effort to see how we can
> move to something better. Given the current proposal around bower I'm still
> left with a production deployment question.
> For a build environment sitting in isolation, unable to download from the
> Internet including Github, how would they be able to get all the bower
> controlled packages to create a system horizon package (e.g., rpm or deb)?
> These build environments currently use mirrors and controlled packages.
> For example, someone might have a pypi mirror with copies of the xstatic
> packages. This is tightly controlled. If bower is managing packages where,
> in theory, would it get them from for an environment like this?
> I may have missed something. If this has already been answered please
> excuse me and point me in the right direction.
> Thanks,
> Matt
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150108/e622c112/attachment.html>

More information about the OpenStack-dev mailing list