Before updating scaffolding from new db edward norton dating

containers (which came in flavors inboxfake and inboxreal) are being dropped from the scaffolding. Network isolation is by far more powerful that the proxies, and reduces maintenance and inflexibility burden in projects.

Besides, configuring Odoo to fetch mail from real host names reduces the diff between a Odoo deployment from the 90's and a modern Doodba-based one.

Dockerfile#L11-L61 Those do the magic of Doodba, but we can safely split them into 2: onbuild and not onbuild.

We'll use this chance to enhace project branding by renaming it and the Docker Hub images.

Please subscribe here if you use this project in production, because you will care of these changes.

However, deprecated images will continue to be available in the same place (just not updated anymore), and current scaffolding-based deployments will continue to work, as their code is local and doesn't depend on public official scaffolding. When #165 and Tecnativa/doodba-scaffolding#5 get merged. The testing environments already have the requirement to run in a server that declares an example does not seem like adding much difficulty to the current status.

We will soon start defaulting to use https://github.com/Tecnativa/docker-duplicity project to generate backups. into glacier after 1 month, and to expire everything after 3 months. Deprecated since 2 months ago, it's time to remove it... Builds using that file will not get pip dependencies installed. This means that Docker will create a new volume and leave the older one dangling, meaning you could get the surprise of having an empty Odoo database.

https://github.com/Tecnativa/docker-server-backup will start being unmaintained. If you need to restore an old backup, you will have to roll back your project to the last commit before updating the scaffolding, and use the old restore process. More dangerous is that if you execute was introduced in #84 last week, so not much chance it's widely used out there.

The default scaffolding image will use Postgres 10. OTOH, this will reduce the amount of containers to be booted up by 5 for each testing deployment.

Since that's the default recommended environment to use for running our QA suite, this can mean quicly hundreds of containers. Images: environments, which never had data persistence guarantees.

Leave a Reply