Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update nextcloud's instructions #684

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update nextcloud's instructions #684

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 7 additions & 10 deletions nextcloud.subdomain.conf.sample
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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 on the same docker network as swag
# make sure that your dns has a cname set for nextcloud
# assuming this container is called "swag", edit your nextcloud container's config
# located at /config/www/nextcloud/config/config.php and add the following lines before the ");":
# 'trusted_proxies' => [gethostbyname('swag')],
# edit your nextcloud container's config located at
# /config/www/nextcloud/config/config.php and add the following lines before the ");":
# 'trusted_proxies' => ['172.16.0.0/12'],
# 'overwrite.cli.url' => 'https://nextcloud.example.com/',
# 'overwritehost' => 'nextcloud.example.com',
# 'overwriteprotocol' => 'https',
#
# Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this:
# array (
# 0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it.
# 1 => 'nextcloud.example.com',
# ),
# add your domain name to the trusted domains array:
# 'trusted_domains' => ['nextcloud.example.com'],

server {
listen 443 ssl http2;
Expand Down
17 changes: 7 additions & 10 deletions nextcloud.subfolder.conf.sample
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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 on the same docker network as swag
# 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
# located at /config/www/nextcloud/config/config.php and add the following lines before the ");":
# 'trusted_proxies' => [gethostbyname('swag')],
# edit your nextcloud container's config located at
# /config/www/nextcloud/config/config.php and add the following lines before the ");":
# 'trusted_proxies' => ['172.16.0.0/12'],
# 'overwritewebroot' => '/nextcloud',
# 'overwrite.cli.url' => 'https://example.com/nextcloud',
#
# Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this:
# array (
# 0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it.
# 1 => 'example.com',
# ),
# add your domain name to the trusted domains array:
# 'trusted_domains' => ['nextcloud.example.com'],

location ^~ /.well-known {
# The rules in this block are an adaptation of the rules
Expand Down