From af6610d590ad2ed29ad797247dc911a79d4a453c Mon Sep 17 00:00:00 2001
From: aptalca <541623+aptalca@users.noreply.github.com>
Date: Fri, 8 Mar 2024 17:37:20 -0500
Subject: [PATCH 1/4] add support for Nextcloud notify push mod

---
 nextcloud.subdomain.conf.sample | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/nextcloud.subdomain.conf.sample b/nextcloud.subdomain.conf.sample
index 5fb72f831..6b82c68b3 100644
--- a/nextcloud.subdomain.conf.sample
+++ b/nextcloud.subdomain.conf.sample
@@ -1,4 +1,4 @@
-## Version 2023/06/24
+## Version 2024/03/09
 # make sure that your nextcloud container is named nextcloud
 # make sure that your dns has a cname set for nextcloud
 # assuming this container is called "swag", edit your nextcloud container's config
@@ -13,6 +13,9 @@
 #    0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it.
 #    1 => 'nextcloud.example.com',
 #  ),
+#
+# The /push/ location block works with the optional notify-push mod:
+# https://github.com/linuxserver/docker-mods/tree/nextcloud-notify-push
 
 server {
     listen 443 ssl http2;
@@ -42,4 +45,11 @@ server {
         # Disable proxy buffering
         proxy_buffering off;
     }
+
+    location ^~ /push/ {
+        include /config/nginx/proxy.conf;
+        include /config/nginx/resolver.conf;
+        proxy_pass http://127.0.0.1:7867/;
+    }
+
 }

From d3293f813b1d8022ba85b531095bfc2ae46041eb Mon Sep 17 00:00:00 2001
From: aptalca <541623+aptalca@users.noreply.github.com>
Date: Tue, 26 Mar 2024 10:57:00 -0400
Subject: [PATCH 2/4] Update date

---
 nextcloud.subdomain.conf.sample | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/nextcloud.subdomain.conf.sample b/nextcloud.subdomain.conf.sample
index 6b82c68b3..62c9d7a60 100644
--- a/nextcloud.subdomain.conf.sample
+++ b/nextcloud.subdomain.conf.sample
@@ -1,4 +1,4 @@
-## Version 2024/03/09
+## Version 2024/03/26
 # make sure that your nextcloud container is named nextcloud
 # make sure that your dns has a cname set for nextcloud
 # assuming this container is called "swag", edit your nextcloud container's config

From a49330d56a5a8d36e7f03c6372481d3bf72b8f47 Mon Sep 17 00:00:00 2001
From: aptalca <541623+aptalca@users.noreply.github.com>
Date: Tue, 26 Mar 2024 14:14:13 -0400
Subject: [PATCH 3/4] apparently I was drunk

---
 nextcloud.subdomain.conf.sample | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/nextcloud.subdomain.conf.sample b/nextcloud.subdomain.conf.sample
index 62c9d7a60..ff8b333bc 100644
--- a/nextcloud.subdomain.conf.sample
+++ b/nextcloud.subdomain.conf.sample
@@ -49,7 +49,8 @@ server {
     location ^~ /push/ {
         include /config/nginx/proxy.conf;
         include /config/nginx/resolver.conf;
-        proxy_pass http://127.0.0.1:7867/;
+        set $upstream_app nextcloud;
+        proxy_pass http://$upstream_app:7867/;
     }
 
 }

From fc96b1f8d54e1c9369bebee48f05209be0be065d Mon Sep 17 00:00:00 2001
From: aptalca <541623+aptalca@users.noreply.github.com>
Date: Tue, 26 Mar 2024 14:30:00 -0400
Subject: [PATCH 4/4] add comments on notify-push

---
 nextcloud.subdomain.conf.sample | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/nextcloud.subdomain.conf.sample b/nextcloud.subdomain.conf.sample
index ff8b333bc..10fa16b36 100644
--- a/nextcloud.subdomain.conf.sample
+++ b/nextcloud.subdomain.conf.sample
@@ -50,6 +50,8 @@ server {
         include /config/nginx/proxy.conf;
         include /config/nginx/resolver.conf;
         set $upstream_app nextcloud;
+        # The url below is for the notify-push service running inside the NC container
+        # The address should be the NC container's address, but the proto and port are the custom service's
         proxy_pass http://$upstream_app:7867/;
     }