Server configuration written in help for argocd
  • Dockerfile 88.4%
  • Shell 11.6%
Find a file
2026-03-06 07:43:11 +01:00
apps Feat: Brought back vs code 2026-03-06 07:43:11 +01:00
argo Feat: Enabled argo metrics 2026-01-26 11:58:50 +01:00
forgejo Feat: Brought back vs code 2026-03-06 07:43:11 +01:00
forgejo-pre Feat: Cleaned history 2025-12-19 12:03:48 +01:00
kubeSystem Feat: Added router for jira 2026-02-20 12:33:28 +01:00
networking/values Feat: Removed unused tls config for traefik, since its behind a proxy 2026-02-07 11:39:48 +01:00
observability Feat: Removed otel collector from prometheus 2026-02-10 08:05:48 +01:00
sealedSecrets Feat: Cleaned history 2025-12-19 12:03:48 +01:00
wakatime Feat: Added wakatime 2026-01-21 19:46:24 +01:00
.gitignore Feat: Cleaned history 2025-12-19 12:03:48 +01:00
README.md Feat: Reconfigured runners 2025-12-20 16:30:49 +01:00

Server

This repo is a list of services, which I use. Steps to set them up:

  • Forgejo = initialize git
  • Sealed secrets

While running this app for the first time, make sure to fill gitea.admin data in values-x.yaml. Without them, no admin will be created. Once admin is created, replace values with empty strings.

This application uses sealed secrets. Apply it first. After starting sealed secrets service, encrypt secrets from forgejo-pre folder using:

kubeseal \
  --controller-namespace ${namespace} \
  --controller-name sealed-secrets \
  --format yaml \
  < secret-file.yaml \
  > output.yaml

Save outputs into proper files and apply helm again

Important

Make of copy of sealed secrets key just in case

kubectl -n ${namespace} get secret | grep sealed-secrets
kubectl -n ${namespace} get secret ${secretNameFromPreviousStep} -o yaml > key.yaml

Gitea-runners are added externally outside argo due to some issues with deployments