|
1 | 1 | # CHANGELOG
|
2 | 2 |
|
| 3 | +### Update Instructions |
| 4 | + |
| 5 | +The ```docker compose``` stack bump version of the provided MariaDB. |
| 6 | + |
| 7 | +Docker Compose does not cleanly stop MySQL by default. |
| 8 | +Therefore, an error can occur when restarting the DB after an update. |
| 9 | +see:https://github.com/MariaDB/mariadb-docker/issues/185 |
| 10 | + |
| 11 | +To cleanly stop MariaDB with docker compose, you can use the following command: |
| 12 | +```dc exec db /usr/bin/mysqladmin -uroot -p shutdown``` |
| 13 | + |
| 14 | +Performing a DB backup is recommended before starting the update procedure. |
| 15 | +You can use the db-backup profile included in the docker-compose.tools.yml file to perform the backup. |
| 16 | + |
| 17 | +Added environement variable |
| 18 | +MARIADB_AUTO_UPGRADE variable is set to 1 (activated) by default and used to automate the upgrade of the mariadb system tables. |
| 19 | +When this environment variable is set, this will run the mariadb-upgrade (https://mariadb.com/kb/en/mariadb-upgrade/), if needed, so any changes in the MariaDB system tables required to expose new features will be made. This may impeed some downgrade options. Unless the environment variable MARIADB_DISABLE_UPGRADE_BACKUP is set, there will be a backup of the system tables created as system_mysql_backup_*.sql.zst in the top level of the data directory to assist in the downgrade if needed. |
| 20 | + |
| 21 | +Keep in mind, the provided MariaDB container in ```docker compose``` and stack is not ready for production as-is and requires adjustments. |
| 22 | +It is recommended to use an external, redundant service for the primary datastore. |
| 23 | + |
| 24 | +#### Steps to Follow for Update docker compose stack |
| 25 | + |
| 26 | + |
| 27 | +1. Perform a backup of the application box and all databoxes published on your MariaDB server (the MariaDB database). |
| 28 | +2. Stop the MariaDB server with (adapt it with your credentials): |
| 29 | + ```sh |
| 30 | + dc exec db /usr/bin/mysqladmin -uroot -p shutdown |
| 31 | + ``` |
| 32 | +3. Take down the Docker stack with: |
| 33 | + ```sh |
| 34 | + dc down |
| 35 | + ``` |
| 36 | +4. Deploy the new Docker stack version. |
| 37 | +5. Bring up your stack with: |
| 38 | + ```sh |
| 39 | + dc up -d |
| 40 | + ``` |
| 41 | + |
| 42 | +**Note:** `dc` is a bash function aliasing `docker compose` with `.env` and `.env.local` values merged. See the [README.md](https://github.com/alchemy-fr/Phraseanet/blob/master/README.md#using-a-envlocal-method-for-custom-env-values) for more details. |
| 43 | + |
| 44 | + |
| 45 | +- **Phraseanet Migration Patch**: |
| 46 | + - A migration script for the configuration file is available. Run the following command in the setup container with Docker if the environment variable `PHRASEANET_UPGRADE=1` is set: |
| 47 | + ``` |
| 48 | + bin/setup system:upgrade |
| 49 | + ``` |
| 50 | +
|
| 51 | +
|
| 52 | +### Stack (Docker Compose and Helm) |
| 53 | +
|
| 54 | +- **MariaDB**: Bumped to 10.11.4 |
| 55 | +
|
3 | 56 | ### Version Summary
|
4 | 57 |
|
5 | 58 | - Bump MariaDB
|
|
15 | 68 |
|
16 | 69 | **Full Changelog**: https://github.com/alchemy-fr/Phraseanet/compare/4.1.15...4.1.16
|
17 | 70 |
|
18 |
| -__ |
19 | 71 | ## 4.1.15
|
20 | 72 |
|
21 | 73 | ### Update Instructions
|
|
0 commit comments