1. Mailing Lists
  2. Contributors
  3. Re: Docker :: Distributed Deployment Wheelhouse

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Docker :: Distributed Deployment Wheelhouse

Re: Docker :: Distributed Deployment Wheelhouse

Avatar

Re: Docker :: Distributed Deployment Wheelhouse

by
dar@devco.co
- 11/11/2015 04:11:35
sorry, I missed those two beforehand:     
libsasl2-dev \
    libssl-dev \

El mar., 10 nov. 2015 a las 18:41, David Arnold (<dar@devco.co>) escribió:
It's not nice to share headache without remedy, so on ubunty:trusty, those where the deps to build all current standard pip requirements.txt of the offical odoor repo properly:

# Additional dependencies for wheelfactory (placed here for caching reasons)
RUN apt-get update && apt-get install -y 
python-pip \
libldap2-dev \
libxml2-dev \
libxslt-dev \
    libpq-dev \
    libjpeg-dev \
    python-renderpm

The last one I'm not 100% sure. Just put it there, as it doesn't really matter and sounds so similar to a pip req.

Best

El mar., 10 nov. 2015 a las 16:28, David Arnold (<dar@devco.co>) escribió:
Hi

I wanted to share with you a pattern for rather easily achieving a distributed deployment wheelhouse on your distributed CI runners on your docker infrastructure with the purpose of saving bandwidth and pushing speed.

Step 1: Make a pre-build Dockerfile which prepares wheels and other stuff such as odoo.zips and webserver binaries.

Step 2: on docker run copy those to a bindmounted shared volume

Step 3: run a uhttp (ej. fnichol/uhttpd) with volumes_from

Step 4: access your ephemeral, but cached (by docker build stack), webserver from your other dockers via the host gateway and the exposed port [ej. $(ip route get 8.8.8.8 | grep -Eo 'via \S+' | awk '{print $2}')]

Enjoy the speed up, even more so on slow network connection (or just save on your bandwith)

Best David

Reference