Finish OnlyOffice Setup (#13)

* Add newlines in output.

* Remove fancy DNS attempts to get NC and OO to talk. Just had to give NC the local IP through the Advanced settings. Yay!!

Config/Nextcloud/docker-compose.yml

@@ -5,6 +5,12 @@
 # Changelog:
 # 2023-07-16 Change from mariadb:10.5 to 10.6.
 # 2023-08-20 Add Redis. (https://markontech.com/docker/setup-nextcloud-with-redis-using-docker/)
+# 2023-08-21 Got NC to work with OO after specifying the Advanced parameters!
+#              OO Address: https://FQDN-For-Reverse-Proxied-OO-Server
+#              OO Secret: Contents-Of-$JWT_SECRET
+#              OO Header:
+#              OO Internal Address: http://docker-server-ip:8000
+#              NC Internal Address: http://docker-server-ip:8080
 
 version: '3'
 
@@ -47,5 +53,3 @@ services:
       - PHP_UPLOAD_LIMIT=$PHP_UPLOAD_LIMIT
       - REDIS_HOST=$REDIS_HOST
       - REDIS_HOST_PASSWORD=$REDIS_HOST_PASSWORD
-    #dns:
-    #  - $DNS

Config/Nextcloud/env.example

@@ -16,14 +16,3 @@ MYSQL_PASSWORD=changeme
 
 REDIS_HOST=redis
 REDIS_HOST_PASSWORD=someredispassword
-
-## Other ##
-
-# This has not helped, not sure why containers are not uing hosts's DNS, or why
-#  the requests are failing. Needs further research/testing but works on Ubuntu
-#  laptop, just not Debian VM. VM can use the DNS server properly though.
-### # If you have both Nextcloud and OnlyOffice on the same internal network you
-### #   will likely want to set this to an internal DNS server. Some routers will
-### #   drop traffic if an internal IP tries to communicate with the WAN IP, causing
-### #   the curl to OnlyOffice's /healthcheck to fail. Do the same in both configs.
-### DNS=10.110.1.53

Config/OnlyOffice/docker-compose.yml

@@ -13,5 +13,3 @@ services:
       - 4443:443
     environment:
       - JWT_SECRET=$JWT_SECRET
-    #dns:
-    #  - $DNS

Config/OnlyOffice/env.example

@@ -4,14 +4,3 @@
 
 # Secret
 JWT_SECRET=abc123
-
-## Other ##
-
-# This has not helped, not sure why containers are not uing hosts's DNS, or why
-#  the requests are failing. Needs further research/testing but works on Ubuntu
-#  laptop, just not Debian VM. VM can use the DNS server properly though.
-### # If you have both Nextcloud and OnlyOffice on the same internal network you
-### #   will likely want to set this to an internal DNS server. Some routers will
-### #   drop traffic if an internal IP tries to communicate with the WAN IP, causing
-### #   the curl to OnlyOffice's /healthcheck to fail. Do the same in both configs.
-### DNS=10.110.1.53

bin/start.sh

@@ -16,9 +16,12 @@ fi
 
 ## Main ##
 
+echo "Starting all containers."
+
 cd $DOCKER_HOME/Config
 for dir in `ls`; do
 	[ -d $dir ] && cd $dir || continue
+	echo ""
 	pwd
 	[ -e Dockerfile ] && docker compose build
 	[ -e docker-compose.yml ] && docker compose up -d

bin/stop.sh

@@ -16,9 +16,12 @@ fi
 
 ## Main ##
 
+echo "Stopping all containers."
+
 cd $DOCKER_HOME/Config
 for dir in `ls`; do
 	[ -d $dir ] && cd $dir || continue
+	echo ""
 	pwd
 	[ -e docker-compose.yml ] && docker compose down
 	cd ..