You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*[Using the nextcloud docker image auto-configuration via env vars](#using-the-nextcloud-docker-image-auto-configuration-via-env-vars)
@@ -500,6 +501,38 @@ The nextcloud deployment includes a series of different probes you can use to de
500
501
> [!Note]
501
502
> If you are getting errors on initialization (such as `Fatal error: require_once(): Failed opening required '/var/www/html/lib/versioncheck.php'`, but you can get other errors as well), a good first step is to try and enable the startupProbe and/or increase the `initialDelaySeconds` for the `livenessProbe` and `readinessProbe` to something much greater (consider using `120` seconds instead of `10`. This is an especially good idea if your cluster is running on older hardware, has a slow internet connection, or you're using a slower storage class, such as NFS that's running with older disks or a slow connection.
502
503
504
+
### Notify Push
505
+
506
+
We include an optional Client Push [nextcloud/notify_push](https://github.com/nextcloud/notify_push).
| `notifyPush.redisURLEnv` | option to set the redis_url per env (if a external redis is used) e.g.: `value: ""`or `valueFrom: {secretKeyRef:{name:"",key:""}}` | `""` |
| `notifyPush.service.type` | notify-push: Kubernetes Service type | `ClusterIP` |
526
+
| `notifyPush.service.loadBalancerIP` | Use serviceLoadBalancerIP to request a specific static IP, otherwise leave blank | `nil` |
527
+
| `notifyPush.service.nodePort` | notify-push: NodePort for service type NodePort | `nil` |
528
+
| `notifyPush.service.annotations` | Additional annotations for service notify-push | `{}` |
529
+
| `notifyPush.service.labels` | Additional labels for service notify-push | `{}` |
530
+
| `notifyPush.ingress.path` | Add path in default ingress to notify_push service | `/push` |
531
+
| `notifyPush.ingress.pathType` | PathType for additional path in default ingress for notify-push path | `Prefix` |
532
+
533
+
> [!Note]
534
+
> notify-push needs an redis (redis.enabled=true or notifyPush.redisURLEnv={...})
535
+
503
536
### Collabora Configuration
504
537
505
538
This section provides options to enable and configure the Collabora Online server within your deployment. Please ensure to review the [Collabora Online Helm chart documentation](https://github.com/CollaboraOnline/online/tree/master/kubernetes/helm/collabora-online) for additional details and recommended values.
0 commit comments