Community mailing list archives
Re: Dockers for OCA/OCBby
David Arnold BA HSG / Analista
315 304 13 68/ email@example.com
devCO - empresa de consultoría de sistemas (en fundación)
This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. devCO is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.
To be noted that original objective for us was twofold- the use of OCB instead of standard odoo- Tweak the code to replace blocked website in chinaWe will have a look at proposed alternative tools.Still hope docker expert in the community could help the OCA to build a solid and maintainable solution.Best regardsEricOn Wed, Oct 21, 2015 at 5:12 AM David Arnold <firstname.lastname@example.org> wrote:
+ 1 for travis2docker can be a docker2travis as well, but as Eric said, for now the testing infrastructure is stable on travis.
+1 for travisfile2docjerfile, though. Probably revise the base image...
-1 for not compiled sugar code on the user's machine.Nhomar Hernández <email@example.com> schrieb am Di., 20. Okt. 2015 um 15:42:Dear community contributors,
We are currently using docker for our infrastructure and it has been quite a challenge to finetune the setup and deployment but we are finally getting there.One quick question.May be a late question.IF we have already a methodology to create .travis.yml files which can be converted magically to docker files and are linked with the CI.Why the methodology can not be simply create a .travis instead a DockerFIle?It means.If you will deploy a production environment.1.- COpy your template .travis in a repository.2.- Create a Module App which pre-install the modules you need.3.- Run .travis2docker to test and develop.4.- Deploy in production passing a new parameter (to develop such paramenter) which will simply make a -u all.In order to standarize everything it is what we are doing and we haev already such deployment process working like a charm.Regards.PS: It is a question just to know why it is not taking into account.In our case fix things on 4 different environments without automate the control in only one was really time consuming with this approach all environments will be exactly the same.Regards.