mirror of
https://github.com/mealie-recipes/mealie.git
synced 2026-06-14 04:50:13 -04:00
* Dev docs: tests, postgres/psycog2 * Update pull request process. * Add Food/Unit parsing instructions to the FAQ * Update docker composes: mealie-data now local to docker-compose rather than hidden in docker volume dir! postgres points to 1.0.0b5 * sqlite docker-compose: mealie-data now local rather than hidden in docker volumes * Merge Intro FAQ into main FAQ * Progress on docs * Add Advanced and v1b5 to docs index * v1b5 changelog consistency with other changelogs * Features: fix wrong link, name buttons for clarity * Migration: link to github releases * Updating: link to migration page, format docker cmds * FAQ: update smart ingredient formatting * Intro: fix typos * API: update for newbie clarity * Roadmap: update feature request & progress mechanism * iOS shortcut: fix broken image links * installation: add SMTP google app passwords * Postgres: add header note on why. * Update Groups doc per Discord discussion * mealie-data back into docker default volume path
25 lines
1.1 KiB
Markdown
25 lines
1.1 KiB
Markdown
# Updating Mealie
|
|
|
|
!!! warning "Read The Release Notes"
|
|
You MUST read the release notes prior to upgrading your container. Mealie has a robust backup and restore system for managing your data. Pre-v1.0.0 versions of Mealie use a different database structure, so if you are upgrading from pre-v1.0.0 to v1.0.0, you MUST backup your data and then re-import it. Even if you are already on v1.0.0, it is strongly recommended to backup all data before updating.
|
|
|
|
### Before Upgrading
|
|
- Read The Release Notes
|
|
- Identify Breaking Changes
|
|
- Create a Backup and Download from the UI
|
|
- Upgrade
|
|
|
|
## Upgrading to Mealie v1
|
|
If you are upgrading from pre-v1.0.0 to v1.0.0, make sure you read [Migrating to Mealie v1](./migrating-to-mealie-v1.md)!
|
|
|
|
## Backing Up Your Data
|
|
|
|
[See Backups and Restore Section](../getting-started/usage/backups-and-restoring.md) for details on backing up your data
|
|
|
|
## Docker
|
|
For all setups using Docker the updating process looks something like this
|
|
|
|
- Stop the container using docker-compose down
|
|
- Pull the latest image using `docker-compose pull`
|
|
- Start the container again using `docker-compose up -d`
|