Add per-workload replicas values and a chart-global scaleDown flag

Every Deployment/StatefulSet now takes its replica count from a replicas
value (default 1, explicit 0 allowed) via a new per-chart <chart>.replicas
helper; the helper uses a kindIs "invalid" nil check so an explicit 0 is
not swallowed by Helm's default function. A chart-global scaleDown flag
(default false) takes precedence: it renders every workload with
replicas: 0 and suspends the paperless-ngx consume CronJob, stopping the
app without uninstalling it (PVCs, Secrets, Services and Ingress remain).

Defaults leave the rendered manifests byte-identical to main, so all
published charts get a minor version bump; the template-chart carries the
reference helper implementation and stays unversioned.

Fixes #25

zipline/Chart.yaml

@@ -15,7 +15,7 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 4.0.0+up4.6.4
+version: 4.1.0+up4.6.4
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to

zipline/templates/_helpers.tpl

@@ -83,3 +83,34 @@ results are printed without a decimal point.
 {{- printf "%v%s" $product $suffix -}}
 {{- end -}}
 {{- end -}}
+
+{{/*
+Render the replica count for a Deployment/StatefulSet.
+
+Input: dict
+  "scaleDown"  the chart-global .Values.scaleDown flag (may be nil)
+  "replicas"   the workload's replicas value (may be nil)
+
+Rules (issue #25):
+  - scaleDown: true takes precedence and always yields 0.
+  - otherwise an explicitly set replicas value is used as given, including an
+    explicit 0 — Helm's "default" would swallow 0, hence the explicit
+    kindIs "invalid" nil check.
+  - a missing replicas value defaults to 1.
+
+Usage (the values path to the workload's replicas varies per chart):
+  replicas: {{ include "zipline.replicas" (dict "scaleDown" .Values.scaleDown "replicas" .Values.<app>.replicas) }}
+
+NOTE: like the resources helper above, this is duplicated into every chart's
+templates/_helpers.tpl with the chart's name as define prefix. This file in
+template-chart is the reference implementation.
+*/}}
+{{- define "zipline.replicas" -}}
+{{- if .scaleDown -}}
+0
+{{- else if not (kindIs "invalid" .replicas) -}}
+{{- .replicas -}}
+{{- else -}}
+1
+{{- end -}}
+{{- end -}}

zipline/templates/zipline.sfs.yaml

@@ -7,7 +7,7 @@ spec:
     matchLabels:
       app: "{{ .Release.Name }}-{{ .Chart.Name }}-sfs"
   serviceName: "{{ .Release.Name }}-{{ .Chart.Name }}-service"
-  replicas: 1
+  replicas: {{ include "zipline.replicas" (dict "scaleDown" .Values.scaleDown "replicas" .Values.zipline.replicas) }}
   template:
     metadata:
       labels:

zipline/values.yaml

@@ -1,3 +1,9 @@
+# Scale the whole chart down without uninstalling it: scaleDown: true renders
+# every Deployment/StatefulSet with replicas: 0 (and suspends CronJobs) and
+# takes precedence over any per-workload replicas value. PVCs, Secrets and
+# Services stay in place; scaleDown: false brings the workloads back up.
+scaleDown: false
+
 config:
   storage: 50Gi
   storageClass: longhorn
@@ -7,6 +13,9 @@ config:
   domain: null
   maxUploadFileSize: 30m
 zipline:
+  # Replica count for this workload; 0 is allowed and scales it down.
+  # The chart-global scaleDown flag takes precedence.
+  replicas: 1
   # The upstream image ships no dedicated user, but the Node.js server runs
   # fine as an arbitrary non-root uid; fsGroup makes the uploads PVC writable.
   securityContext:
@@ -58,4 +67,4 @@ zipline:
     requests:
       cpu: 0.1
       memory: 265Mi
-      ephemeralStorage: 100Mi
+      ephemeralStorage: 100Mi