Merge pull request #171 from ConductionNL/Feature/XW-106/docker-conta…

…iner

Add helm files

helm/index.yaml

@@ -0,0 +1,14 @@
+apiVersion: v1
+entries:
+  woo-website:
+  - apiVersion: v2
+    appVersion: 1.0.0
+    created: "2023-11-14T14:22:03.775981517+01:00"
+    description: A Helm chart for the Skeleton Gatsby Application
+    digest: 49a13c2e43c2bc6dda02a40f032f70d68bb4b877b9979566ad3511071f086458
+    name: woo-website
+    type: application
+    urls:
+    - woo-website-1.0.6.tgz
+    version: 1.0.6
+generated: "2023-11-14T14:22:03.772476395+01:00"

helm/woo-website/.helmignore

@@ -0,0 +1,25 @@
+# Patterns to ignore when building packages.
+# This supports shell glob matching, relative path matching, and
+# negation (prefixed with !). Only one pattern per line.
+.DS_Store
+# Common VCS dirs
+.git/
+.gitignore
+.bzr/
+.bzrignore
+.hg/
+.hgignore
+.svn/
+# Common backup files
+*.swp
+*.bak
+*.tmp
+*.orig
+*~
+# Various IDEs
+.project
+.idea/
+*.tmproj
+.vscode/
+
+/*.tgz

helm/woo-website/Chart.yaml

@@ -0,0 +1,23 @@
+apiVersion: v2
+name: woo-website
+description: A Helm chart for the Skeleton Gatsby Application
+
+# 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.
+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: 1.0.6
+
+# 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.
+appVersion: 1.0.0

helm/woo-website/README.md

@@ -0,0 +1,29 @@
+# Deploying to a Kubernetes Cluster
+
+In order to install the application in your own cloud environment we support installation in [Kubernetes](https://kubernetes.io) using the supplied [helm](https://helm.sh) chart. Kubernetes is a Container Orchestration Engine that has been standardised for Dutch municipalities under the [Haven](https://haven.commonground.nl) standard, and for which Helm is the default installation method of components.
+
+This helm chart can be installed with the help of Kubernetes Management Tools like [Rancher](https://rancher.com).
+
+This helm chart can be installed by running Helm from your local machine (see instructions on how to install Helm on [helm.sh](https://helm.sh/docs/intro/install/#through-package-managers), which requires to have [kubectl](https://kubernetes.io/docs/tasks/tools/) installed).
+
+If you have Helm and Kubectl installed and you have configured access to your cluster (usually via a kubeconfig file) you can run the following commands to install the application.
+
+```cli
+$ helm repo add woo-website 
+$ helm install woowebsite woo-website/woo-website
+```
+
+The application can be adapted using the following helm values
+
+| Value                       | Description                                                                                                                                        | Default           |
+|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|
+| `global.domain`             | Sets the domain for the application and its dependencies.                                                                                          | `opencatalogi.nl` |
+| `global.tls`                | If the application should request TLS certificates for itself on the domains in `global.domain`, uses a cluster issuer named `letsencrypt-prod`.   | `true`            |
+
+
+For more information about the helm file for the common gateway see the [installation manual of the common gateway](https://github.com/CommonGateway/CoreBundle/blob/master/docs/features/Installation.md#haven--kubernetes).
+Keep in mind that if the common gateway is installed via the subchart of this chart, all values in the manual mentioned should be prefixed by `gateway.`.
+
+## Changelog
+
+- 0.0.1: First version based upon opencatalogi helm file

helm/woo-website/artifacthub-repo.yaml

@@ -0,0 +1,20 @@
+# Artifact Hub repository metadata file
+#
+# Some settings like the verified publisher flag or the ignored packages won't
+# be applied until the next time the repository is processed. Please keep in
+# mind that the repository won't be processed if it has not changed since the
+# last time it was processed. Depending on the repository kind, this is checked
+# in a different way. For Helm http based repositories, we consider it has
+# changed if the `index.yaml` file changes. For git based repositories, it does
+# when the hash of the last commit in the branch you set up changes. This does
+# NOT apply to ownership claim operations, which are processed immediately.
+#
+repositoryID:
+owners: # (optional, used to claim repository ownership)
+  - name: Ruben van der linde
+    email: [email protected]
+  - name: Conduction
+    email: [email protected]
+ignore: # (optional, packages that should not be indexed by Artifact Hub)
+  - name: postgresql
+  - name: redis