github/reverse-proxy-confs
1
0
Fork 0
mirror of https://github.com/linuxserver/reverse-proxy-confs.git synced 2025-08-22 06:13:49 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Update nextcloud's instructions

Browse source
This commit is contained in:
quietsy 2024-07-06 17:49:40 +03:00
commit 8ee43598f1
2 changed files with 14 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

17
nextcloud.subdomain.conf.sample
View file

@ -1,18 +1,15 @@
## Version 2024/04/25 ## Version 2024/07/06
# make sure that your nextcloud container is named nextcloud # make sure that your nextcloud container is named nextcloud
# make sure that your nextcloud container is on the same docker network as swag
# make sure that your dns has a cname set for nextcloud # make sure that your dns has a cname set for nextcloud
# assuming this container is called "swag", edit your nextcloud container's config # edit your nextcloud container's config located at
# located at /config/www/nextcloud/config/config.php and add the following lines before the ");": # /config/www/nextcloud/config/config.php and add the following lines before the ");":
# 'trusted_proxies' => [gethostbyname('swag')], # 'trusted_proxies' => ['172.16.0.0/12'],
# 'overwrite.cli.url' => 'https://nextcloud.example.com/', # 'overwrite.cli.url' => 'https://nextcloud.example.com/',
# 'overwritehost' => 'nextcloud.example.com', # 'overwritehost' => 'nextcloud.example.com',
# 'overwriteprotocol' => 'https', # 'overwriteprotocol' => 'https',
# # add your domain name to the trusted domains array:
# Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this: # 'trusted_domains' => ['nextcloud.example.com'],
# array (
# 0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it.
# 1 => 'nextcloud.example.com',
# ),
server { server {
listen 443 ssl http2; listen 443 ssl http2;

17
nextcloud.subfolder.conf.sample
View file

@ -1,17 +1,14 @@
## Version 2024/04/25 ## Version 2024/07/06
# make sure that your nextcloud container is named nextcloud # make sure that your nextcloud container is named nextcloud
# make sure that your nextcloud container is on the same docker network as swag
# make sure that nextcloud is set to work with the base url /nextcloud/ # make sure that nextcloud is set to work with the base url /nextcloud/
# Assuming this container is called "swag", edit your nextcloud container's config # edit your nextcloud container's config located at
# located at /config/www/nextcloud/config/config.php and add the following lines before the ");": # /config/www/nextcloud/config/config.php and add the following lines before the ");":
# 'trusted_proxies' => [gethostbyname('swag')], # 'trusted_proxies' => ['172.16.0.0/12'],
# 'overwritewebroot' => '/nextcloud', # 'overwritewebroot' => '/nextcloud',
# 'overwrite.cli.url' => 'https://example.com/nextcloud', # 'overwrite.cli.url' => 'https://example.com/nextcloud',
# # add your domain name to the trusted domains array:
# Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this: # 'trusted_domains' => ['nextcloud.example.com'],
# array (
# 0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it.
# 1 => 'example.com',
# ),
location ^~ /.well-known { location ^~ /.well-known {
# The rules in this block are an adaptation of the rules # The rules in this block are an adaptation of the rules