fix(notify_push): improve after review - part 1

Signed-off-by: WrenIX <[email protected]>

Author: wrenix

charts/nextcloud/CHANGELOG.md

@@ -8,3 +8,4 @@ Here we list all major versions and their breaking changes for migration.
 ## v7
 
 - move `metrics.serviceMonitor` to `prometheus.serviceMonitor`: It is used for nextcloud-exporter and notify-push
+- change metrics port of service from 9205 to 9100 to get equal everywhere.

charts/nextcloud/files/notify_push.sh.tpl

@@ -1,4 +1,8 @@
 #!/bin/sh
-/var/www/html/occ app:install notify_push
+/var/www/html/occ app:enable notify_push
 /var/www/html/occ config:app:set notify_push base_endpoint --value="http{{ if .Values.ingress.tls }}s{{ end }}://{{ .Values.nextcloud.host }}{{ .Values.notifyPush.ingress.path }}"
-# /var/www/html/occ notify_push:setup "http{{ if .Values.ingress.tls }}s{{ end }}://{{ .Values.nextcloud.host }}{{ .Values.notifyPush.ingress.path }}"
+{{/*
+The command "setup" runs a check, which need a running nextcloud (but we try to configurate it during startup).
+So that command always failure and we stuck in bootloop. 
+/var/www/html/occ notify_push:setup "http{{ if .Values.ingress.tls }}s{{ end }}://{{ .Values.nextcloud.host }}{{ .Values.notifyPush.ingress.path }}"
+*/}}