Community mailing list archives
Re: docker: must longpolling_port be accessible from outsideby
Great to hear! What still pops to my mind to help you get going with docker: You probably might have a look at docker-compose. It works on all platforms now. And if you want to dive into some afterthought of the afterthought, I would suggest having a look on rancher. Best, David
And if you can share something of your tool chain, I'm interested at looking at it.
Hi David,<blockquote cite="mid:CAOLEt-H0bsAwd_eWcJkKm9+xNOxSAe3iY5nJzO4wEyDTxy1UrA@mail.gmail.com" type="cite">
On 04.11.2015 07:03, David Arnold wrote:
We did write something like voodoo, but with focus on the management of projects.Hi Robert,
If you just want odoo web page you're fine with exposing only 8069.If you need longpolling, then also expose 8072. longpolling is AFAIK used by the live chat. But my knowledge is shallow here. See also: https://en.wikipedia.org/wiki/Push_technology#Long_polling
So: docker run ... -p 80:8069 ... to have odoo on standard http port.
I'm curious: you said "multiple". If you refer to an odoo and a db container, you're all set. If you try to attempt to load balance requests to different odoo containers to share the workload, you need to solve two more problems of the stateful odoo application: filestore (solution by ccomb: https://anybox.fr/blog/postgresql-large-object-storage-for-odoo) and session, as both are stored in the local filesystem and therefore stateful to a specific container unless solved otherwise...
It reflects a set of tools we used for years with an other framework (zope/plone). The docker part is more of an afterthought as we only start to use docker.
We do not yet use multiple containers for one odoo instance. And even if we would I probably would prefer a solution that does not store blobs in the db.
<blockquote cite="mid:CAOLEt-H0bsAwd_eWcJkKm9+xNOxSAe3iY5nJzO4wEyDTxy1UrA@mail.gmail.com" type="cite">
Saludos CordialesDavid Arnold
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.
2015-11-02 14:12 GMT-05:00 Gérald Godonou-Dossou <firstname.lastname@example.org>:
8069 is the default port on odoo. but if you use a docker you can specifie your port.i think you have to configure it first
You are right!
Default port is 8069
But you can review your configuration file of odoo or command executed with "ps aux"Hi Moy Lop,
What Robert means is to ask which ports Odoo needs to be accessible from outside the docker for proper functioning of Odoo.
It was not a Docker question, so the Docker documentation doesn't help with Robert's question.
LeoHi there, I am setting up multiple docker containers to run odoo inside. Now I wonder what ports must be accessible from outside. I *assume* it is only 8069.
Ing. conception en Génie Electrique
Intégrateur de solution --- Certifié CCNA
ID skype: godsun87
Tel : (+229) 977-687-39
Nos pensées définissent notre futur
redCOR AG, robert rottermann