Skip to content

Latest commit

 

History

History
executable file
·
35 lines (26 loc) · 1.92 KB

v4-to-v5-migration.md

File metadata and controls

executable file
·
35 lines (26 loc) · 1.92 KB

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

Deployarr v5 Has Manu 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.

Known Issues

Apps requiring a database (e.g. Guacamole, Speedtest-Tracker, Nextcloud, etc.) will fail. Deployarr is not capable of reusing existing databases during re-installation. Possible Fixes:

  1. Delete the associated MariaDB database and user using phpMyAdmin or Adminer. Then reinstall the app. New database and user will be created.
  2. Reinstall the App and manually change database username and password in Docker Secrets folder to reflect the correct username and password (can be found in the previous secrets folder).

This will be fixed in the next release.

Migrating form v4.6.1 to v5.0

Here are the recommended migration steps:

  1. Stop all running containers or down the entire stack.
  2. Run a cold backup from Deployarr Tools menu.
  3. If you have another layer of backup (e.g. Proxmox VM/LXC backup), run it too.
  4. Delete everything inside Docker Folder, EXCEPT, .env, secrets folder, and appdata folder.
  5. Download Deployarr v5.
  6. Reinstall install apps (check known issues above).