Contributors mailing list archives
Re: Docker for OCA/OCBby
We would gladly share and maintain our recipe with / in OCA.
We would even be willing to migrate to an oca account on dockerhub...
I propose we give our recipe and make it use ocb instead of vanilla (one line change), "cleaned-up" & "optimized", if you want to gain space in your image you could remove py3o.template from the base images :)
Yes that is true and we have pending adding the credit of xcgd (we are still with a lot of WIP here).
We split because originally in China we could make xcgd work properly as is due to the fact that pip install was timing out. Now we do not have the issue anymore because we build in hub.docker.com and mirror to China.
Nevertheless the main reason to fork was XCGD bin and Odoo are stored in their servers whereas in our case, we use official pip + OCB github code. Size matters as well: we have optimized the size at a little bit less than a Gb when AFAIR their docker is almost 2 Gb. This is important to us where bandwidth is a huge constraint
Last but not least we will push soon a powerful mechanism based on oca_dependencies.txt file that will all to pull directly dependencies from github.
So yes we started our work based on XCGD (sorry again for the missing credits) but diverged in the approach, objectives and used sources.
Anyway, my original mail was actually to leverage an effort from the community and having XCGD on board would be helpful even if options taken might be discussed altogether for the particular case of OCA.
My original objective was to build a simple and easy to use docker file for quick and up-to-date deployment for OCB but with XCGD's team, it might become even easier.