Upgrading From 6.x to 7.x and target docker-compose.yml files?

1

TLDR; What changes are made, if any, to the docker-compose.yml files when upgrading from 6.x to 7.x? What customized changes are preserved, if any? What should someone expect when upgrading to 7.x if they use a modified docker-compose.yml file within Wappler?

Explanation:
My target docker yml files for staging and production have been mildly customized. My Digital Ocean droplets (server instances) each have a D.O. storage volume mounted and used for persistent storage of large uploaded user files. Therefore, I've had to modify Wappler's implemented docker volumes section in docker-compose.yml to ensure docker uses my attached volume instead of writing/saving everything to the default web volume under /opt/node_app/

I keep backups of docker-compose.yml because the implementation of Traefik removed my configurations. Therefore, while I'm confident I could apply my custom configurations to the yml file again, I'm curious to know what to expect upon upgrade. TIA

2

We use 7.5 and will update to 7.6 later. Last time I made a modification to a Target (in Wappler itself) it wiped my cusomtisations and had to revert to a backup (sub domains for Traefik). As far as I know upon modifying the Target and saving any custom entries will be cleared/dismissed and you will have to enter them again. Not sure if this behavior has changed however..?