Question: Test setup

[Mailblocker]

Hi,
having some problems after upgrading my nextcloud docker setup (link) got me thinking about a testing environment/setup.

My approach would be the following:

1. Move all configurable settings from docker-compose.yml to .env
2. Change all volume paths used in docker-compose.yml to relative volume paths.
3. Copy all docker related files, like docker-compose.yml and the config files of the containers to a second directory e.g from ~/docker to ~/docker_testing.
4. Create a new .env file and replace all letsencrypt environment domain variables with a prefix "testing"
5. Setup my domain CNAME handling for the new "testing" domains

In case of an update I would try to update the ~/docker_testing setup by stopping the ~/docker setup first then upgrading via docker pull and see if it still runs.

Would this work?
Do I run into certificate problems using the same domain name (limited number of certs per domain)?
Is there a better way to do this?

Thanks!

[Mailblocker]

In case anyone needs this:

In general my idea worked. I needed to add the following steps:

1. Removed container_name: name_of_service from all service entries in my docker compose file. Otherwise the testing setup creates the same names for the containers and conflicts with them.
2. Added COMPOSE_PROJECT_NAME=test and =release to the .env files of my docker setups. This creates the containernames with the prefixes test and release and prevents conflicts between the names of the containers of the test and release setup.