all-in-one/tests/QA/060-environmental-variables.md
szaimen 7ae718300f allow to adjust the talk port
Signed-off-by: szaimen <szaimen@e.mail.de>
2022-07-04 14:17:33 +02:00

2.2 KiB

Environmental variables

  • When starting the mastercontainer with -e APACHE_PORT=11000 on a clean instance, the domaincheck container should be started with that same port published. That makes sure that also the Apache container will use that port later on. Using a value here that is not a port will not allow the mastercontainer to start correctly.
  • When starting the mastercontainer with -e TALK_PORT=3479 on a clean instance, the talk container should use this port later on. Using a value here that is not a port will not allow the mastercontainer to start correctly. Also it should stop if apache_port and talk_port are set to the same value.
  • Make also sure that reverse proxies work by following https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md#reverse-proxy-documentation and following 001-initial-setup.md and 002-new-instance.md
  • When starting the mastercontainer with -e SKIP_DOMAIN_VALIDATION=true on a clean instance, it should skip the domain verification. So it should accept any domain that you type in then.
  • When starting the mastercontainer with -e NEXTCLOUD_DATADIR="/mnt/testdata" it should map that location from /mnt/testdata to /mnt/ncdata inside the Nextcloud container. Not having adjusted the permissions correctly before starting the Nextcloud container the first time will not allow the Nextcloud container to start correctly. See https://github.com/nextcloud/all-in-one#how-to-change-the-default-location-of-nextclouds-datadir for allowed values.
  • When starting the mastercontainer with -e NEXTCLOUD_MOUNT="/mnt/" it should map /mnt/ to /mnt/ inside the Nextcloud container. See https://github.com/nextcloud/all-in-one#how-to-allow-the-nextcloud-container-to-access-directories-on-the-host for allowed values.
  • When starting the mastercontainer with -e DOCKER_SOCKET_PATH="/var/run/docker.sock.raw" it should map /var/run/docker.sock.raw to /var/run/docker.sock inside the watchtower container which allow to update the mastercontainer on macos and with docker rootless.

You can now continue with 070-timezone-change.md