Repositories

gerngesund.de - Frontend Application

gerngesund.de Fronend incl. its Backend based on https://nuxt.com

gerngesund.de - Forms

gerngesund.de - Botpress Client

Forms Data for gerngesund.de

gerngesund.de - Vereinschampions Forms

gerngesund.de - Mail Microservice

Webserver

Stage Webserver

{{#if: | Provider: {{{Server Provider}}}
| }}{{#if: | Console: [{{{Server Admin URL}}} {{{Server Admin URL}}}]
| }}{{#if: | Server Access: {{{Server Access}}} | }}

Backend

{{#if: | {{{Backend Notes}}}
| }} {{#if: | =====URL===== {{#invoke:CSVIterator|iterateCSV| }} }}

Frontend

{{#if: | {{{Frontend Notes}}}
| }} {{#if: https://JhGQpvu2WT:XPupxU4cP9ghxsY3gZWGtxZuRP@stage.gerngesund.de/ | =====URL===== {{#invoke:CSVIterator|iterateCSV|https://JhGQpvu2WT:XPupxU4cP9ghxsY3gZWGtxZuRP@stage.gerngesund.de/ }} }}

DEV

https://dev.gerngesund.de

BasicAuth: 1Password

BasicAuth file: custadm@gfhl-aok-li378:/data/htaccess/htpasswd

Infrastruktur

Login über https://pam.aok.de/login/login mit dem User (Credentials Store) custad. Auf dem Host-System läuft mysql.

Datenbanken

backend-gerngesund
backenddev
forms-gerngesund
geo-gerngesund
logs-gerngesund
stats-gerngesund

Die Container laufen auf Podman.

Pods

bot-psql
backend-forms
directus-geo
directus-logs
backend-dev (Directus Development Backend)
zd-forms-dev
botpress
zd-forms
matomo-psl
mail-service-dev
nuxt-preview
nuxt
mail-service
ewe-nuxt-dev
backend-prod Directus Production Backend (Node.js, )
ewe-nuxt-prod

stats.gerngesund.de

Podman: matomo-psl

Update via bash script /home/custadm/matomo-update.sh

change matomo version in script (vi /home/custadm/matomo-update.sh)
run script
database update via webbrowser

gerngesund.de

Repository

{{#if: | {{{Repository Notes}}}

| }}{{#if: Parasol Island (GitLab) | Provider: Parasol Island (GitLab)
| }}{{#if: git@git.parasol-island.com:aokrf/gerngesund-de.git | URL: git@git.parasol-island.com:aokrf/gerngesund-de.git
| }} {{#if: | ====Deployment Strategy==== | }} {{#if: | {{{Deployment Strategy}}} | }}

Production Webserver

{{#if: | Provider: {{{Server Provider}}}
| }}{{#if: | Console: [{{{Server Admin URL}}} {{{Server Admin URL}}}]
| }}{{#if: | Server Access: {{{Server Access}}} | }}

Backend

{{#if: Using Directus | Using Directus
| }} {{#if: https://backend.gerngesund.de/admin | =====URL===== {{#invoke:CSVIterator|iterateCSV|https://backend.gerngesund.de/admin }} }}

Frontend

{{#if: Using nuxt.com and vuejs.org as Frontend Workframe | Using nuxt.com and vuejs.org as Frontend Workframe
| }} {{#if: https://gerngesund.de/ | =====URL===== {{#invoke:CSVIterator|iterateCSV|https://gerngesund.de/ }} }}

Production Webserver

{{#if: | Provider: {{{Server Provider}}}
| }}{{#if: | Console: [{{{Server Admin URL}}} {{{Server Admin URL}}}]
| }}{{#if: | Server Access: {{{Server Access}}} | }}

Backend

{{#if: | {{{Backend Notes}}}
| }} {{#if: https://forms-backend.gerngesund.de/admin | =====URL===== {{#invoke:CSVIterator|iterateCSV|https://forms-backend.gerngesund.de/admin }} }}

Frontend

{{#if: | {{{Frontend Notes}}}
| }} {{#if: | =====URL===== {{#invoke:CSVIterator|iterateCSV| }} }}

Preview Webserver

{{#if: | Provider: {{{Server Provider}}}
| }}{{#if: | Console: [{{{Server Admin URL}}} {{{Server Admin URL}}}]
| }}{{#if: | Server Access: {{{Server Access}}} | }}

Backend

{{#if: | {{{Backend Notes}}}
| }} {{#if: https://backend-dev.gerngesund.de/admin/login | =====URL===== {{#invoke:CSVIterator|iterateCSV|https://backend-dev.gerngesund.de/admin/login }} }}

Frontend

{{#if: Log: JhGQpvu2WT Pas: XPupxU4cP9ghxsY3gZWGtxZuRP | Log: JhGQpvu2WT Pas: XPupxU4cP9ghxsY3gZWGtxZuRP
| }} {{#if: https://dev.gerngesund.de/ | =====URL===== {{#invoke:CSVIterator|iterateCSV|https://dev.gerngesund.de/ }} }}

Deployment Workflow

The deployment process for gerngesund.de consists of the following steps:

1. Automatic Deployment to Development Environment

Any commit made to the `develop` branch is automatically deployed to the development environment accessible at https://dev.gerngesund.de.

2. Preparing a Production Deployment

To deploy changes from `develop` to the production environment:
- Create a merge request from the `develop` branch to the `main` branch.
- After merging, generate a tag for the `main` branch.
- The tag must follow the naming convention: `yyMMdd-hhmm` (e.g., `240107-1530` for January 7, 2024, at 3:30 PM).

3. Executing the Production Deployment

Once the tag is created, trigger a pipeline for that tag.
Use the environment variable `DEPLOY_ENV` to define what should be deployed:
- `PROD`: Deploys to both `https://preview.gerngesund.de` and `https://www.gerngesund.de`.
- `CONTENT`: Deploys only content updates to `https://www.gerngesund.de`.

Notes

This workflow ensures that all changes are tested in the development environment (https://dev.gerngesund.de) before being promoted to production (https://www.gerngesund.de).
The environment variable `DEPLOY_ENV` is critical for controlling deployment scope. Ensure this is configured correctly in the pipeline.