- Mailing Lists
- Contributors
- [odoo16 ce] deploy doodba instance on portainer
Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
Partner Types: refactor partner_firstname and introduce partner_type_base
[Odoo CE 17.0] Help needed with client search on budgets
[odoo16 ce] deploy doodba instance on portainer
context: ./odoo
args:
DB_VERSION: "15"
ODOO_VERSION: "16.0"
UID: "${UID:-1000}"
GID: "${GID:-1000}"
by Francesco Ballerini - 10:01 - 17 Nov 2024
Follow-Ups
-
Re: [odoo16 ce] deploy doodba instance on portainer
Thank you Enric, I didn't customize the image yet as I'm still exploring the Doodba environment in my spare time and thus progressing gradually with this task :-)I’ll definitely keep your suggestion in mind. Once again, thank you all for the support.Cheers--FrancescoIl giorno lun 18 nov 2024 alle ore 00:02 Enric Tobella Alomar <notifications@odoo-community.org> ha scritto: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.--FrancescoIl 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 AlomarCEO & Founder_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Francesco Ballerini - 09:46 - 21 Nov 2024 -
Re: [odoo16 ce] deploy doodba instance on portainer
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.--FrancescoIl 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 AlomarCEO & Founder
by Enric Tobella Alomar - 12:01 - 18 Nov 2024 -
Re: [odoo16 ce] deploy doodba instance on portainer
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.--FrancescoIl 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
by Francesco Ballerini - 11:21 - 17 Nov 2024 -
Re: [odoo16 ce] deploy doodba instance on portainer
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
by Graeme Gellatly - 10:26 - 17 Nov 2024