Add documentation if you want to use a custom network

[hey-johnnypark]

CURRENT

We are using the standard networks that Docker provides. This can cause trouble for Health Departments which have conflicting IP Address Ranges.

TARGET

We should add a documentation about how to create your custom network configuration. We already received great input from one of our clients.

[jekutzsche]

Shouldn't we rather change the Compose files to our own network and thus avoid such problems in general?

[jekutzsche]

I have now looked deeper into the topic and think that this issue is unnecessary as it is based on a wrong assumption.

We are not using Docker's default network. We use Docker-Compose and it automatically creates its own bridge network for the containers it launches.

This network has its own network segment and is independent of the other networks. Docker chooses the segment and IP address range on its own. Only in very justified exceptions should be deviated from this.

I consider my last question, or rather my related suggestion, to be invalid and in principle already fulfilled.

Of course, it's possible I'm misunderstanding the issue. Therefore, I will leave it open until January (return of @hey-johnnypark) and then close it if necessary.