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!!
This commit is contained in:
		@@ -13,5 +13,3 @@ services:
 | 
			
		||||
      - 4443:443
 | 
			
		||||
    environment:
 | 
			
		||||
      - JWT_SECRET=$JWT_SECRET
 | 
			
		||||
    #dns:
 | 
			
		||||
    #  - $DNS
 | 
			
		||||
 
 | 
			
		||||
@@ -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
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user