Skip to Content
  2. Mailing Lists
  3. Contributors
  4. Suggested ways for deploying odoo through docker-odoo-project

Archives

Contributors

New library to migrate Odoo module code "odoo-migrate"

Runbot restart

Suggested ways for deploying odoo through docker-odoo-project

Hi folks,

I’m currently using camptocamp’s docker-odoo-project and akretion’s ak tool for local development and testing. It works like charm, thank you guys for building the great tools.

I have one question though.  Why do we need either use on-build base image or COPY instruction in our own Dockerfile to copy the files and folders into container while we’ve already set the volume like `./odoo:/odoo` in the `docker-compose.yml` file. Is it a redundant job, or did I miss any point here? My guess is that when we copy everything in the container, we can build our own project specific docker image to be used in deployment process. This leads to my second question. How can we use the docker-odoo-project for deployment process? Simple ideas, suggestions or a sophisticated container orchestrating solutions are all welcomed, Thank you very much in advance.

Best regards,

Tony Gu 
Skype: digitalsatori  Tel:56473822
Mobile: 13386068213




by Tony - 03:50 - 13 Oct 2019

Follow-Ups

  • Re: Suggested ways for deploying odoo through docker-odoo-project
    Dear Guewen,

    Thank you very much for the enlightenment. That makes good sense. I will try to implement the CI process as you mentioned and follow your suggested workflow. 

    Best regards,

    Tony Gu 
    Skype: digitalsatori  Tel:56473822
    Mobile: 13386068213




    2019年10月14日 下午2:26，Guewen Baconnier <guewen.baconnier@camptocamp.com> 写道：

    Hi,

    When you work in dev locally, you wouldn't really need to COPY the files in the docker image, as, as you say, there is the volume.
    However, as soon as you want to deploy, you should not use the git repository anymore.
    The workflow we use is to build the image in CI (hence the COPY), run the tests in a container started from the new image, when tests are successful, the image is pushed to a registry. From there, the image can be deployed to test/staging/production environments.

    Guewen


    On Sun, Oct 13, 2019 at 3:51 AM Tony Gu <tony@openerp.cn> wrote:
    Hi folks,

    I’m currently using camptocamp’s docker-odoo-project and akretion’s ak tool for local development and testing. It works like charm, thank you guys for building the great tools.

    I have one question though.  Why do we need either use on-build base image or COPY instruction in our own Dockerfile to copy the files and folders into container while we’ve already set the volume like `./odoo:/odoo` in the `docker-compose.yml` file. Is it a redundant job, or did I miss any point here? My guess is that when we copy everything in the container, we can build our own project specific docker image to be used in deployment process. This leads to my second question. How can we use the docker-odoo-project for deployment process? Simple ideas, suggestions or a sophisticated container orchestrating solutions are all welcomed, Thank you very much in advance.

    Best regards,

    Tony Gu 
    Skype: digitalsatori  Tel:56473822
    Mobile: 13386068213




    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe


    by Tony - 01:01 - 14 Oct 2019
  • Re: Suggested ways for deploying odoo through docker-odoo-project
    Hi,

    When you work in dev locally, you wouldn't really need to COPY the files in the docker image, as, as you say, there is the volume.
    However, as soon as you want to deploy, you should not use the git repository anymore.
    The workflow we use is to build the image in CI (hence the COPY), run the tests in a container started from the new image, when tests are successful, the image is pushed to a registry. From there, the image can be deployed to test/staging/production environments.

    Guewen


    On Sun, Oct 13, 2019 at 3:51 AM Tony Gu <tony@openerp.cn> wrote:
    Hi folks,

    I’m currently using camptocamp’s docker-odoo-project and akretion’s ak tool for local development and testing. It works like charm, thank you guys for building the great tools.

    I have one question though.  Why do we need either use on-build base image or COPY instruction in our own Dockerfile to copy the files and folders into container while we’ve already set the volume like `./odoo:/odoo` in the `docker-compose.yml` file. Is it a redundant job, or did I miss any point here? My guess is that when we copy everything in the container, we can build our own project specific docker image to be used in deployment process. This leads to my second question. How can we use the docker-odoo-project for deployment process? Simple ideas, suggestions or a sophisticated container orchestrating solutions are all welcomed, Thank you very much in advance.

    Best regards,

    Tony Gu 
    Skype: digitalsatori  Tel:56473822
    Mobile: 13386068213




    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: https://odoo-community.org/groups?unsubscribe

    by Guewen Baconnier - 08:25 - 14 Oct 2019