Upgrade should run fine as long as you generate a new compose or stack
Upgrade should run fine as long as you generate a new compose or stack
configuration and upgrade your mailu.env.
configuration and upgrade your mailu.env.
There are some changes to the configuration overrides. Override files are now mounted read-only into the containers.
Please note that the current 1.8 is what we call a "soft release": It’s there for everyone to see and use, but to limit possible user-impact of this very big release, it’s not yet the default in the setup-utility for new users. When upgrading, please treat it with some care, and be sure to always have backups!
The Dovecot and Postfix overrides are moved in their own sub-directory.
There are some changes to the configuration overrides. Override files are now mounted read-only into the containers.
The Dovecot and Postfix overrides are moved in their own sub-directory.
If there are local override files, they will need to be moved from overrides/ to overrides/dovecot and overrides/postfix/.
If there are local override files, they will need to be moved from overrides/ to overrides/dovecot and overrides/postfix/.
See https://mailu.io/1.8/faq.html#how-can-i-override-settings for all the mappings.
See https://mailu.io/1.8/faq.html#how-can-i-override-settings for all the mappings.
Release 1.8 has come a long way again. Due to corona the project slowed down to a crawl. Fortunately new contributors have joined the team what enabled us to still release Mailu 1.8 this year.
Release 1.8 has come a long way again. Due to corona the project slowed down to a crawl. Fortunately new contributors have joined the team what enabled us to still release Mailu 1.8 this year.
For a list of all changes refer to CHANGELOG.md in the root folder of the Mailu github project. Please read the 'Override location changes' section. It contains important information for the people who use the overrides folder.
New functionality
Please note that the current 1.8 is what we call a "soft release": It’s there for everyone to see and use, but to limit possible user-impact of this very big release, it’s not yet the default in the setup-utility for new users. When upgrading, please treat it with some care, and be sure to always have backups!
`````````````````
short summary of new features
For a list of all changes refer to `CHANGELOG.md` in the root folder of the Mailu github project. Please read the 'Override location changes' section. It contains important information for the people who use the overrides folder.
- placeholder1
New Functionality & Improvements
- placeholder2
````````````````````````````````
mention alpine is updated in .... containers.
Here’s a short summary of new features:
other interesting section
- Full-text-search is back after having been disabled for a while due to nasty bugs.
`````````````````````````
- Tons of documentation improvements, especially geared towards new users.
- (Experimental) support for different architectures, such as ARM.
bla bla bla.
- Improvements around webmails, such as CardDAV and a new skin for an updated roundcube, and support for MySQL for it.
more bla bla bla.
- Improvements around relaying, such as AUTH LOGIN and non-standard port support.
- Update to alpine:3.12 as baseimage for most containers.
Override location changes
`````````````````````````
If you have regenerated the Docker compose and environment files, there are some changes to the configuration overrides.
Override files are now mounted read-only into the containers. The Dovecot and Postfix overrides are moved in their own sub-directory. If there are local override files, they will need to be moved from ``overrides/`` to ``overrides/dovecot`` and ``overrides/postfix/``.
Upgrading
Upgrading
`````````
`````````
@ -36,9 +29,16 @@ Upgrade should run fine as long as you generate a new compose or stack
configuration and upgrade your mailu.env.
configuration and upgrade your mailu.env.
Please not that the shipped image for PostgreSQL database is deprecated.
Please not that the shipped image for PostgreSQL database is deprecated.
The shipped image for PostgreSQL is not maintained anymore from release 1.8.
The shipped image for PostgreSQL is not maintained anymore from release 1.8.
We recommend switching to an external database as soon as possible.
We recommend switching to an external database as soon as possible.
Override location changes
^^^^^^^^^^^^^^^^^^^^^^^^^
If you have regenerated the Docker compose and environment files, there are some changes to the configuration overrides.
Override files are now mounted read-only into the containers. The Dovecot and Postfix overrides are moved in their own sub-directory. If there are local override files, they will need to be moved from ``overrides/`` to ``overrides/dovecot`` and ``overrides/postfix/``.
Dario Ernst
4 years ago