Before updating scaffolding from new db

This produced an absurd situation where we pushed a default dependency that was never actually used.

Since #213 was merged, one side effect was that the git version didn't get installed.

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.

I wasn't expecting this breakage, but it happens to be better to have it than to fix it.

We needed a way to define defaults in odoo config files which doesn't conflict with the problem of odoo v11 and v12 not allowing duplicate sections or keys, so we ended up creating a smarter config merger that allowed that. 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.

Besides adding some CPU consumption (not much, honestly), these containers also exhaust easily the available IPv4 address pool since they require creating one extra network per project to perform the isolation correctly. This version contains some bugs that are fixed in 3.5.6, which is the latest python 3.5 bugfix release. The base image is also a Debian 9 base, but it includes many build dependencies, since it is based on when installing any pip dependency with C extensions. In fact, if you install it, you'd have the included-and-locally-built python 3.5.6 headers, and the apt-installed python 3.5.3 headers, which could cause confusion and could cause some packages to appear to be installed at image build time, but not be executable later at container execution time. Current fonts shipped by Debian do not render fine in Adobe PDF on Windows and Mac OS. When updating scaffolding of current deployments of any of those test environments and re-deploying, you'll probably see a new "prod" database being created. Python 3.5 is the version that Odoo SA uses in their deployments, so the project leader, @pedrobaeza, considers this version is more safe to use in Doodba than the currently latest stable version of Python: 3.7.

When you update the scaffolding, you won't be able to deploy test environments if your servers are not ready for the change. If you were relying on this feature, you will see that your test/prod builds are missing the requirements that they were getting automatically from the linked repositories. In case you were installing python packages through and, thus, installs it. Scaffolding: Tecnativa/[email protected] When #199 gets merged. Since all the code you write for Odoo 12.0 should be Python 3.5 compatible, as Odoo itself, nothing should break. Git was never a good place to store secrets in plain text.

and get no conflicts, this change might get unnoticed and land into your deployment.

If you rely on the pip-released version of openupgradelib, you could get unknown results. This release fixes the infamous bug wkhtmltopdf/wkhtmltopdf#2711, and according to odoo/odoo#21255 (comment) it should be mostly safe to upgrade from current 0.12.4 version.

before updating scaffolding from new db-79before updating scaffolding from new db-64before updating scaffolding from new db-61

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

Join our conversation (91 Comments).
Click Here To Leave Your Comment Before updating scaffolding from new db.


Leave a Reply

Your email address will not be published. Required fields are marked *