1. Mailing Lists
  2. Contributors
  3. Re: [odoo16 ce] deploy doodba instance on portainer

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Automatically Generating Serial Numbers or Lots Upon MO Start in Multi-BoM Scenarios

Re: [odoo16 ce] deploy doodba instance on portainer

Avatar

Re: [odoo16 ce] deploy doodba instance on portainer

by
DIXMIT Consulting SLU, Enric Tobella Alomar
- 17/11/2024 23:58:19
On the creation of the doodba, you were able to set where to store the image.

Just use copier update to reset the values and set it to a registry of your own choice.

Kind regards,

El dom, 17 nov 2024 a las 23:22, Francesco Ballerini (<notifications@odoo-community.org>) escribió:
Oh.. right, after I read your answer I feel like I made a dumb question, well, it is neither the first nor the last time ; ) 

As a developer who is starting to explore the world of deployment, I find your advice very helpful, thanks Graeme. 

--Francesco

Il giorno dom 17 nov 2024 alle ore 22:27 Graeme Gellatly <notifications@odoo-community.org> ha scritto:
It makes no sense to build in a production compose file (note, this is not to say Doodba is wrong, as it needs instructions to make a production build, but that in a real prod environment you wouldn't). You are just pulling an image. Provided you link to your already built image you don't need any of that. Your CI will have the build instructions, tag the image etc, and then you are just pulling it.

On Mon, Nov 18, 2024 at 10:02 AM Francesco Ballerini <notifications@odoo-community.org> wrote:
Hi, 

few days ago I managed to set up a basic doodba instance. We're running this as "prod env" but we're actually just testing it at the moment. The instance is running well, but I've been asked to run this configuration from Portainer if possible.

I'm trying to make some adaptations in order to make it work on portainer, I merged the `common.yaml` and `prod.yaml` in a single compose, added the result in the stack web editor, with some additional adjustments. However I am not sure how to solve this. 

```
build:
      context: ./odoo
      args:
        DB_VERSION: "15"
        ODOO_VERSION: "16.0"
        UID: "${UID:-1000}"
        GID: "${GID:-1000}"
```

when I try to deploy it says that "build" is an unsupported option. Is there any way to adapt this? 
I would also like to ask if someone has to link an example on github or any other platform, I havent find any yet.

Thank you
--Francesco


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

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

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



--
Enric Tobella Alomar
CEO & Founder

Reference