Migration to v2 on instance created from setup script

[federicochiesa]

Our instance has been created by the setup script, so we have a single docker compose file with the database, the caddy proxy, and the defguard components all in one docker compose file, and until now I updated by changing the versions in the .env file that was created along the docker compose yaml.

I just watched the video in the email that announced the v2 beta and I'm not certain on how to upgrade our installation since it's very different from having all components on a single host and in a single docker file.

[teon]

@federicochiesa the protocol is simple:
0. ALWAYS backup your database / whole setup before migration/testing.
2. Update docker tags to "2.0.0-beta1"
3. Add volumes for proxy (now edge) and gateway - where SSL certificates for these components will be held:

   volumes:
      - /path/where/ssl/will/be/for/edge/gateway:/etc/defguard/certs

And that's it. After launching you will need to adopt the edge and gateway - in the wizard where you need to give the IP of these components just enter their docker names - similarly as on these video: https://youtu.be/DWQlyHmqMlo?t=402

[teon]

@federicochiesa here is also our official Docker compose for 2.0:
https://github.com/DefGuard/deployment/blob/main/docker-compose2.0/docker-compose.yaml

[federicochiesa]

Thank you. I'll be testing v2 soon.