funman300
6905f26b56
Build and Deploy / build-and-push (push) Successful in 35s
Secrets committed in prior commits (matomo-secret.yaml, secret-analytics-auth.yaml) have been scrubbed from history via filter-branch — rotate those credentials immediately. Going forward: - deploy/*-secret.yaml is gitignored; apply manually with kubectl - deploy/matomo-secret.yaml.example shows the required shape - ArgoCD ignoreDifferences on matomo-secret prevents it pruning a manually-applied secret - Remove matomo-secret.yaml from kustomization.yaml so ArgoCD never manages it again Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
23 lines
735 B
Plaintext
23 lines
735 B
Plaintext
# DO NOT COMMIT THE REAL VERSION OF THIS FILE.
|
|
# deploy/matomo-secret.yaml is gitignored — apply it manually once:
|
|
#
|
|
# cp deploy/matomo-secret.yaml.example deploy/matomo-secret.yaml
|
|
# # edit the passwords below, then:
|
|
# kubectl apply -f deploy/matomo-secret.yaml
|
|
# kubectl annotate secret matomo-secret -n solitaire \
|
|
# argocd.argoproj.io/sync-options=Prune=false --overwrite
|
|
#
|
|
# Generate strong passwords with:
|
|
# python3 -c "import secrets; print(secrets.token_urlsafe(18))"
|
|
apiVersion: v1
|
|
kind: Secret
|
|
metadata:
|
|
name: matomo-secret
|
|
namespace: solitaire
|
|
stringData:
|
|
MYSQL_ROOT_PASSWORD: "CHANGE_ME"
|
|
MYSQL_DATABASE: matomo
|
|
MYSQL_USER: matomo
|
|
MYSQL_PASSWORD: "CHANGE_ME"
|
|
MATOMO_ADMIN_PASSWORD: "CHANGE_ME"
|