Merge pull request #3 from ConductionNL/feature/HP-199/leiden-theme

feature/HP-199/leiden-theme

.env

@@ -9,3 +9,6 @@ VERSION=
 NEXT_PUBLIC_API_URL=https://api.huwelijksplanner.online/api
 NEXT_PUBLIC_MATOMO_URL=https://stats.utrecht.nl/analytics/
 NEXT_PUBLIC_MATOMO_SITE_ID=5
+NEXT_PUBLIC_NL_DESIGN_THEME_CLASSNAME=utrecht-theme
+NEXT_PUBLIC_ORGANISATION_NAME=Gemeente Utrecht
+NEXT_PUBLIC_FAV_ICON=https://www.utrecht.nl/favicon.ico

.env.development

@@ -0,0 +1,3 @@
+NEXT_PUBLIC_NL_DESIGN_THEME_CLASSNAME=leiden-theme
+NEXT_PUBLIC_ORGANISATION_NAME=Gemeente Leiden
+NEXT_PUBLIC_FAV_ICON=https://gemeente.leiden.nl/typo3conf/ext/leiden_template/Resources/Public/Images/favicon/favicon-96x96.png

.env.production

@@ -0,0 +1,3 @@
+NEXT_PUBLIC_NL_DESIGN_THEME_CLASSNAME=
+NEXT_PUBLIC_ORGANISATION_NAME=
+NEXT_PUBLIC_FAV_ICON=

.github/workflows/huwelijksplanner-page-deploy.yml

@@ -0,0 +1,52 @@
+name: Deploy the Huwelijksplanner Page to GitHub Pages
+
+env: # Change these to your preferences any image url can also be a base encoded image
+  GITHUB_PAGES_BRANCH: gh-pages
+
+  NL_DESIGN_THEME_CLASSNAME: leiden-theme
+  ORGANISATION_NAME: Gemeente Leiden
+  FAV_ICON: https://gemeente.leiden.nl/typo3conf/ext/leiden_template/Resources/Public/Images/favicon/favicon-96x96.png
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Get the Huwelijksplanner Code
+        uses: actions/checkout@v2
+        with:
+          repository: ConductionNL/utrecht-huwelijksplanner
+          ref: main
+
+      # With special thanxs to https://github.com/SpicyPizza/create-envfile
+      - name: Make envfile
+        uses: SpicyPizza/[email protected]
+        with:
+          envkey_NEXT_PUBLIC_NL_DESIGN_THEME_CLASSNAME: ${{ env.NL_DESIGN_THEME_CLASSNAME }}
+          envkey_NEXT_PUBLIC_ORGANISATION_NAME: ${{ env.ORGANISATION_NAME }}
+          envkey_NEXT_PUBLIC_FAV_ICON: ${{ env.FAV_ICON }}
+          file_name: .env.production
+          fail_on_empty: true
+          sort_keys: false
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v2
+        with:
+          node-version: 18
+
+      - name: Install dependencies
+        run: npm install
+
+      - name: Build application
+        run: npm run build
+
+      - name: Deploy to GitHub Pages
+        uses: JamesIves/[email protected]
+        with:
+          branch: ${{ env.GITHUB_PAGES_BRANCH }}
+          folder: .next

helm/huwelijksplanner/Chart.yaml

@@ -22,4 +22,4 @@ version: 0.0.1
 # follow Semantic Versioning. They should reflect the version the application is using.
 appVersion: 1.0.0
 
-dependencies: []
+dependencies: []

helm/huwelijksplanner/templates/secrets.yaml

@@ -1,7 +1,6 @@
 apiVersion: v1
 kind: Secret
 metadata:
-  name: {{ include "api-platform.fullname" . }}
-  labels:
-    {{- include "api-platform.labels" . | nindent 4 }}
+  name: { { include "api-platform.fullname" . } }
+  labels: { { - include "api-platform.labels" . | nindent 4 } }
 type: Opaque

helm/huwelijksplanner/values.yaml

@@ -55,7 +55,7 @@ securityContext:
   {}
   # capabilities:
   #   drop:
-    #   - ALL
+  #   - ALL
   # readOnlyRootFilesystem: true
   # runAsNonRoot: true
 # runAsUser: 1000
@@ -69,7 +69,8 @@ ingress:
   path: ""
   pathType: ImplementationSpecific
   className: nginx
-  annotations: {}
+  annotations:
+    {}
     # kubernetes.io/ingress.class: nginx
     # kubernetes.io/tls-acme: "true"
   hosts:
@@ -78,7 +79,8 @@ ingress:
   #    hosts:
   #      - chart-example.local
 
-resources: {}
+resources:
+  {}
   # We usually recommend not to specify default resources and to leave this as a conscious
   # choice for the user. This also increases chances charts run on environments with little
   # resources, such as Minikube. If you do want to specify resources, uncomment the following