use the new base chart for oopsy

charts/oopsy/Chart.lock

@@ -0,0 +1,9 @@
+dependencies:
+- name: rails-application
+  repository: https://klausmeyer.github.io/helm-charts
+  version: 0.1.0-alpha2
+- name: redis
+  repository: https://groundhog2k.github.io/helm-charts
+  version: 0.7.10
+digest: sha256:ad881f7e6607d089740c1968f3948cf8edf4aab90b319325131ab7fca3ea50eb
+generated: "2024-04-26T16:43:21.424829808+02:00"

charts/oopsy/Chart.yaml

@@ -1,24 +1,14 @@
 apiVersion: v2
 name: oopsy
-description: Rails based error tracker
-
-# A chart can be either an 'application' or a 'library' chart.
-#
-# Application charts are a collection of templates that can be packaged into versioned archives
-# to be deployed.
-#
-# Library charts provide useful utilities or functions for the chart developer. They're included as
-# a dependency of application charts to inject those utilities and functions into the rendering
-# pipeline. Library charts do not define any templates and therefore cannot be deployed.
+description: A Helm chart for Kubernetes
 type: application
+version: "0.2.0-alpha1"
 
-# 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: 0.1.1
+dependencies:
+  - name: rails-application
+    version: "0.1.0-alpha2"
+    repository: https://klausmeyer.github.io/helm-charts
 
-# 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
-# follow Semantic Versioning. They should reflect the version the application is using.
-# It is recommended to use it with quotes.
-appVersion: "1.0.0-dev"
+  - name: redis
+    version: "0.7.10"
+    repository: https://groundhog2k.github.io/helm-charts