search

cloudflavor / odoo-cloud

Odoo on Kubernetes demo application. (with minikube and standalone)
Apache License 2.0
44 stars 56 forks source link

Custom Odoo Add-ons #3

Open gridworkz opened 6 years ago

gridworkz commented 6 years ago

Hi:

How would I integrate a custom Odoo add-ons directory into this configuration?

Cheers, Dave

PI-Victor commented 6 years ago

@gridworkz i believe you can do that with configmaps, but i'm not sure to be honest. i could explore that at some point if you haven't already figured it out by yourself and are still interested.

PI-Victor commented 6 years ago

oh, and, alternatively, the simpler approach would be to bake it inside the Docker image that is used for the build. Or build your own on top of the original base image with the added directory.

gridworkz commented 6 years ago

Hi:

Thanks for the ideas. Let me give this some thought. The way it's done without Docker is the custom addons directory resides on an NFS configured drive then all the Odoo instances can access it via NFS mount initiated upon startup. This way, any new addons are added in one place and automatically available to the nodes (without having to install the new addon on each Odoo instance).

Cheers, Dave

On Tue, Jun 19, 2018 at 8:01 AM, Palade Ionuț-Victor < notifications@github.com> wrote:

oh, and, alternatively, the simpler approach would be to bake it inside the Docker image https://github.com/cloudflavor/odoo-docker that is used for the build. Or build your own on top of the original base image with the added directory.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cloudflavor/odoo-k8s/issues/3#issuecomment-398374238, or mute the thread https://github.com/notifications/unsubscribe-auth/ASt2yPq5pd83ukBtt7WMW0dDUtY9FCkKks5t-OgXgaJpZM4UhXjq .