Skip to content

Latest commit

 

History

History
executable file
·
29 lines (22 loc) · 1.65 KB

v4-to-v5-migration.md

File metadata and controls

executable file
·
29 lines (22 loc) · 1.65 KB

Deployarr v4.6.1 (and older) to v5.0 Migration

Deployarr v5 Has Many New Features

The following new features required a rewrite of majority of Deployarr code. Backward compatibility could not be maintained.

  • NEW: Deployarr logo and icon.
  • NEW: Local mode for installing apps for local access only (no reverse proxy). This should now remove the Traefik requirement and allow multi-server setups.
  • NEW: Traefik Exposure Modes. Simple - all apps behind Traefik accessible internally and externally. Advanced - control over exposing apps internally, externally, or both.
  • NEW: By default Traefik will use file providers to expose apps via reverse proxy. Previously this was done using Docker labels. Some apps (e.g. Traefik, OAuth, and Authelia), will continue to use labels.

Migrating form v4.6.1 to v5.0

Here are the recommended migration steps:

  1. Stop all running containers or down the entire stack. Keep the stack down (do not restart it).
  2. Run a cold backup from Deployarr Tools menu.
  3. Exit Deployarr v4.6.1
  4. If you have another layer of backup (e.g. Proxmox VM/LXC backup), run it too.
  5. Delete all Deployarr Status files starting 03_, 04_, 05_, and 06_ in /opt/deployarr/status folder.
  6. In the Docker folder, delete the compose folder and the master Docker compose file.
  7. Restart Deployarr v4.6.1 and go through all the steps in sequence. Your appdata should be automatically picked up.
  8. Choose to overwrite when reinstalling Traefik.

Here is a video walk through with some additional explanation: https://youtu.be/_9C7bDPveMg