diff --git a/.dockerignore b/.dockerignore index e88c8ff..94cecb3 100644 --- a/.dockerignore +++ b/.dockerignore @@ -4,8 +4,8 @@ node_modules/**/* node_modules -src/static/**/* -src/static +static/**/* +static scripts/**/* scripts diff --git a/.drone.yml b/.drone.yml index 237c634..6ee51f5 100644 --- a/.drone.yml +++ b/.drone.yml @@ -1,12 +1,15 @@ +--- # ---------------------------------------------- # -- Update the helm chart # ---------------------------------------------- kind: pipeline -type: docker +type: kubernetes name: Publish the helm chart + trigger: event: - push + steps: - name: Publish the Helm chart image: alpine/helm @@ -23,43 +26,45 @@ steps: # -- Build the site and push it to the registry # ---------------------------------------------- kind: pipeline -type: docker +type: kubernetes name: Build badhouseplants.net + trigger: event: - push clone: disable: true + steps: - name: clone image: alpine/git environment: - GIT_LFS_SKIP_SMUDGE: 0 + GIT_LFS_SKIP_SMUDGE: 1 commands: - - git clone $DRONE_REMOTE_URL . - - git checkout $DRONE_BRANCH - - git submodule update --init --recursive + - git clone $DRONE_REMOTE_URL --recurse-submodules . + - git checkout $DRONE_COMMIT + - name: Test a build - image: git.badhouseplants.net/badhouseplants/hugo-container - depends_on: + image: git.badhouseplants.net/badhouseplants/hugo-builder + depends_on: - clone commands: - - hugo -s ./src + - hugo + - name: Build and push the docker image - image: git.badhouseplants.net/badhouseplants/badhouseplants-builder:9665015b44590b7ce2139f7acbad23af6628fff3 + image: git.badhouseplants.net/badhouseplants/badhouseplants-builder:80ffd53372652576fa3c36a56b351b448a025c6a privileged: true - depends_on: + depends_on: - Test a build environment: - BUILDER_COMMIT: 2449b73b13a62ae916c6703778d096e5290157b3 GITEA_TOKEN: from_secret: GITEA_TOKEN commands: - - rm -rf $DRONE_WORKSPACE/src/assets/ - ./scripts/build-container.pl + - name: Sync pictures from lfs to Minio - image: git.badhouseplants.net/badhouseplants/badhouseplants-builder:9665015b44590b7ce2139f7acbad23af6628fff3 - depends_on: + image: git.badhouseplants.net/badhouseplants/badhouseplants-builder:80ffd53372652576fa3c36a56b351b448a025c6a + depends_on: - Test a build environment: RCLONE_CONFIG_CONTENT: @@ -68,26 +73,90 @@ steps: commands: - echo "$RCLONE_CONFIG_CONTENT" > $RCLONE_CONFIG - ./scripts/upload-media.pl - - name: Deploy the application - image: git.badhouseplants.net/badhouseplants/badhouseplants-builder:9665015b44590b7ce2139f7acbad23af6628fff3 + + - name: Deploy a preview ApplicationSet + image: alpine/k8s:1.24.10 + when: + branch: + exclude: + - main depends_on: - Build and push the docker image - Sync pictures from lfs to Minio + environment: + KUBECONFIG_CONTENT: + from_secret: KUBECONFIG_CONTENT + commands: + - mkdir $HOME/.kube + - echo $KUBECONFIG_CONTENT | base64 -d > $HOME/.kube/config + - apk update --no-cache && apk add yq gettext openssl + - export ARGO_APP_CHART_VERSION=`cat chart/Chart.yaml | yq '.version'` + - export ARGO_APP_BRANCH=$DRONE_BRANCH + - export ARGO_APP_HOSTNAME="${DRONE_BRANCH}-dev.badhouseplants.net" + - export ARGO_APP_IMAGE_TAG=$DRONE_COMMIT_SHA + - export ARGO_REMARK42_SECRET=$(openssl rand -hex 12) + - kubectl get -f ./kube/applicationset.yaml -o yaml > /tmp/appset.yaml + - yq -i "del(.metadata.resourceVersion)" /tmp/appset.yaml + - yq -i "del(.metadata.generation)" /tmp/appset.yaml + - yq -i "del(.metadata.uid)" /tmp/appset.yaml + - yq -i "del(.status)" /tmp/appset.yaml + - yq -i "del(.spec.generators[].list.elements[] | select(.branch == \"$ARGO_APP_BRANCH\"))" /tmp/appset.yaml + - envsubst < ./kube/template.yaml > /tmp/elements.yaml + - yq -i '.spec.generators[].list.elements += load("/tmp/elements.yaml")' /tmp/appset.yaml + - kubectl apply -f /tmp/appset.yaml + + - name: Deploy a main ApplicationSet + image: alpine/k8s:1.24.10 + when: + branch: + - main + depends_on: + - Build and push the docker image + - Sync pictures from lfs to Minio + environment: + KUBECONFIG_CONTENT: + from_secret: KUBECONFIG_CONTENT + ARGO_GITHUB_OAUTH_KEY: + from_secret: GITHUB_OAUTH_KEY + ARGO_GOOGLE_OAUTH_KEY: + from_secret: GOOGLE_OAUTH_KEY + commands: + - mkdir $HOME/.kube + - echo $KUBECONFIG_CONTENT | base64 -d > $HOME/.kube/config + - apk update --no-cache && apk add yq gettext + - export ARGO_APP_CHART_VERSION=`cat chart/Chart.yaml | yq '.version'` + - export ARGO_APP_BRANCH=$DRONE_BRANCH + - export ARGO_APP_IMAGE_TAG=$DRONE_COMMIT_SHA + - kubectl get -f ./kube/applicationset.yaml -o yaml > /tmp/appset.yaml + - yq -i "del(.metadata.resourceVersion)" /tmp/appset.yaml + - yq -i "del(.metadata.generation)" /tmp/appset.yaml + - yq -i "del(.metadata.uid)" /tmp/appset.yaml + - yq -i "del(.status)" /tmp/appset.yaml + - yq -i "del(.spec.generators[].list.elements[] | select(.branch == \"$ARGO_APP_BRANCH\"))" /tmp/appset.yaml + - yq -i "del(.spec.generators[].list.elements[] | select(.commit_sha == \"$ARGO_APP_IMAGE_TAG\"))" /tmp/appset.yaml + - yq -i '. *= load("./kube/applicationset.yaml")' /tmp/appset.yaml + - envsubst < ./kube/main.yaml > /tmp/elements.yaml + - yq -i '.spec.generators[].list.elements += load("/tmp/elements.yaml")' /tmp/appset.yaml + - kubectl apply -f /tmp/appset.yaml + + - name: Sync application + image: argoproj/argocd + depends_on: + - Deploy a main ApplicationSet + - Deploy a preview ApplicationSet environment: ARGOCD_SERVER: from_secret: ARGOCD_SERVER ARGOCD_AUTH_TOKEN: from_secret: ARGOCD_AUTH_TOKEN - ARGO_GITHUB_OAUTH_KEY: - from_secret: GITHUB_OAUTH_KEY - ARGO_GOOGLE_OAUTH_KEY: - from_secret: GOOGLE_OAUTH_KEY commands: - - ./scripts/deploy-app.pl + - argocd app sync -l app=badhouseplants -l branch=$DRONE_BRANCH + - argocd app wait -l app=badhouseplants -l branch=$DRONE_BRANCH + - name: Cleanup everything - image: git.badhouseplants.net/badhouseplants/badhouseplants-builder:9665015b44590b7ce2139f7acbad23af6628fff3 + image: rclone/rclone:latest depends_on: - - Deploy the application + - Sync application environment: RCLONE_CONFIG_CONTENT: from_secret: RCLONE_CONFIG_CONTENT_PRIVATE @@ -100,26 +169,44 @@ steps: from_secret: ARGOCD_AUTH_TOKEN commands: - echo "$RCLONE_CONFIG_CONTENT" > $RCLONE_CONFIG + - apk update + - apk add curl jq perl git yq + - curl -sSL -o argocd-linux-amd64 https://github.com/argoproj/argo-cd/releases/latest/download/argocd-linux-amd64 + - install -m 555 argocd-linux-amd64 /usr/local/bin/argocd + - rm argocd-linux-amd64 - ./scripts/cleanup.pl + --- +# ---------------------------------------------- +# -- Upload a newer version of my CV +# ---------------------------------------------- kind: pipeline -type: docker -name: Spell-Checker +type: kubernetes +name: CV Builder + trigger: + branch: + - main event: - - push -clone: - disable: true + - push + steps: - - name: clone - image: alpine/git + - name: Build the CV + image: ghcr.io/puppeteer/puppeteer + commands: + - cp -R ./content/cv/* $HOME + - cd $HOME + - npm install md-to-pdf + - npx md-to-pdf index.md + - mkdir $DRONE_WORKSPACE/cv + - mv index.pdf $DRONE_WORKSPACE/cv/n.rodionov.pdf + + - name: Upload the CV + image: rclone/rclone:latest environment: - GIT_LFS_SKIP_SMUDGE: 1 + RCLONE_CONFIG_CONTENT: + from_secret: RCLONE_CONFIG_CONTENT_PRIVATE + RCLONE_CONFIG: /tmp/rclone.conf commands: - - git clone $DRONE_REMOTE_URL --recurse-submodules . - - git checkout $DRONE_BRANCH - - name: Spell-Checker - image: node - commands: - - npm i markdown-spellcheck -g - - mdspell "src/content/**/*.md" -n -r + - echo "$RCLONE_CONFIG_CONTENT" > $RCLONE_CONFIG + - rclone copy -P $DRONE_WORKSPACE/cv badhouseplants-minio:/public-download diff --git a/.gitattributes b/.gitattributes index c2b8e77..3097b99 100644 --- a/.gitattributes +++ b/.gitattributes @@ -1,2 +1,2 @@ -src/static/** filter=lfs diff=lfs merge=lfs -text -src/static/**/* filter=lfs diff=lfs merge=lfs -text +static/** filter=lfs diff=lfs merge=lfs -text +static/**/* filter=lfs diff=lfs merge=lfs -text diff --git a/.gitignore b/.gitignore index de40ffb..436acc7 100644 --- a/.gitignore +++ b/.gitignore @@ -1,4 +1,5 @@ -src/node_modules -src/public -src/resources -.hugo_build.lock +node_modules +#static +content/cv/index.pdf +public +resources diff --git a/.gitmodules b/.gitmodules index 6c34b41..311fa4c 100644 --- a/.gitmodules +++ b/.gitmodules @@ -1,3 +1,3 @@ -[submodule "src/themes/stack"] - path = src/themes/stack - url = https://github.com/CaiJimmy/hugo-theme-stack.git +[submodule "themes/papermod"] + path = themes/papermod + url = https://github.com/adityatelange/hugo-PaperMod.git diff --git a/src/content/music/_index.md b/.hugo_build.lock similarity index 100% rename from src/content/music/_index.md rename to .hugo_build.lock diff --git a/.spelling b/.spelling deleted file mode 100644 index 6cb1d43..0000000 --- a/.spelling +++ /dev/null @@ -1,161 +0,0 @@ -# markdown-spellcheck spelling configuration file -# Format - lines beginning # are comments -# global dictionary is at the start, file overrides afterwards -# one word per line, to define a file override use ' - filename' -# where filename is relative to this configuration file -WIP -envs -anymore -hostname -hostnames -Dockerfile -helmfile -k8s -env -dir -dev'n'stages -oi -minio -ArgoCD -setups -SRE -autoscaler -gitea -vendoring -cli -vpa -ok -cmp -config -GitOps -argo -argocding -cluster-1 -cluster-2 -cluster-3 -kubernetes -argocd -helmfiles -plugin -helmfile.yaml -cleanup -serie -backend -js -frontend -ShowToc -cover.png -allanger -DIY -DevOps -funkwhale -PSY -bandcamp -soundcloud -spotify -deezer -prog-rock -oveleane -IDM -gitlab -bitwarden -elasticsearch -grafana -lifecycle -auditable -the-first-production-grafaba -grafana -applicationsets -helm-releases-v2 -yaml -CR -minecraft -github -ddosed -VST -Xfer -plugins -yabridgectl -yabridge -DAW -polyverse -camelcrusher -standalone -url -glitchmachines -MacBook -configs -behaviour -FreqEcho -DSP -Supermassive -Ableton -Softube -center -iZotope -V2 -auth -README.md -TAL-Chorus-LX -badhouseplants -Deelay -Gatelab -Filterstep -Panflow -PaulXStretch -Audiomodern -Kushview -JUCE -Melda -MDrummer -GBs -laggy -MDrumReplacer -MPowerSynth -MGuitarArchitect -u-he -TyrellN6 -Tyrell -install.sh -MGuitarArchitect -Amazona.de. -Bitwig -ProjectSAM -Pendulate -Protoverb -Eurorack -S3 -XT -Ruina -VCV -LFO -beatmaker -wavetables -OSC -YOUTUBE -Twelve50TV -Robotik -McRoy -brah -aw -shite -lowrider -mdma -nah -clubby -MGK -params - - src/themes/papermod/README.md -PaperMod -hugo-paper -og -ExampleSite -exampleSite -pipelining -Fuse.js -webpack -nodejs -Pagespeed -Highlight.js -2023-02-25T14 -argocd-dynamic-environment-per-branch-part-1 diff --git a/.woodpecker.yml b/.woodpecker.yml deleted file mode 100644 index 3189887..0000000 --- a/.woodpecker.yml +++ /dev/null @@ -1,93 +0,0 @@ ---- -when: - event: - - push - -steps: - - image: alpine/helm - name: Publish the Helm chart - commands: - - helm plugin install https://github.com/chartmuseum/helm-push - - helm package chart -d chart-package - - helm repo add --username allanger --password $GITEA_TOKEN badhouseplants-net https://git.badhouseplants.net/api/packages/badhouseplants/helm - - helm cm-push "./chart-package/$(ls chart-package)" badhouseplants-net - secrets: - - gitea_token - - - name: Test a build - image: git.badhouseplants.net/badhouseplants/hugo-container - commands: - - hugo -s ./src - - - name: Build and push the docker image - image: git.badhouseplants.net/badhouseplants/badhouseplants-builder:latest - privileged: true - depends_on: - - Test a build - secrets: - - gitea_token - environment: - BUILDER_COMMIT: 2449b73b13a62ae916c6703778d096e5290157b3 - commands: - - rm -rf $DRONE_WORKSPACE/src/assets/ - - ./scripts/build-container.pl - backend_options: - kubernetes: - resources: - requests: - memory: 500Mi - cpu: 200m - limits: - memory: 1000Mi - cpu: 1000m - securityContext: - privileged: true - - - name: Sync pictures from lfs to Minio - image: git.badhouseplants.net/badhouseplants/badhouseplants-builder:latest - depends_on: - - Test a build - secrets: - - rclone_config_content - environment: - RCLONE_CONFIG: /tmp/rclone.conf - commands: - - echo "$RCLONE_CONFIG_CONTENT" > $RCLONE_CONFIG - - ./scripts/upload-media.pl - - - name: Deploy the application - image: git.badhouseplants.net/badhouseplants/badhouseplants-builder:latest - depends_on: - - Build and push the docker image - - Sync pictures from lfs to Minio - secrets: - - gitea_token - - argocd_auth_token - - argo_github_oauth_key - - argo_google_oauth_key - environment: - ARGOCD_SERVER: https://argo.badhouseplants.net:443 - commands: - - ./scripts/deploy-app.pl - - - name: Cleanup everything - image: git.badhouseplants.net/badhouseplants/badhouseplants-builder:latest - depends_on: - - Deploy the application - secrets: - - gitea_token - - argocd_auth_token - - rclone_config_content - environment: - ARGOCD_SERVER: argo.badhouseplants.net:443 - RCLONE_CONFIG: /tmp/rclone.conf - commands: - - echo "$RCLONE_CONFIG_CONTENT" > $RCLONE_CONFIG - - ./scripts/cleanup.pl - - - name: Spell-Checker - failure: ignore - image: node - commands: - - npm i markdown-spellcheck -g - - mdspell "src/content/**/*.md" -n -r diff --git a/Containerfile b/Containerfile deleted file mode 100644 index 9979a54..0000000 --- a/Containerfile +++ /dev/null @@ -1,4 +0,0 @@ -FROM git.badhouseplants.net/badhouseplants/hugo-container:43fd807fea2238853f48f95a435081d88857bb79 -WORKDIR /src -COPY ./src /src -ENTRYPOINT ["hugo"] diff --git a/Dockerfile b/Dockerfile new file mode 100644 index 0000000..388a6cd --- /dev/null +++ b/Dockerfile @@ -0,0 +1,4 @@ +FROM git.badhouseplants.net/badhouseplants/hugo-builder +WORKDIR /src +COPY . /src +ENTRYPOINT ["hugo"] diff --git a/README.md b/README.md index 7ca4a73..b10608b 100644 --- a/README.md +++ b/README.md @@ -1,8 +1,4 @@ # Badhouseplants NET -## About -- To be done ## Static content Storing static content in the repo is painful, because there are massive. That's why for storing them I'm using a S3 bucket that is publicly available for downstream operations - - diff --git a/archetypes/default.md b/archetypes/default.md new file mode 100644 index 0000000..d669718 --- /dev/null +++ b/archetypes/default.md @@ -0,0 +1,12 @@ +--- +title: "{{ replace .Name "-" " " | title }}" +date: {{ .Date }} +draft: true +ShowToc: true +cover: + image: "cover.png" + caption: "{{ replace .Name "-" " " | title }}" + relative: false + responsiveImages: false +--- + diff --git a/chart/Chart.yaml b/chart/Chart.yaml index 96d4f43..409a1d4 100644 --- a/chart/Chart.yaml +++ b/chart/Chart.yaml @@ -2,10 +2,11 @@ apiVersion: v2 name: badhouseplants-net description: A Helm chart for Kubernetes type: application -version: 0.9.0 +version: 0.6.0 appVersion: "4.20.0" dependencies: - name: remark42 - version: 0.7.0 + version: 0.5.5 repository: https://groundhog2k.github.io/helm-charts/ condition: remark42.enabled + diff --git a/chart/templates/deployment.yaml b/chart/templates/deployment.yaml index 7b0ee77..cdafb77 100644 --- a/chart/templates/deployment.yaml +++ b/chart/templates/deployment.yaml @@ -60,7 +60,7 @@ spec: volumeMounts: - name: {{ .Values.volumes.rclone.name }} mountPath: /src/static - readOnly: false + readOnly: true - name: {{ .Values.volumes.public.name }} mountPath: /src/public readOnly: false @@ -88,7 +88,7 @@ spec: volumes: - name: rclone-config secret: - secretName: rclone-config-{{ .Release.Name }} + secretName: rclone-config - name: {{ .Values.volumes.rclone.name }} emptyDir: sizeLimit: {{ .Values.volumes.rclone.sizeLimit }} @@ -97,5 +97,5 @@ spec: sizeLimit: {{ .Values.volumes.public.sizeLimit }} - name: nginx-config configMap: - name: nginx-config-{{ .Release.Name }} + name: nginx-config diff --git a/chart/templates/namespace.yaml b/chart/templates/namespace.yaml new file mode 100644 index 0000000..a16fa00 --- /dev/null +++ b/chart/templates/namespace.yaml @@ -0,0 +1,16 @@ +{{- if .Values.istio.enabled -}} +apiVersion: v1 +kind: Namespace +metadata: + name: {{ .Values.namespace.name }} + labels: + {{- include "badhouseplants-net.labels" . | nindent 4 }} + {{- range $key, $value := .Values.namespace.labels}} + {{ $key }}: {{ $value }} + {{- end }} + {{- with .Values.namespace.annotations }} + annotations: + {{- toYaml . | nindent 4 }} + {{- end }} + +{{- end }} \ No newline at end of file diff --git a/chart/templates/nginx-config-cm.yaml b/chart/templates/nginx-config-cm.yaml index bcaab33..e8e1d38 100644 --- a/chart/templates/nginx-config-cm.yaml +++ b/chart/templates/nginx-config-cm.yaml @@ -1,7 +1,7 @@ apiVersion: v1 kind: ConfigMap metadata: - name: nginx-config-{{ .Release.Name }} + name: nginx-config labels: {{- include "badhouseplants-net.labels" . | nindent 4 }} data: diff --git a/chart/templates/rclone-config-sec.yaml b/chart/templates/rclone-config-sec.yaml index bd529a7..8e20719 100644 --- a/chart/templates/rclone-config-sec.yaml +++ b/chart/templates/rclone-config-sec.yaml @@ -1,7 +1,7 @@ apiVersion: v1 kind: Secret metadata: - name: rclone-config-{{ .Release.Name }} + name: rclone-config labels: {{- include "badhouseplants-net.labels" . | nindent 4 }} type: generic diff --git a/chart/templates/virtual-service.yaml b/chart/templates/virtual-service.yaml new file mode 100644 index 0000000..0db7593 --- /dev/null +++ b/chart/templates/virtual-service.yaml @@ -0,0 +1,57 @@ +{{- if .Values.istio.enabled -}} +apiVersion: networking.istio.io/v1beta1 +kind: VirtualService +metadata: + name: {{ include "badhouseplants-net.fullname" . }} + labels: + {{- include "badhouseplants-net.labels" . | nindent 4 }} + {{- with .Values.istio.annotations }} + annotations: + {{- toYaml . | nindent 4 }} + {{- end }} +spec: + gateways: + - istio-system/badhouseplants-net + hosts: + {{- range .Values.istio.hosts}} + - {{ . }} + {{- end }} + http: + - match: + - uri: + prefix: {{ .Values.istio.prefix }} + route: + - destination: + host: {{ include "badhouseplants-net.fullname" . }} + port: + number: {{ .Values.service.port }} +{{- end }} +--- +{{- if .Values.remark42.istio.enabled -}} +apiVersion: networking.istio.io/v1beta1 +kind: VirtualService +metadata: + name: {{ include "remark42.fullname" . }}-remark42 + labels: + {{- include "badhouseplants-net.labels" . | nindent 4 }} + {{- with .Values.remark42.istio.annotations }} + annotations: + {{- toYaml . | nindent 4 }} + {{- end }} +spec: + gateways: + - istio-system/badhouseplants-net + hosts: + {{- range .Values.remark42.istio.hosts}} + - {{ . }} + {{- end }} + http: + - match: + - uri: + prefix: {{ .Values.remark42.istio.prefix }} + route: + - destination: + host: {{ .Release.Name }}-remark42 + port: + number: {{ .Values.remark42.service.port }} +{{- end }} diff --git a/chart/values.yaml b/chart/values.yaml index c0463a3..dadc637 100644 --- a/chart/values.yaml +++ b/chart/values.yaml @@ -1,5 +1,12 @@ replicaCount: 1 +namespace: + annotations: {} + labels: + istio-injection: enabled + enabled: true + name: badhouseplants-application + nginx: container: name: nginx @@ -30,7 +37,7 @@ hugo: container: name: badhouseplants-net resources: {} - image: + image: repository: git.badhouseplants.net/badhouseplants/badhouseplants-net pullPolicy: Always tag: latest @@ -39,19 +46,27 @@ hugo: env: HUGO_PARAMS_GITBRANCH: main +istio: + annotations: {} + enabled: true + hosts: + - badhouseplants.net + - www.badhouseplants.net + prefix: / + volumes: # ---------------------------------------------- - # -- An emptydir volume where hugo should + # -- An emptydir volume where hugo should # -- put the static content # ---------------------------------------------- public: name: public-content - sizeLimit: 1Gi + sizeLimit: 1Gi # ---------------------------------------------- - # -- An emptydir volume where rclone should + # -- An emptydir volume where rclone should # -- download pictures # ---------------------------------------------- - rclone: + rclone: name: s3-data sizeLimit: 1Gi diff --git a/config.yaml b/config.yaml new file mode 100644 index 0000000..c0abc4c --- /dev/null +++ b/config.yaml @@ -0,0 +1,71 @@ +--- +languageCode: 'en-us' +title: 'Bad Houseplants' +theme: 'papermod' +menu: + main: + - name: Posts + url: /posts + weight: 10 + - name: Music + url: /music + weight: 11 + - name: Beats + url: /beats + weight: 12 + - name: About + url: /about + weight: 13 + - name: Search + url: /search + weight: 14 +taxonomies: + tag: tags +params: + GitBranch: main + Remark42ID: remark + Remark42URL: https://remark42.badhouseplants.net + ShowBreadCrumbs: true + ShowReadingTime: true + ShowPostNavLinks: true + ShowCodeCopyButtons: true + comments: true + profileMode: + enabled: true + title: "Bad Houseplants" + subtitle: "... by allanger" + imageUrl: "main-logo.png" + imageWidth: 150 + imageHeight: 150 + buttons: + - name: Source + url: "https://git.badhouseplants.net/badhouseplants/badhouseplants-net" + - name: My Music + url: "https://funkwhale.badhouseplants.net/library/artists" + socialIcons: + - name: "telegram" + url: "https://t.me/allanger" + - name: "twitter" + url: "https://twitter.com/_allanger" + - name: "mastodon" + url: "https://mastodon.social/@allanger" + - name: github + url: 'https://github.com/allanger' + - name: instagram + url: "https://instagram.com/_allanger" + - name: email + url: 'mailto:allanger@badhouseplants.net' + ShowShareButtons: true + ShareButtons: ["telegram", "twitter", "reddit", "linkedin"] + env: production + title: Bad Houseplants + description: "...by allanger" + keywords: [Blog, Portfolio] + author: allanger + DateFormat: "January 2, 2006" + defaultTheme: auto +outputs: + home: + - HTML + - RSS + - JSON diff --git a/content/about/_index.md b/content/about/_index.md new file mode 100644 index 0000000..97c9ac6 --- /dev/null +++ b/content/about/_index.md @@ -0,0 +1,27 @@ +--- +title: About +date: 2023-01-24T09:26:52+01:00 +draft: false +--- + + +It was supposed to be just yet another web page with musical releases reviews, but after trying to write something like that, I've found out that I'm not good at it. So I've decided to start a blog where I can write anything that comes to my mind. + + + + +> The last build is [![Build Status](https://drone.badhouseplants.net/api/badges/badhouseplants/badhouseplants-net/status.svg?ref=refs/heads/{{< param GitBranch >}})](https://drone.badhouseplants.net/badhouseplants/badhouseplants-net) + +### What is Bad Houseplants? + +> **allanger** +> +> *Actually, I'm not sure yet. I wanted it to be something about music, but I found out that musical industry is not very welcoming, and I don't know what exactly I > can do there. Creating music is somehow an intimate process to me, so I can't share a lot about it. The whole distributing thing is a black-box, and I wouldn't like to be a part of it, until anything is changed. I wanted to do musical reviews, but there are tons of guys who already do it a way better than I can. So I've given up on music here. I still hope that one day I'll open a recording studio under this name, but I'm not sure when it's even going to be possible. The second thing that I can talk about is IT. I think it can be interesting, but I don't want to kind of stigmatized as an IT blogger. And then I've decided that I would like to write something about indie culture, about DIY philosophy and all this punk related stuff. So let's say that is a blog about indie* + +### Wanna join? + +If you want to publish anything here, I don't mind. But for doing that you need to have at least basic `git` knowledge because this blog is written as code. You can check the [source code](https://git.badhouseplants.net/badhouseplants/badhouseplants-net) to understand if you're ready or not. I'm hosting my own `Gitea` instance, so you will have to request an account ([just email me](mailto:allanger@zohomail.com) or find me on [telegram](https://t.me/allanger)), when you got one, you're ready to start writing. If you have any questions about how to start, I'm always open for a conversation. + +Thanks, + +Oi! diff --git a/content/authors/allanger/_index.md b/content/authors/allanger/_index.md new file mode 100644 index 0000000..33377bf --- /dev/null +++ b/content/authors/allanger/_index.md @@ -0,0 +1,34 @@ +> If you're hiring, you can find [my CV here]({{< ref "cv" >}} ) + +I'm a musician and a geek, who works full time as a DevOps engineer, whatever it means. Thanks to my job, I know how to run self-hosted services pretty well, and that's helping me achieve my goal of bringing the indie culture everywhere I can. I'm trying to separate myself from global companies as a user as much as it's possible in my daily life. + +Also, I'm a Linux lover, what doesn't really correlate with my will to make music. I hope that one day we will see that developers will see that Linux is a real OS that can be used as a daily driver. And building software for Linux is important just like building for MacOS and Windows. I hope that we will be able to use not only open source solutions working on Linux, but also closed-source proprietary ones. + +### Music, Beats and Arrangements + +## Music + +> I always thought I was a musician +[Check out what I've got](https://funkwhale.badhouseplants.net) + +You can find everything I consider ready enough to be shown on my [FunkWhale](https://funkwhale.badhouseplants.net/library) instance. Also, my music can be found on many streaming services, and yes, I know that it's not a very independent way of doing things, but it's one of many exceptions 🙃. + +All of my beats are waiting for somebody to do something with them. I'm giving them all for donation, so if you happen to like any, just shoot me a message. I can re-arrange and remix them as much as possible. I can mix your tracks, and I really will to do that, it doesn't matter what kind of music it is, I'm ready to work with everything, if I like it *(at least a little bit)*. + +## IT + +> I'm a DevOps after all +[Visit my gitea](https://git.badhouseplants.net) +For I'm a DevOps I'm working a lot with Kubernetes, Containers, Linux, etc. And that's the root of my intention to move to Linux completely. + +I hope I will do my contribution to the world of Linux music production too. I'm hosting my own Gitea instance. There you will be able to find all my code (or almost all of my code). + +If you made it to here, you might think that it's the point of all of this existing. Self-hosted blog, a music streaming service, and git. **This guy is just a fucking geek! ** + +And yes, you're partially right. The main reason it exists is that I'm trying to follow and promote `indie/punk` culture, that is not only applies to arts. And that's going to be covered in my posts, I hope. + +--- + +### If you're still here, + +I'm looking for people with the same mindset as me, to make music or to code together, or anything. So I would be happy to get connections on [Mastodon](https://mastodon.social/@allanger) diff --git a/content/beats/_index.md b/content/beats/_index.md new file mode 100644 index 0000000..6c6b683 --- /dev/null +++ b/content/beats/_index.md @@ -0,0 +1,88 @@ +--- +title: Beats +date: 2023-01-24T09:26:52+01:00 +draft: false +--- +>I don't lease my beats. If you happen to like anything, just shout me a message and we will come to an agreement. And if you decide to use any of my beats you'll be the only one using it (legally). + +--- +### Easy Money +{{< rawhtml >}} + +{{< /rawhtml >}} + +### Monk +{{< rawhtml >}} + +{{< /rawhtml >}} + +### Phantom Limb +{{< rawhtml >}} + +{{< /rawhtml >}} + +### Ark +{{< rawhtml >}} + +{{< /rawhtml >}} + +### Silk Road +{{< rawhtml >}} + +{{< /rawhtml >}} + +### Tremor +{{< rawhtml >}} + +{{< /rawhtml >}} + +### Silver Grenade +{{< rawhtml >}} + +{{< /rawhtml >}} + +### Spinal Cord +{{< rawhtml >}} + +{{< /rawhtml >}} + +### Empty Cubicles +{{< rawhtml >}} + +{{< /rawhtml >}} + +### Petrol +{{< rawhtml >}} + +{{< /rawhtml >}} + +### PSY +{{< rawhtml >}} + +{{< /rawhtml >}} + +### Vicious Shine +{{< rawhtml >}} + +{{< /rawhtml >}} + +### Body Drop +{{< rawhtml >}} + +{{< /rawhtml >}} + +### Broken Piano +{{< rawhtml >}} + +{{< /rawhtml >}} + +### Dead Wings +{{< rawhtml >}} + +{{< /rawhtml >}} + +### Trapped +{{< rawhtml >}} + +{{< /rawhtml >}} + diff --git a/content/cv/index.md b/content/cv/index.md new file mode 100644 index 0000000..8569c60 --- /dev/null +++ b/content/cv/index.md @@ -0,0 +1,108 @@ +--- +title: "Curriculum Vitae (CV)" +date: 2023-02-11T18:29:00+01:00 +draft: false +ShowToc: true +--- +# Nikolai Rodionov + +``` +> Location: Düsseldorf, Germany +> Email: allanger@zohomail.com (preffered) +> Phone: 015223284008 +> Github: https://github.com/allanger +``` + +--- + +## About me +

+drawing +

+ +I'm a DevOps engineer (or SRE if you wish) with 5++ years of hands-on experience with a decent amount of tools that are most probably used or going to be used in your company. One of the most important tools that I love working with and want to continue working with, is Kubernetes. At least, while I don't see any better alternative to it. I think that containers themselves are one of coolest inventions in development, and I'm trying to use them as long as it's possible. Also, I believe that every routine must be automated, because routing is a boring job that lets people lose focus and make mistakes. + +I think that there are several things that a good SRE or DevOps engineer must be able to do: +- To build reliable and stable infrastructure +- Keep this infrastructure up-to-date +- Keep all the source and instructions of this infrastructure clean and simple +- Avoid a human factor as long as possible +- And when it's not possible to avoid it, not to be afraid to take responsibility + +Also, I think it's important that before implementing anything, an engineer has understood all the requirements and checked tools that can fulfil them. I often see, how people try to use a tool for its name but not for its functionality, and hence they have to do a lot of additional work and deal with compromises. And if nothing really can fulfil those requirements, you need not be afraid of writing something new *and open-source it*. + +
+ +## Experience + +**Grandcentrix**: SRE +> 02.2023 - until now + +``` +| Microsoft Azure +| Containers - Kubernetes - Helm - Kustomize +| PostgreSQL +| Bash - Python +| Prometheus - Grafana - Loki +| ArgoCD - Github Actions +| Sops +| Terraform +``` + +**Klöckner-i**: DevOps Engineer +> 01.2022 - 01.2023 + +``` +| GCloud - Microsoft Azure +| Linux - Containers - Kubernetes - Helm - Helmfile +| Percona Mysql - Postgresql +| Bash +| Prometheus - Grafana - Elasticsearch - Kibana +| ArgoCD - Gitlab CI - Github Actions +| Sops +| Ansible +``` +--- + +**Itigris**: DevOps Engineer +> 07.2019 - 12.2021 + +``` +| AWS - Yandex Cloud +| Linux - Containers - Kubernetes - Helm - Helmfile - Kustomize +| Bash +| Gitlab CI - Drone - ArgoCD +| Postgresql - Redis +| Java - JS - Go +| Ansible - Terraform +| Prometheus - Grafana - Loki - Elasticsearch - Kibana +``` +--- + +**Etersoft**: DevOps Engineer +> 03.2017 - 06.2019 + +``` +| Bare metal - Proxmox - Virtual Box +| Linux - Containers - Networks +| Bash - Perl +| Mysql - Postgresql +| Minio - Ceph +| Gitlab CI +| Ansible +``` + + +## A little bit more about me + +- I love to work with `Kubernetes`, but not with `yaml`. +- I'm a huge fan of [Helmfile](https://github.com/helmfile/helmfile). +- I have written several small cli tools in Rust, that you might find in my [GitHub profile pins](https://github.com/allanger) (they are not perfect, but I'm working on it). +- I'm contributing to [db-operator](https://github.com/kloeckner-i/db-operator). +- I'm trying to automate everything until I'm losing control over something that is automated. +- I love Perl, although I don't even remember how to write code with it, but I would be somehow thrilled to have any ability to work with it in production +- I also think that everything is better in Rust, or at least in Go *(if Bash is not enough)* + +I have a blog (written-as-code) that is deployed to K8s (https://badhouseplants.net/), with the source code stored in a self-hosted Gitea, that is also deployed to K8s alongside the CI/CD system where this blog is being built and published. This CV is also being built as a part of the CI process, and then uploaded to `minio` storage that is also ~~surprisingly~~ running in this cluster. So you can download the latest version of CV here: + +> But I can't guarantee 100% availability because it's a one-node k8s, and sometimes I need to do a maintenance work diff --git a/content/cv/myself.jpeg b/content/cv/myself.jpeg new file mode 100644 index 0000000..25fb28d Binary files /dev/null and b/content/cv/myself.jpeg differ diff --git a/content/music/index.md b/content/music/index.md new file mode 100644 index 0000000..1dbc05c --- /dev/null +++ b/content/music/index.md @@ -0,0 +1,95 @@ +--- +title: "Music" +date: 2023-01-31T13:52:43+01:00 +draft: false +ShowToc: true + +--- +Everything that's created by me, can be found on my [funkwhale instance](https://funkwhale.badhouseplants.net). But I'm only uploading `lossy` there. I was trying to upload losseless, but then it either doesn't really work with my Android App, or it's hard to manage. And it needs a way more disk that way. So if you want to listnen to lossless, go to my [Bandcamp](https://allanger.bandcamp.com/). *A lot of tracks are still not there, but they will be there soon*. I also have a [SoundCloud account](https://soundcloud.com/allanger) and I try to publish everything there. + + +--- + +### allanger + +[Spotify](https://open.spotify.com/artist/1VPAs75xrhaXhCIIHsgF02) - [Apple Music](https://music.apple.com/us/artist/allanger/1617855325) - [Deezer](https://www.deezer.com/us/artist/117780712) - [SoundCloud](https://soundcloud.com/allanger) - [Bandcamp](https://allanger.bandcamp.com/) - [Funkwhale](https://funkwhale.badhouseplants.net/library/artists/3/) + + +#### Out of Law +>![Cover](/music/allanger-Out_of_Law.png) +>Release Date: 2022-06-08 +> +>Genre: Alternative +> +>Sub Genre: Punk + +[Spotify](spotify:album:4RACKNtJqPXZOB6UsmwxKp) - [Apple Music](https://music.apple.com/us/album/1625562031) - [Deezer](https://www.deezer.com/us/album/321014447) - [SoundCloud](https://soundcloud.com/allanger/out-of-law) - [Bandcamp](https://allanger.bandcamp.com/album/out-of-law) - [Funkwhale](https://funkwhale.badhouseplants.net/library/albums/5/) + +{{< rawhtml >}} + +{{< /rawhtml >}} + +#### Wasted Time +>![Cover](/music/allanger-Waster_Time.png) +>Release Date: 2022-05-17 +> +>Genre: Punk/Rock +> +>Sub Genre: Prog-Rock/Art Rock + +[Spotify](spotify:album:2zOW72GHTTKIZAbwjmxili) - [Apple Music](https://music.apple.com/us/album/1617855666) - [Deezer](https://www.deezer.com/us/album/308544627) - [SoundCloud](https://soundcloud.com/allanger/wasted-time?si=59896836701c48b6a07f7af96043faaf&utm_source=clipboard&utm_medium=text&utm_campaign=social_sharing) - [Bandcamp](https://allanger.bandcamp.com/album/wasted-time) - [Funkwhale](https://funkwhale.badhouseplants.net/library/albums/4/) + +{{< rawhtml >}} + +{{< /rawhtml >}} + +#### Let Me Kill +> In this song, I'm using samples from a YouTube video and so I'm not sure that I can distribute on all platforms. That's why it exists only on SoundCloud, Funkwhale, and Bandcamp +>![Cover](/music/allanger-Let_Me_Kill.png) +>Release Date: 2021-10-15 +> +>Genre: Trap + +[SoundCloud](https://soundcloud.com/allanger/let-me-kill) - [Bandcamp](https://allanger.bandcamp.com/track/let-me-kill) - [Funkwhale](https://funkwhale.badhouseplants.net/library/albums/7/) + +{{< rawhtml >}} + +{{< /rawhtml >}} + +#### Anymore +> In this song, I'm using samples from a YouTube video and so I'm not sure that I can distribute on all platforms. That's why it exists only on SoundCloud and Funkwhale +>![Cover](/music/allanger-Anymore.jpg) +>Release Date: 2018-12-26 +> +>Genre: Indie +> +>Sub Genre: Lo-Fi Indie + + +[SoundCloud](https://soundcloud.com/allanger/anymore) - [Funkwhale](https://funkwhale.badhouseplants.net/library/albums/11/) +{{< rawhtml >}} + +{{< /rawhtml >}} + +### Oveleane + +> It's another project made by me, I just thought that that electronic stuff won't fit well in the allanger's profile, and so decided to separate them. But it's still allanger, you know... + +[Spotify](https://open.spotify.com/artist/2PKE1XvwP82LCacM5q6rCx?si=hJyJWcEgR4mZLkjbCso45A) - [Apple Music](https://music.apple.com/us/artist/oveleane/1654951021) - [Deezer](https://www.deezer.com/us/artist/190392997) + + +#### Four Steps Behind +>![Cover](/music/Oveleane%20-%20Four%20Steps%20Behind.jpg) +>Release Date: 2022-12-05 +> +>Genre: Electronic +> +>Sub Genre: IDM/Experimental + +[Spotify](https://open.spotify.com/album/1RjB1xLoD2JXmWuBjGegCN?si=fIsGrOfoQRaeKu9f-Oh0dw) - [Apple Music](https://music.apple.com/us/album/1654953305) - [Deezer](https://www.deezer.com/us/album/377293977) - [Funkwhale](https://funkwhale.badhouseplants.net/library/albums/1/) + +{{< rawhtml >}} + +{{< /rawhtml >}} + + diff --git a/content/posts/_index.md b/content/posts/_index.md new file mode 100644 index 0000000..e69de29 diff --git a/content/posts/argocd-dynamic-environment-per-branch-part-1/cover.png b/content/posts/argocd-dynamic-environment-per-branch-part-1/cover.png new file mode 100644 index 0000000..1b5c9b8 Binary files /dev/null and b/content/posts/argocd-dynamic-environment-per-branch-part-1/cover.png differ diff --git a/src/content/post/allanger/argocd-dynamic-environment-per-branch-part-1.md b/content/posts/argocd-dynamic-environment-per-branch-part-1/index.md similarity index 97% rename from src/content/post/allanger/argocd-dynamic-environment-per-branch-part-1.md rename to content/posts/argocd-dynamic-environment-per-branch-part-1/index.md index 93040ea..6de653b 100644 --- a/src/content/post/allanger/argocd-dynamic-environment-per-branch-part-1.md +++ b/content/posts/argocd-dynamic-environment-per-branch-part-1/index.md @@ -1,22 +1,23 @@ -+++ -title = "Dynamic Environment Per Branch with ArgoCD" -date = 2023-02-25T14:00:00+01:00 -image = "/posts/argocd-dynamic-environment-per-branch-part-1/cover.png" -draft = false -categories = [ - "Kubernetes", - "CI-CD" -] -+++ +--- +title: "Dynamic Environment Per Branch with ArgoCD" +date: 2023-02-25T14:00:00+01:00 +draft: false +ShowToc: true +cover: + image: "cover.png" + caption: "Dynamic Environment Per Branch with ArgoCD" + relative: false + responsiveImages: false +--- [Do you remember?]({{< ref "dont-use-argocd-for-infrastructure" >}}) > And using `helmfile`, I will install `ArgoCD` to my clusters, of course, because it's an awesome tool, without any doubts. But don't manage your infrastructure with it, because it's a part of your infrastructure, and it's a service that you provide to other teams. And I'll talk about in one of the next posts. -Yes, I have written 4 posts where I was almost absolutely negative about `ArgoCD`. But I was talking about infrastructure then. I've got some ideas about how to describe it in a better way, but I think I will write another post about it. +Yes, I have written 4 posts where I was almost absuletely negative about `ArgoCD`. But I was talking about infrastructure then. I've got some ideas about how to describe it in a better way, but I think I will write another post about it. Here, I want to talk about dynamic *(preview)* environments, and I'm going to describe how to create them using my blog as an example. My blog is a pretty easy application. From `Kubernetes` perspective, it's just a container with some static content. And here, you already can notice that static is an opposite of dynamic, so it's the first problem that I'll have to tackle. Turning static content into dynamic. So my blog consists of `markdown` files that are used by `hugo` for a web page generation. ->Initially I was using `hugo` server to serve the static, but it needs way more resources than `nginx`, so I've decided in favour of `nginx`. +>Initially I was using `hugo` server to serve the static, but it needs way more resources than `nginx`, so I've decided in favor of `nginx`. I think that I'll write 2 of 3 posts about it, because it's too much to cover in only one. So here, I'd share how I was preparing my blog to be ready for dynamic environments. @@ -32,7 +33,7 @@ So this is how my workflow looked like before I decided to use dynamic environme - `Keel` spots that images was updated and pulls it. - Pod with a static is being recreated, and I have my blog with a new content -What I don't like about it? I can't test something unless it's in `production`. And when I stated to work on adding comments (that is still WIP) I've understood that I'd like to have a real environment where I can test everything before firing the main pipeline. Even though having a static development environment would be fine for me, because I'm the only one who do the development here, I don't like the concept of static envs, and I want to be able to work on different posts in the same time. Also, adding a new static environment for development purposes it kind of the same amount of work as implementing a solution for deploying them dynamically. +What I don't like about it? I can't test something unless it's in `production`. And when I stated to work on adding comments (that is still WIP) I've understood that I'd like to have a real environemnt where I can test everything before firing the main pipeline. Even though having a static development environment would be fine for me, because I'm the only one who do the development here, I don't like the concept of static envs, and I want to be able to work on different posts in the same time. Also, adding a new static environemnt for development purposes it kind of the same amount of work as implementing a solution for deploying them dynamically. Before I can start deploying them, I have to prepare the application for that. At the first glance changes looks like that: @@ -97,7 +98,7 @@ containers: name: nginx-config ``` -So in the `init` container I'm generating a static content (`--baseUrL` flag is templated with `Helm`). Putting the result to the directory that is mounted as en `emptyDir` volume. And then later I'm mounting this folder to a container with `nginx`. Now I can use my docker image wherever I'd like with the same result It doesn't depend on the hostname that was fixed during the build. +So in the `init` container I'm generating a static content (`--baseUrL` flag is templated with `Helm`). Putting the result to the directory that is mounted as en `emptyDir` volume. And then later I'm mounting this folder to a container with `nginx`. Now I can use my docker image wherever I'd like with the same result It doesn't depend on the hostmame that was fixed during the build. ### No more `latest` Since I want to have my envs updated on each commit, I can't push only `latest` anymore. So I've decided to use `commit sha` as tags for my images. But it means that I'll have a lot of them now and having `300Mb` of images and other media is becoming very painful. That means that I need to stop putting images directly to container during the build. So instead of using `rclone` to get data from `minio` in a `drone` pipeline, I'm adding another `init` container to my deployment. @@ -480,7 +481,7 @@ foreach my $line (@builds_out) ``` {{< /details >}} -It's far from being perfect, but it works, and I like that I was able to finally use `Perl` somewhere +It's far from being perfect, but it works and I like that I was able to finally use `Perl` somewhere 2. I want to have a manifest that I can apply in case of kind of *disaster recovery*. And it means that `ApplicationSet` should contain enough information to deploy a production instance of my blog right off the bat. But I don't want to keep it up-to-date with every new commit hash. So I've decided to keep pushing `latest` to registry but only on `main` builds. So I can use the latest tag in application set, but in the application life-time I'll keep using `SHA` as tags. The only static hard-coded value in the `ApplicationSet` is a version of the `Helm chart`. And I don't know how to automate it yet. But I'm sure that I will do it somehow. I know that it's a very common practice to store all `Argo` resource in `git`. But I don't see any sense in storing manifests for temporary environments that can be recreated by clicking a button in `Drone` or by pushing a new commit. @@ -506,7 +507,7 @@ And then I'm setting an env var `HUGO_PARAMS_GITBRANCH`. And now badge is lookin ## Some kind of conclusion -Even though my application is just a simple blog, I still believe that creating dynamic environments is a great idea that should totally replace static dev'n'stages. And it's not only my blog, I've created dynamic envs for. Two biggest pains *as I think* are `Static content` and `Persistent data` (I think, there are more, but these two are most obvious). I've already shown an example how you can handle the first one, and the second is also a big pain in the ass. In my case this data is the one coming from the `Minio` and I'm not doing anything about it, *but I'll write one more post, when it's solved*, other, in my opinion, more obvious example, are databases. You need it to contain all the data that's required for testing, but you also may want it not to be huge, and it most probably should not contain any sensible personal data. So maybe you could stream a database from the production through some kind of anonymiser, clean it up, so it's not too big. And it doesn't sound easy already. But if I'll have to add something like that to my blog once, I'll try to describe it. +Even though my application is just a simple blog, I still believe that creating dynamic environments is a great idea that should totally replace static dev'n'stages. And it's not only my blog, I've created dynamic envs for. Two biggest pains *as I think* are `Static content` and `Persistent data` (I think, there are more, but these two are most obvious). I've already shown an example how you can handle the first one, and the second is also a big pain in the ass. In my case this data is the one coming from the `Minio` and I'm not doing anything about it, *but I'll write one more post, when it's solved*, other, in my opinion, more obvious example, are databases. You need it to contain all the data that's required for testing, but you also may want it not to be huge, and it most probably should not contain any sensible personal data. So maybe you could stream a database from the production through some kind of anonymizer, clean it up, so it's not too big. And it doesn't sound easy already. But if I'll have to add something like that to my blog once, I'll try to describe it. Thanks, diff --git a/content/posts/argocd-dynamic-environment-per-branch-part-2/index.md b/content/posts/argocd-dynamic-environment-per-branch-part-2/index.md new file mode 100644 index 0000000..5127b42 --- /dev/null +++ b/content/posts/argocd-dynamic-environment-per-branch-part-2/index.md @@ -0,0 +1,53 @@ +--- +title: "Argocd Dynamic Environment per Branch Part 2" +date: 2023-03-29T17:31:20+02:00 +draft: true +ShowToc: true +cover: + image: "cover.png" + caption: "Argocd Dynamic Environment per Branch Part 2" + relative: false + responsiveImages: false +--- + +So it's been a while since the last post. And I'd like to continue the topic, because I've updated some things. But at the same time I'd like to talk about the setup that I've got and why I think it is good. + +First, I'd like to show how I fixed the Minio issue from the previous post. + +>I’m using Minio as a storage for pictures, and currently all pictures (and other files) are stored in one folder regardless of the environment. + +I've started using `git lfs` for media data. But I still want to have small docker images so I've decided to add some logi around pushing media files to `Minio`. So I've added a Drone job: +```YAML + - name: Sync pictures from lfs to Minio + image: rclone/rclone:latest + when: + branch: + exclude: + - main + environment: + RCLONE_CONFIG_CONTENT: + from_secret: RCLONE_CONFIG_CONTENT_PRIVATE + RCLONE_CONFIG: /tmp/rclone.conf + commands: + - echo "$RCLONE_CONFIG_CONTENT" > $RCLONE_CONFIG + - apk update + - apk add git make + - make upload_static + + - name: Sync pictures to the main Minio bucket + image: rclone/rclone:latest + when: + branch: + - main + environment: + RCLONE_CONFIG_CONTENT: + from_secret: RCLONE_CONFIG_CONTENT_PRIVATE + RCLONE_CONFIG: /tmp/rclone.conf + commands: + - echo "$RCLONE_CONFIG_CONTENT" > $RCLONE_CONFIG + - apk update + - apk add git make + - make sync_static_with_main +``` + + diff --git a/content/posts/argocd-vs-helmfile-application/cover.png b/content/posts/argocd-vs-helmfile-application/cover.png new file mode 100644 index 0000000..7536770 Binary files /dev/null and b/content/posts/argocd-vs-helmfile-application/cover.png differ diff --git a/src/content/post/allanger/argocd-vs-helmfile-application.md b/content/posts/argocd-vs-helmfile-application/index.md similarity index 97% rename from src/content/post/allanger/argocd-vs-helmfile-application.md rename to content/posts/argocd-vs-helmfile-application/index.md index eef42f2..65c26ba 100644 --- a/src/content/post/allanger/argocd-vs-helmfile-application.md +++ b/content/posts/argocd-vs-helmfile-application/index.md @@ -1,13 +1,14 @@ -+++ -title = "ArgoCD vs Helmfile: Applications" -date = 2023-02-13T12:14:09+01:00 -image = "/posts/argocd-vs-helmfile/cover-applications.png" -draft = false -categories = [ - "Kubernetes", - "CI-CD" -] -+++ +--- +title: "ArgoCD vs Helmfile: Applications" +date: 2023-02-13T12:14:09+01:00 +draft: false +cover: + image: "cover.png" + caption: "ArgoCD" + relative: false + responsiveImages: false +ShowToc: true +--- > So as promised in [the previous ArgoCD post]({{< ref "dont-use-argocd-for-infrastructure" >}}), I'll try to show a simple example of Pull Requests for different kinds of setups. This is the first part. Putting everything in the same post seems kind of too much. @@ -64,7 +65,7 @@ But logic would be like this - Add a new application to the `manifests/$CLUSTER` dir - Push - CI/CD - - Since it needs to be `GitOps`, you need to check that charts in the `vendor` dir are up-to-date with `helm-freeze.yaml`. *Because if you updated helm-freeze and forgot to execute `helm-freeze sync`, you will have a contradiction between actual and desired states. That's one of the reasons, why I don't like this kind of vendoring. Either it's an addition step in CI, that is verifying that the manual step was done, or it's an additional work for reviewer. You also can add an action that is going to execute it within the pipeline and push to your branch, but I'm completely against it. (something for another post maybe)* + - Since it needs to be `GitOps`, you need to check that charts in the `vendor` dir are up-to-date with `helm-freeze.yaml`. *Because if you updated helm-freeze and forgot to execute `helm-freeze sync`, you will have a contradiction between actual and desired states. That's one of the reasons, why I don't like this kind of vendoring. Either it's an addition step in CI, that is verifying that the manual step was done, or it's an additional work for reviewer. You also can add an action that is going to execute it withing the pipeline and push to your branch, but I'm completely against it. (something for another post maybe)* - Then depending on a branch: - If not `main` @@ -440,7 +441,7 @@ argocd app diff vpa FATA[0000] rpc error: code = NotFound desc = error getting application: applications.argoproj.io "vpa" not found ``` -There is a `--local` option, but it still requires a name ~~(why if there is a name in manifests 🙃🙃🙃)~~ +There is a `--local` option, but it still requires a name ~~(why if there is a name in manfiests 🙃🙃🙃)~~ ```BASH # Just testing out argocd app diff vpa --local ./manifests/cluster2/ @@ -542,7 +543,7 @@ Let's try installing apps directly. Remove an app-of-apps from k8s. And let's us ## Conclusion So you can check the PR here: -I like that `values` can be handled as normal values files. (But for handling secrets you might have to add a [CMP](https://argo-cd.readthedocs.io/en/stable/user-guide/config-management-plugins/), that means an additional work and maintenance) But even if adding CMP is fine, I couldn't get proper `diffs` for my changes, that means that I can't see what's happening without applying manifests. And applying manifests will mean that other team members will not be work on other tickets within the same scope, so it looks like a bottleneck to me. +I like that `values` can be handled as normal values files. (But for handling secrets you might have to add a [CMP](https://argo-cd.readthedocs.io/en/stable/user-guide/config-management-plugins/), that means an additional work and maintenance) But even if adding CMP is fine, I couldn't get proper `diffs` for my changes, that means that I can't see what's happening without applying manifests. And applying manifests will mean that other team members will not be work on other tickets withing the same scope, so it looks like a bottleneck to me. But I don't like that you need to add a lot of manifests to manage all the applications. We have only 2 manifests that are copied from folder to folder. So we have a lot of repeating code. And repeating code is never good. So I would write a tool that can let you choose applications from the list of all applications and choose clusters where they need to be deployed. So the config looks like this: ```YAML @@ -564,7 +565,7 @@ But I think that with the whole GitOps pulling concept it will be a hard thing t I can only say, that I see no profit in using argo like this. It only seems like either a very complicated setup (most probably you will be able to implement anything you need, the question is, how much time will you spend with that), or a ~~crippled~~ not complete setup. -And if you compare an amount of lines that area updated to install these apps as `Applications` to the helmfile stuff, it's going to be ~100 vs ~30. And that's what I also don't like. +And if you compare an amount of lines that area updadated to install these apps as `Applications` to the helmfile stuff, it's going to be ~100 vs ~30. And that's what I also don't like. In the next post I will try doing the same with `ApplicationSets`, and we'll see, if it looks better or not. diff --git a/content/posts/argocd-vs-helmfile-applicationset/cover.png b/content/posts/argocd-vs-helmfile-applicationset/cover.png new file mode 100644 index 0000000..d242e3a Binary files /dev/null and b/content/posts/argocd-vs-helmfile-applicationset/cover.png differ diff --git a/src/content/post/allanger/argocd-vs-helmfile-applicationset.md b/content/posts/argocd-vs-helmfile-applicationset/index.md similarity index 93% rename from src/content/post/allanger/argocd-vs-helmfile-applicationset.md rename to content/posts/argocd-vs-helmfile-applicationset/index.md index 1fef0be..4cefb06 100644 --- a/src/content/post/allanger/argocd-vs-helmfile-applicationset.md +++ b/content/posts/argocd-vs-helmfile-applicationset/index.md @@ -1,13 +1,14 @@ -+++ -title = 'ArgoCD vs Helmfile: ApplicationSet' -date = 2023-02-15T10:14:09+01:00 -image = "/posts/argocd-vs-helmfile/cover-applicationset.png" -draft = false -categories = [ - "Kubernetes", - "CI-CD" -] -+++ +--- +title: "ArgoCD vs Helmfile: ApplicationSet" +date: 2023-02-15T10:14:09+01:00 +draft: false +cover: + image: "cover.png" + caption: "ArgoCD" + relative: false + responsiveImages: false +ShowToc: true +--- This is a second post about *"argocding"* your infrastructure. [First can be found here]({{< ref "argocd-vs-helmfile-application" >}}). @@ -63,7 +64,7 @@ spec: ``` -Manifests with a setup like this have only one values that is really different, so we could create just one manifest that would look like that: +Manifests with a setup like thos have only one values that is really different, so we could create just one manifest that would look like that: ```YAML apiVersion: argoproj.io/v1alpha1 kind: ApplicationSet @@ -208,7 +209,7 @@ Those applications should be deployed automatically within a pipeline. So steps - Add new generators - Sync applications with argocd cli -But I'm not sure what going to happen if you have two different pipelines at the same time. Probably, changes will be overwritten but the pipeline that is a little bit slower. But I think that it can be solved without a lot of additional problems. And also I don't think that it's a situation that you will have to face very often, so you can just rerun your pipeline after all. +But I'm not sure what going to happen if you have two different pipelines at the same time. Probably, changes will be overwriten but the pipeline that is a little bit slower. But I think that it can be solved without a lot of additional problems. And also I don't think that it's a situation that you will have to face very often, so you can just rerun your pipeline after all. ### Diffs Diffs are not supported for `ApplicationSets` at the moment, and I'm not sure when they will be: diff --git a/src/content/post/allanger/argocd-vs-helmfile-helmfile.md b/content/posts/argocd-vs-helmfile-helmfile/index.md similarity index 99% rename from src/content/post/allanger/argocd-vs-helmfile-helmfile.md rename to content/posts/argocd-vs-helmfile-helmfile/index.md index ab2999d..69915cb 100644 --- a/src/content/post/allanger/argocd-vs-helmfile-helmfile.md +++ b/content/posts/argocd-vs-helmfile-helmfile/index.md @@ -1,13 +1,11 @@ -+++ -title = "Argocd vs Helmfile: Helmfile" -date = 2023-02-17T12:48:51+01:00 -draft = false -categories = [ - "Kubernetes", - "CI-CD" -] -+++ -In two previous posts I've described how it's possible to install a couple of applications with [`Applications`]({{< relref "/post/allanger/argocd-vs-helmfile-application" >}}) and [`ApplicationSets`]({{< relref "/post/allanger/argocd-vs-helmfile-applicationset" >}}), and this one is the last in a row. And here I'm going to install the same applications (`VPA` and `Goldilocks`) with helmfile, and I will tell why I think that it's better than `ArgoCD` +--- +title: "Argocd vs Helmfile: Helmfile" +date: 2023-02-17T12:48:51+01:00 +draft: false +ShowToc: false +--- + +In two previous posts I've described how it's possible to install a couple of applications with [`Applications`]({{< ref "argocd-vs-helmfile-application" >}}) and [`ApplicationSets`]({{< ref "argocd-vs-helmfile-applicationset" >}}), and this one is the last in a row. And here I'm going to install the same applications (`VPA` and `Goldilocks`) with helmfile, and I will tell why I think that it's better than `ArgoCD` So let's start. Here you can find the [initial config](https://git.badhouseplants.net/allanger/helmfile-vs-argo/src/branch/helmfile-main). Let's see what we got here: @@ -80,7 +78,7 @@ helmfiles: - path: {{.Environment.Name }}/helmfile.yaml ``` -It's going to import helmfiles that are not used across all clusters. So if you want to install something to `cluster-2` across, you will add it to the `/cluster2/helmfile.yaml` and sync the main helmfile. I will show an example later. +It's going to import helmfiles that are not used across all clusters. So if you want to install something to `cluster-2` accross, you will add it to the `/cluster2/helmfile.yaml` and sync the main helmfile. I will show an example later. So we're all set and ready to begin installing new stuff. @@ -1577,7 +1575,7 @@ Yeah, it's huge, but you can see everything that's going to happen. So I'd say i It's a short article, because I think the whole setup is super easy, CI is easy too. You still have a full `GitOps` (or almost full) but you also have control. I love this setup and would like to use it for my infrastructure. Why do I think it's better that `ArgoCD`? -With `ArgoCD` I either have a lot of `yaml` to install things, or I have complicated setups with `ApplicationSets` that are most probably very special and won't be reused in other companies. I need to care about how `ArgoCD` will handle a lot of applications that are added there only for diffing. I need additional applications installed in my clusters not only as a part of infrastructure itself, but also as a service that I'm providing other teams with. Because I want to manage applications that are being developed by other teams with `Argo`, so I'm mixing a lot of different kinds of applications here. +With `ArgoCD` I either have a lot of `yaml` to install things, or I have complicated setups with `ApplicationSets` that are most probably very special and won't be reused in other companies. I need to care about how `ArgoCD` will handle a lot of applications that are added there only for diffing. I need additional applications installed im my clusters not only as a part of infrastructure itself, but also as a service that I'm providing other teams with. Because I want to manage applications that are being developed by other teams with `Argo`, so I'm mixing a lot of different kinds of applications here. Helmfile lets me separate infra from applications. `ArgoCD` can be only provided as a service, and other teams can use, because it's making k8s easier for those who don't need to understand it so deeply. Also, helmfile lets me use helm-secrets to encrypt values. I can do it with Argo too, but then I need to either have a custom `ArgoCD` image, or support a CMP plugin, that will handle SOPS. diff --git a/content/posts/design-a-scalable-system/index.md b/content/posts/design-a-scalable-system/index.md new file mode 100644 index 0000000..6f219db --- /dev/null +++ b/content/posts/design-a-scalable-system/index.md @@ -0,0 +1,26 @@ +--- +title: "Design a Scalable System" +date: 2023-03-06T21:18:23+01:00 +draft: true +ShowToc: true +cover: + image: "cover.png" + caption: "Design a Scalable System" + relative: false + responsiveImages: false +--- + +Well, after I've posted my argo serie, I've found out that I couldn't really make myself understood. So now I want to talk more not about the way of implementation, but rather about the consequinces of different implementations. And maybe I will e able to finally make a point about why I don't like Terraform and why I think that ArgoCD is mostly mis-used by almost any SRE team I know. + +But first I'll try to describe how I see myself as a part of a team, the team as a part of a bigger team, and all the teams across different companies as links in the bigger chain. + +This is how I used to see development teams before: + +![Chain](/posts/design-a-scalable-system/chain-1.png) + +The whole team is using something as a service, for example `AWS`, the whole team is working together and producing something that is passed to a customer. But apparently this approach is only applicable to small teams, and I think it's working just fine. But there is a problem. Teams tend to grow without an understanding that they are growing, hence they keep acting like they're small but in the same time they don't change the workflow, and brick-by-brick they are building something that eventually is something unscalable at first and later unmaintanble. + +Example of an evolution like this: + +Let's take a regular Java(backend) + JS(frontend) web application + diff --git a/content/posts/dont-use-argocd-for-infrastructure/cover.png b/content/posts/dont-use-argocd-for-infrastructure/cover.png new file mode 100644 index 0000000..1154626 Binary files /dev/null and b/content/posts/dont-use-argocd-for-infrastructure/cover.png differ diff --git a/src/content/post/allanger/dont-use-argocd-for-infrastructure.md b/content/posts/dont-use-argocd-for-infrastructure/index.md similarity index 98% rename from src/content/post/allanger/dont-use-argocd-for-infrastructure.md rename to content/posts/dont-use-argocd-for-infrastructure/index.md index fbae692..5dfa0e9 100644 --- a/src/content/post/allanger/dont-use-argocd-for-infrastructure.md +++ b/content/posts/dont-use-argocd-for-infrastructure/index.md @@ -1,14 +1,14 @@ -+++ -title = "Don't use ArgoCD for your infrastructure" -date = 2023-02-09T12:47:32+01:00 -draft = false -image = '/posts/dont-use-argocd-for-infrastructure/cover.png' -categories = [ - "Kubernetes", - "CI-CD" -] -+++ - +--- +title: "Don't use ArgoCD for your infrastructure" +date: 2023-02-09T12:47:32+01:00 +draft: false +ShowToc: true +cover: + image: "cover.png" + caption: "ArgoCD" + relative: false + responsiveImages: false +--- > Of course, it's just a clickbait title. Use whatever works for you. I will just describe why I wouldn't use `ArgoCD` for the infrastructure ## Prelude diff --git a/content/posts/vst-on-linux-1/cover.png b/content/posts/vst-on-linux-1/cover.png new file mode 100644 index 0000000..6487c55 Binary files /dev/null and b/content/posts/vst-on-linux-1/cover.png differ diff --git a/content/posts/vst-on-linux-1/index.md b/content/posts/vst-on-linux-1/index.md new file mode 100644 index 0000000..eec993d --- /dev/null +++ b/content/posts/vst-on-linux-1/index.md @@ -0,0 +1,287 @@ +--- +title: "Vst on Linux 1" +date: 2023-01-24T15:47:50+01:00 +draft: false +ShowToc: true +cover: + image: "cover.png" + caption: "Vst on Linux" + relative: false + responsiveImages: false +--- + +>Best, but according to Output. Their article: *[https://output.com/blog/output-favorites-freebies](https://output.com/blog/output-favorites-freebies) + +This is kinda article where I'm looking for "BEST FREE VST" articles or videos, or whatever, trying to run them on Linux and checking how they perform. The first article I've found is one by **Output**, so be it. + +--- + +## 1. Arcade by Output 👎 + +Freaking unexpected, huh? But what choice do I have? **Walk the walk and talk the talk. **So let's start by pressing the "TRY IT FREE" button. + +First I need to enter my email, then I need to enter a bunch of information about myself and then: What a bummer, they want me to add a payment method. And even thought they won't charge me the first month, I'm not doing talking the talk. Sorry, let's go to the next one. + +--- + +## 2. OTT by Xfer 👍 + +This one you will find in any top, I believe. It can mean only one thing: it's really one of the best. So let's try. + +There is no Linux version of this plugin, so we will have to use the Windows one. How, you would ask me? I will have to install a couple of packages to my system before I'm ready. I'm starting by installing **wine**.   + +I am not going to describe the process of installing it, google `"$YOUR_LINUX_DISTRO_NAME install wine" ` after it's done you may want to create a new wine prefix in your system. + +What is wine prefix? Let's think of it as of a directory that contains Windows-related stuff. All plugins will be installed there alongside libraries that are required to make them work. + +Let's give this prefix a recognizable name, like `.wine_vst_plugins.` I'm opening the terminal, yes, I'll have to use it, but you shouldn't be scared of it, because terminal is our friend. Opening it and executing: + + $ WINEPREFIX="$PWD/.wine_vst_plugins/" winecfg + + +It will open a window when you can configure your wine prefix, but the main stuff is already done, so I just close it. + +To check if we're happy, I'm executing the following + + $ ls -la $HOME/.wine_vst_plugins + + total 3332 + drwxr-xr-x 1 allanger allanger 126 Oct 27 18:13 . + drwx------ 1 allanger root 1922 Oct 27 18:15 .. + drwxr-xr-x 1 allanger allanger 8 Oct 27 18:13 dosdevices + drwxr-xr-x 1 allanger allanger 110 Oct 27 18:13 drive_c + -rw-r--r-- 1 allanger allanger 3282847 Oct 27 18:13 system.reg + -rw-r--r-- 1 allanger allanger 12 Oct 27 18:13 .update-timestamp + -rw-r--r-- 1 allanger allanger 4130 Oct 27 18:13 userdef.reg + -rw-r--r-- 1 allanger allanger 113309 Oct 27 18:13 user.reg + + +If your output looks like mine, we're good to go. Let's install the second tool: [https://github.com/robbert-vdh/yabridge](https://github.com/robbert-vdh/yabridge). You will find all the instructions if you just scroll down a wee bit. After installing it you also must have a tool called **yabridgectl,** to check that it is right, just execute the following + + $ yabridgectl + + yabridgectl 4.0.2 + Robbert van der Helm + Optional utility to help set up yabridge + + USAGE: + yabridgectl + + OPTIONS: + -h, --help Print help information + -V, --version Print version information + + SUBCOMMANDS: + add Add a plugin install location + rm Remove a plugin install location + list List the plugin install locations + status Show the installation status for all plugins + sync Set up or update yabridge for all plugins + set Change the yabridge path (advanced) + blacklist Manage the indexing blacklist (advanced) + help Print this message or the help of the given subcommand(s) + + + +I hope you're seeing pretty much the same picture as I am. And it only means that we can go further. + +Now it's time to install the plugin itself. I'm downloading the **Windows** version and opening my terminal again + +Let's assume that you've downloaded it to the `~/Downloads` folder, and the file name is `Install_Xfer_OTT_135.exe` + + $ cd ~/Dowloads + $ WINEPREFIX="$PWD/.wine_vst_plugins/" wine ./Install_Xfer_OTT_135.exe + + +Why we're adding this `WINEPREFIX` thing every time when running `wine`? Because we're saying which wine prefix should be used by wine, since it's not a default path for the prefix. + +After installing this plugin, I will need to add it to **yabridge**. To do that, use **yabridgectl** + +Insted of what I'm putting after `/drive_c/`, provide a path that you've chosen during the installation + + $ yabridgectl add ~/.wine_vst_plugins/drive_c/Program\ Files/Common\ Files/VST + $ yabridgectl sync + + +And I'm opening a DAW, *I assume you already have one too, for here you are. But if you don't, and you don't know which to install, just install **Ardour.*** + +I'm opening it, adding a track and adding the **OTT** plugin to that track. + +![OTT Xfer](/posts/vst-on-linux-1/ott-xfer.png) + +It is working and I would even say it's running +The UI part is a wee bit buggy, but I don't think that it's a problem. + +--- + +## 3. Wider by Polyverse 👍 + +I'm entering my email again and receiving a download link. Downloading, unpacking, and installing + + $ WINEPREFIX="$PWD/.wine_vst_plugins/" wine ./InfectedMushroom-Wider-V1.1.3.exe + $ yabridgectl sync + + +![Wider](/posts/vst-on-linux-1/wider.png)Again, it's working flawlessly +So far so good, even the UI part is perfect. + +--- + +## 4. CamelCrusher by Camel Audio 👍 + +It can be downloaded even without email thingy. + + $ WINEPREFIX="$HOME/.wine_vst_plugins/" wine ./camelcrusher-win_mac\ \(www.mpcindia.co\)/CamelCrusherWin-1-0-1-x64.exe + $ yabridgectl sync + + + And when I'm trying to add it to Ardour, I'm getting an error + + [Info]: Scanning: /home/allanger/.vst/yabridge/CamelCrusher.so + 09:23:38 [error] + 09:23:38 [error] Error during initialization: + 09:23:38 [error] '/home/allanger/.vst/yabridge/CamelCrusher.dll' does not exist, make sure to rename 'libyabridge-vst2.so' to match a VST plugin .dll file. + 09:23:38 [error] + [ERROR]: ** ERROR** VSTFX : CamelCrusher could not be instantiated :( + + [WARNING]: Cannot get VST information from '/home/allanger/.vst/yabridge/CamelCrusher.so': instantiation failed. + Scan Failed. + + +And I can't actually understand what is the problem here. + +I don't give up so quickly. Let's try running it via [Carla](https://github.com/carla-simulator/carla). I won't describe how to install it, you can google it. + + +So after it's installed, I'm opening it as a standalone app first and trying to add my **CamelCrusher** there. And it's working. Then the next step is to add **Carla** as a **FX** plugin in **Ardour** and then add CamelCrusher there. +![CamelCrush](/posts/vst-on-linux-1/camel-crush.png)Working again, but not without Carla + +--- + +## 5. Fracture by Glitchmachines 👍 + +I love this plugin, and I'm using it a lot on my MacBook, so it would be nice to run it on **Linux** too. So let's go. But Glitchmachines can give us another great plugin for free, so I will try running both of them here. The other one is **Hysteresis**. So I'm downloading both of them. + +After receiving two links, I'm installing them + + $ WINEPREFIX="$HOME/.wine_vst_plugins/" wine Fracture_setup.exe + $ WINEPREFIX="$HOME/.wine_vst_plugins/" wine Hysteresis_setup.exe + $ yabridgectl sync + + +![Glitchmachines](/posts/vst-on-linux-1/glitchmachines.png) + +They are working but there is one UI glitch + +![Glitchmachine's making glitch](/posts/vst-on-linux-1/glitchmakesrs-glitch.gif) + +#### Maybe you won't notice it on your system + +Because we probably have different system configs, so maybe it's only possible to reproduce this bug with a set of configs and packages I'm using in my Linux. So if you don't face this issue, lucky you! + +It's not very annoying to me, but to avoid this kind of behavior, I can wrap these plugins with **Carla.** +![Glitchmachines with Carla](/posts/vst-on-linux-1/glitchmaker-carla.gif) +It's working perfectly with Carla *(it's not that buggy in real life, only on the record)* + +--- + +## 6. FreqEcho by Valhalla DSP 👍 + +Valhalla's plugins, I think, are one of the most popular in the music world. I don't know a man who doesn't have all of their free plugins installed.  And I do have them installed already in my system, but I will go through the installation process again, just to describe it here. So let's download all of their free plugins + +- Valhalla Freq Echo +- Valhalla Space Modulator +- Valhalla Supermassive +```BASH +$ WINEPREFIX="$HOME/.wine_vst_plugins/" wine ValhallaFreqEchoWin_V1_2_0.exe +$ WINEPREFIX="$HOME/.wine_vst_plugins/" wine ValhallaSpaceModulatorWin_1_1_6v3.exe +$ WINEPREFIX="$HOME/.wine_vst_plugins/" wine ValhallaSupermassiveWin_V2_0_0.exe +$ yabridgectl sync +``` + +![Valhalla plugins](/posts/vst-on-linux-1/valhalla.png) +All of them run flawlessly + +--- + +## 7. Audio Treasure by Max For Cats 👎 + +As far as I could understand, it can be used only in **Ableton Live**, and since I'm not an Ableton user, and I don't want to run it with **Wine** *(cause there is no native Linux version)*, it's becoming the second plugin in the list, that is not working on + +## 8. Saturation Knob by Softube 👎 + +To get it, I must have a Softube account, (*but I already have it, because I used to download all them free plugins like nuts and create accounts everywhere 🤦)* + +So I'm downloading their App Center, that I'm going to use to install a plugin. *I do hate this approach of managing software, but I will cover it in another post one day. * + +So the process is very similar to a direct plugin installation. Install **Softube Central** to the same **Wine** prefix + + WINEPREFIX="$HOME/.wine_vst_plugins/" wine Softube\ Central\ Setup\ 1.7.1.exe + + +But after that, I've found out that their **Software Center** is written is **Electron-based** application, and I wasn't yet able to run stuff like this in **Wine**. Maybe later I will put more effort into that, but for now, I'm saying that it's not working. 😥 + +> #### Some kind of rhetorical question +> +> I don't understand why they and, for example, **Splice** can't release a Linux version of their application, it they already use Electron, that in my understanding is supposed for cross-platform development. + +--- + +## 9 and 10. Plugins by iZotope 👎 + +**iZotope** is like **Valhalla**, everybody knows it. But I remember having troubles with their plugins on **Linux**. But now I'm trying again, and I'm full of hope. + +Plugins: + +- iZotope Vinyl +- iZotope Ozone Imager V2 *(it's not in the Output list, but why not?)* +- iZotope Vocal Doubler + +One more plugin vendor that requires an account creation. But I do have one from those good old times. + +Well, since I remember that there was a problem with them, I'll start by trying only one. Let it be **Ozone Imager V2**. + + $ WINEPREFIX="$HOME/.wine_vst_plugins/" wine iZotope_Ozone_Imager_v2_1_0.exe + + +But unfortunately, when I'm opening these plugins, it asks for an authorization, and it doesn't work. It's described in the **yabridge README.md**,but I'm too dummy to read it there. + +#### There is a workaround + +I've heard that you can download cracked versions of these plugins and they won't require an auth, so they might work. But I'm not trying that, and you shouldn't too. + +--- + +## 11. TAL-Chorus-LX 👍👍👍 + +It's a piece of cake. This plugin has a native build for Linux, so I'm (since I'm using **Arch Linux**) just installing it using **yay**. And you may want to use another package manager, or download it from the official web page, it's presented there. +![NATIVE, YOU KNOW!](/posts/vst-on-linux-1/tal-chorus.png) + + +--- + +## 12. Snap Heap by Kilo Hearts 👎 + +I was trying to get it, but It didn't seem free. + +![Snap Heap](/posts/vst-on-linux-1/snap-heap.png) + +--- + +## 13. Signal Free VST by Output 👎 + +I'm sorry, but I'm not even trying. It still hurts since the first place in this top. + +--- + +## Some kind of conclusion + +First, you have seen only pictures here but haven't heard anything I've done with these plugins. And I know that it sucks, because we're talking about music. I'll record a track using these plugins later and show you how it's working. + +About those plugins that didn't work: I know that some of them are great, and it's sad that **iZotope** are not running on Linux, but there are alternatives that are Linux native. So for each failed one I will try to find an alternative, and later I will share my findings here. + +Thanks for reading + +Oi! + + diff --git a/content/posts/vst-on-linux-2/cover.png b/content/posts/vst-on-linux-2/cover.png new file mode 100644 index 0000000..71116c3 Binary files /dev/null and b/content/posts/vst-on-linux-2/cover.png differ diff --git a/content/posts/vst-on-linux-2/index.md b/content/posts/vst-on-linux-2/index.md new file mode 100644 index 0000000..c60910c --- /dev/null +++ b/content/posts/vst-on-linux-2/index.md @@ -0,0 +1,138 @@ +--- +title: "Vst on Linux 2" +date: 2023-01-31T19:32:34+01:00 +ShowToc: true +cover: + image: "cover.png" + caption: "VST on Linux" + relative: false + responsiveImages: false +--- + +Big ups, **Venus Theory!** +[Link to the video](https://www.youtube.com/watch?v=OCzf38fCqB4) + +## Prerequisite +All of them are covered in [the first post]({{< ref "vst-on-linux-1" >}} ) + +- You have Wine and Yabridge installed +- You have a Wine prefix configured (in my case, `$HOME/.wine_vst_plugins/`, so every time you see it, use your own wine prefix) + +## Deelay 👍 + +You can find it here: [https://sixthsample.com/deelay/](https://sixthsample.com/deelay/) + + +After receiving a link, I'm downloading a **Windows 64-bit** version and running +```BASH + +$ WINEPREFIX="$HOME/.wine_vst_plugins/" wine Deelay-1.0.3-Installer-64bit.exe +$ yabridgectl sync +``` + +![A running deelay](/posts/vst-on-linux-2/deelay.png) + +It's running, but the context menus UI glitch is present +Audio qualities of this plugin on Linux are prefect, but when you open any drop-down menu, plugin's window is getting hidden. + +![UI glitch](posts/vst-on-linux-2/deelay-glitch.gif) + +But it can be fixed with **Carla**. If I'm putting Carla to my FX chain and then adding **Deelay** to **Carla**, this problem is gone. + +## Surge XT 👍👍👍 + +This plugin has a native **Linux** version, and it's open-source, so just install it with your package manager or download from the official site. You won't even have to touch **yabridge** and **wine** this time + +[**Source code**](https://github.com/surge-synthesizer/surge) + +![Surge XT Linux native](/posts/vst-on-linux-2/surge.png) + +## Cardinal 👍👍👍 + +**You won't believe me!** + +But it's open-source too and has supports **Linux** out of the box. + +[**Source code**](https://github.com/DISTRHO/Cardinal) + +![Again native and open-source](/posts/vst-on-linux-2/cardinal.png) + +## Fire 👍👍👍 + +*It ... is ... open ... source ... too ... and ... supports ... **Linux*** + +[**Source code**](https://github.com/jerryuhoo/Fire) + +So I'm just installing it with a package manager and trying. +![A real fire](/static/posts/vst-on-linux-2/fire.png) + +## Ruina 👍 + +*And a couple of others* + +It would be too good, if this one had a Linux version. To get this plugin, you will have to create an account, and download their installer 👿 + +[https://noiseengineering.us/products/the-freequel-bundle-sinc-vereor-virt-vereor-ruina](https://noiseengineering.us/products/the-freequel-bundle-sinc-vereor-virt-vereor-ruina) + +After downloading an Installer, I'm installing it with **wine **to the same prefix I install all their other plugins + + $ WINEPREFIX="$HOME/.wine_vst_plugins/" wine Noise\ Engineering\ Products\ 09358.exe + +![The installer](/static/posts/vst-on-linux-2/noise-engineering.png) + +It will install plugins, we've only left to sync yabridge config. + + $ yabridgectl sync + +![Running Ruina ](/posts/vst-on-linux-2/runia-plugin.png) + +![Sinc Vereor](/posts/vst-on-linux-2/sirt-plugin.png) + +![Virt Vereor](/posts/vst-on-linux-2/virt-vereor.png) + +All of them are working flawlessly. One wouldn't even notice that they're not native + +--- + +## Gatelab 👍 / Filterstep 👎 / Panflow 👍 + +No **Linux** version again, so I'm gonna. And they want me to enter my email again. That's a shame, but let's do it anyway. If Venus Theory says they're good, I'm sure they really are. + + $ export WINEPREFIX="$HOME/.wine_vst_plugins/" + $ wine Audiomodern_Filterstep_1.1.2/WIN/Filterstep_64\ 1.1.2\ \(Win64\).exe + $ wine Audiomodern_Gatelab_1.1.3/WIN/Gatelab\ 1.1.3\ \(Win64\).exe + $ wine Audiomodern_Panflow_1.0.1/WIN/Panflow\ 1.0.1\ \(Win64\).exe + +I had to rerun Ardour multiple times in order to make these plugins work. **Panflow** is running fine + +![Panflow](/posts/vst-on-linux-2/panflow.png) + +Gatelab is working fine too + +![Gatelab](/posts/vst-on-linux-2/gatelab.png) + +But when I add **Filterstep**, Ardour stops responding. I'm sure it's possible to make it work too, so I will try doing that in one of the next articles. + +## PaulXStretch 👍👍👎 + +I was tired after **Audiomodern** plugins, because they were freezing my Ardour and I had to log out and log in again to my system, for Ardour wouldn't run again after that. + +But **PaulXStrech** has a native Linux version too, and it has given me a strength to finish with this top. + +So I'm just installing it with a package manager. + +But my expectations were too high. I couldn't add PaulXStretch as a plugin in my **DAW**, even **Carla** couldn't handle it. Only [Kushview Element](https://kushview.net/) could handle it outside a **DAW**, but I couldn't connect Ardour with Element using JACK yet (probably because I'm too dummy). But when running **Element** as a plugin inside an **Ardour**, when I add PaulXStretch, Ardour crashes. + +But on the official site of this plugin, there is nothing said about a plugin version of PaulXStretch for Linux. So you can use it as a standalone application. Just record whatever you want, stretch and render an audio file to import it to your **DAW**. +![PaulXStretch as a standalone application](/posts/vst-on-linux-2/paulxstretch.png) +--- + +Actually, I'm very happy to see that 4 of 9 plugins has a native Linux support. It means that developers see now that Linux can be used for music production. And it makes me feel that Linux is becoming more adopted by more and more guys who just want to make music without struggling with their systems. + +--- + +Thanks for reading + +Oi! + + diff --git a/content/posts/vst-on-linux-3/cover.png b/content/posts/vst-on-linux-3/cover.png new file mode 100644 index 0000000..d2524d9 Binary files /dev/null and b/content/posts/vst-on-linux-3/cover.png differ diff --git a/content/posts/vst-on-linux-3/index.md b/content/posts/vst-on-linux-3/index.md new file mode 100644 index 0000000..4efcd3c --- /dev/null +++ b/content/posts/vst-on-linux-3/index.md @@ -0,0 +1,198 @@ +--- +title: "Vst on Linux 3" +date: 2023-02-03T18:26:44+01:00 +draft: false +ShowToc: true +cover: + image: "cover.png" + caption: "Vst on Linux" + relative: false + responsiveImages: false +tags: ['music'] +--- + +I've been told that I should add descriptions to plugins I'm writing about here, and it sounds very reasonable. So now I will not only describe how to install a plugin but also add a small description to it. + +## Prerequisite + +All of them are covered in [the first post]({{< ref "vst-on-linux-1" >}}) + +- You have Wine and Yabridge installed +- You have a Wine prefix configured (in my case, `$HOME/.wine_vst_plugins/`, so every time you see it, use your own wine prefix) + +## Before we begin + +In the previous post, I was trying to run paulxstretch on Linux, and using it as a plugin in a DAW didn't work out. I've tried to update the JUCE library in the source code, and now it's working. You can find the code here: [https://git.badhouseplants.net/badhouseplants/paulxstretch](https://git.badhouseplants.net/badhouseplants/paulxstretch) + +To build, refer to the official build doc or use the `/build_docker.sh` script + +## Melda Free Bundle 👍 + +You can find it here: + +It's not a one plugin, but a whole bunch of them. I used to have it on my Mac a long ago, but I hate this way of managing plugins, so I don't install them if I'm not sure, I need them. And I never felt this way about **Melda Free Bundle.** + +But now I'll try running it on **Linux**. I don't think I'll ever use it, even if it runs smoothly as hell. So I will create an additional temporary wine prefix to install it there. + + $ export WINEPREFIX="$HOME/.wine_vst_plugins_tmp" + $ wine maudioplugins_16_01_setup.exe + +Install Melda Free bundle +### MDrummer + +[MDrummer](https://www.meldaproduction.com/MDrummer) + +Let's start with the MDrummer plugin. I've tried to run it as a plugin in **Ardour**,but it killed it. So I've added it with a **Carla** as a wrapper + +I'm downloading several GBs of samples and other data to make it work. + +![MDrummer](/posts/vst-on-linux-3/mdrummer.png) +I'd say it's over-bloated. And UI is a wee bit laggy on Linux +Let's see what we can do with it + +{{< video "/posts/vst-on-linux-3/mdrummer-example.mp4" "video-1" >}} + +### MDrumReplacer +[MDrumReplacer](https://www.meldaproduction.com/MDrumReplacer) + +As I understand, this plugin is catching drum signals and replacing them with another sound. So I'll add it next to the **MDrummer** in the **Carla Rack**. +![Replacer](/posts/vst-on-linux-3/mdrummer-lfo-carla.png) + +I've also added LFO in the chain, to modify the pitch value of the **MDrumReplacer** with it, so it doesn't sound so boring (at least, to me). + +{{< video "/posts/vst-on-linux-3/mdrummer-example-lfo.mp4" "video-2" >}} + +### MPowerSynth + +It's just a synth. I don't like the interface, and I'm not gonna use it in the future, so I'm simply using a preset. + +{{< video "/posts/vst-on-linux-3/mpower-synth.mp4" "video-3" >}} + +It sounds a wee bet laggy, but it's just on a video + +--- + +*I'm sorry, I'm not trying all of them, because it's too much. Let's try another one and go further.* + +### MGuitarArchitect + +It's like a pedal board, as I see. I can add many effects here. Let's try adding it to the same **Carla Rack** that is used for the bass. + +{{< video "/posts/vst-on-linux-3/mguitar-architect.mp4" "video-4" >}} + +--- + +## u-he TyrellN6 👍 +[u-he TyrellN6 ](https://u-he.com/products/tyrelln6/) + +I think that almost every **u-he** plugins has a native **Linux** support, and **Tyrell** is not an exception. But you most probably won't be able to install it with a package manager, because it's available only on Amazona.de. So just follow the link on the official web-page and download the Linux version. + +This is a pretty minimalistic synth, that can help you produce a lot of cool sounds without spending tons of hours learning it. I definitely can recommend it, as I can recommend anything developed by **u-he** + +Unpack the archive and run the **./install.sh** script + + $ ./TyrellN6-3898/install.sh + +{{< video "/posts/vst-on-linux-3/tyrell.mp4" "video-5" >}} + +I can't tell anything bad about **u-he**, I love all their plugins, I love that they support Linux and I love that they together with **Bitwig** are working on the new plugin open-source format ([CLAP](https://github.com/free-audio/clap)). + +Tyrell is just a very cool free synth. What else can I say? + +--- + +## Valhalla Supermassive 👍 + +I've already covered Valhalla plugins in the [first post]({{< ref "vst-on-linux-1" >}}), so it doesn't make sense to repeat myself, instead of that, I'll add every free **Valhalla** plugin to the project and show you how it's working. + +{{< video "/posts/vst-on-linux-3/vallhalla.mp4" "video-6" >}} + + +## Spitfire Labs 👍 +[Spitfire Labs](https://labs.spitfireaudio.com/?sortBy=prod_products_labs_latest) + +I think, everybody knows what's that. But if you don't and you don't mind creating a Spitfire account, just try. + +I need to create an account for downloading that. *But I already have one, because I'm an active LABS user.* + + $ wine SpitfireAudio-Win-3.4.0.exe + $ yabridgectl sync + +You will have to install presets +![Spitfire App](/posts/vst-on-linux-3/spitfire-labs-app.png) + +{{< video "/posts/vst-on-linux-3/labs-example.mp4" "video-7" >}} + +## Infinite Space Piano 👍 + +[Space Piano](https://zaksound.com/infinite-space-piano/) + +This is a piano synth. I already have a lot of them, and as for me, this is yet another one. But is sounds pretty good, so you may like it. + +This time I really need to create an account, because it's the first time I hear about this one. + +There is no **Linux** version, I'm getting the **Windows** one. I've got a feeling that I'm not gonna use it in the future, so I'm installing it in the temporary prefix. + + $ export WINEPREFIX="$HOME/.wine_vst_plugins_tmp/" + $ wine Infinite\ Space\ Piano\ 2.exe + $ yabridgectl sync + +{{< video "/posts/vst-on-linux-3/space-piano.mp4" "video-8" >}} + +## ProjectSAM Free Orchestra 👎 +[Free Orchestra](https://projectsam.com/libraries/the-free-orchestra/) +![Free Orchestra](/posts/vst-on-linux-3/native-access.png) +Ok, let's try +I'm downloading **Native Access**, and it's not working. And this is the moment, I'm giving up on this plugin. + +## Eventide Pendulate👍 +[Eventide Pendulate](https://www.eventideaudio.com/plug-ins/pendulate/) + +Downloading a Windows version again. + + $ wine Pendulate-1.3.6-windows-installer.exe + $ yabridgectl sync + +{{< video "/posts/vst-on-linux-3/eventide-pendulate.mp4" "video-9" >}} + +Runnin just fine +As you see, this is a pretty interesting Synth, I have enough of synths for everything, but this one may join the ranks too. + +## VCV Rack 👍 +[VCV Rack](https://vcvrack.com/) + +VCV Rack is an open-source Eurorack modular synthesizer simulator + +I've already covered the Cardinal plugin [here]({{< ref "vst-on-linux-2" >}}). And this is basically the same thing. And so I will just show **Cardinal** instead of **VCV Rack**. But if you want VCV Rack, it's working on Linux just fine, but you can't use the free version as a plugin, that's why I'm showing Cardinal + +{{< video "/posts/vst-on-linux-3/vcv-rack.mp4" "video-10" >}} + +I didn't have enough time to learn it yet, so that's what I could do with it + +## U-He Protoverb 👍 +[U-He Protoverb](https://u-he.com/products/protoverb/) + +Protoverb is a reverb created by u-he. It has native Linux support + +Download the **Linux** version and install it by running a script. You can finfd everything [here](https://u-he.com/products/protoverb/) + +## Paulstretch 👍 + +It's already covered in the previous article. But since then, one thing is changed. You could've seen it in the very beginning of the post, that I've updated JUCE library in the source code, and now it's running as a VST plugin. If you missed it, try reading the beginning one more time. + +I'm testing it currently, but you can help me with that. + +## Bonus: Vital 👍 +[Vital](https://vital.audio/) + +I think this is the best Synth ever made. It's open source and has Linux support. I use it in every project and if you don't, I recommend you to start doing that. + +{{< video "/posts/vst-on-linux-3/vital.mp4" "video-11" >}} + +The video is laggy again, but in reality it's fine. + +--- +If you like what I'm doing, you can follow my [twitter](https://twitter.com/_allanger) or [mastodon](https://mastodon.social/@allanger), since I'll be posing there all the updates + +Thanks +Oi! diff --git a/content/search.md b/content/search.md new file mode 100644 index 0000000..39ef5f9 --- /dev/null +++ b/content/search.md @@ -0,0 +1,8 @@ +--- +title: "Search" # in any language you want +layout: "search" # is necessary +# url: "/archive" +# description: "Description for Search" +summary: "search" +placeholder: "placeholder text in search input box" +--- \ No newline at end of file diff --git a/kube/application.yaml b/kube/application.yaml index cc41ea1..aca1874 100644 --- a/kube/application.yaml +++ b/kube/application.yaml @@ -2,21 +2,51 @@ apiVersion: argoproj.io/v1alpha1 kind: Application metadata: labels: - application: badhouseplants - branch: $ARGO_APP_BRANCH - commit_sha: $ARGO_APP_IMAGE_TAG - name: badhouseplants-$ARGO_APP_BRANCH - namespace: platform + application: $APPLICATON + branch: $GIT_BRANCH + commit_sha: $GIT_COMMIT_SHA + name: $APPLICATON-$GIT_BRANCH + namespace: argo-system spec: destination: - namespace: $ARGO_APP_NAMESPACE + namespace: $APPLICATON-$GIT_BRANCH server: https://kubernetes.default.svc - project: badhouseplants + project: default source: chart: badhouseplants-net - targetRevision: $ARGO_APP_CHART_VERSION + targetRevision: $HELM_CHART_VERSION helm: valueFiles: - values.yaml - values: __DUMMY__ + values: | + namespace: + name: badhouseplants-create-wubs-in-vital + labels: + istio-injection: disabled + istio: + hosts: + - create-wubs-in-vital-dev.badhouseplants.net + annotations: + link.argocd.argoproj.io/env: https://create-wubs-in-vital-dev.badhouseplants.net/ + link.argocd.argoproj.io/remark42: https://remark42-create-wubs-in-vital-dev.badhouseplants.net/web + link.argocd.argoproj.io/build: DRONE_BUILD_LINK + hugo: + image: + tag: ee4efc6107541657f405a3dd9b7ee238d0e69e7b + baseURL: https://create-wubs-in-vital-dev.badhouseplants.net/ + buildDrafts: true + env: + HUGO_PARAMS_GITBRANCH: create-wubs-in-vital + HUGO_PARAMS_REMARK42URL: https://remark42-create-wubs-in-vital-dev.badhouseplants.net + remark42: + istio: + hosts: + - remark42-create-wubs-in-vital-dev.badhouseplants.net + settings: + url: https://remark42-create-wubs-in-vital-dev.badhouseplants.net/ + auth: + anonymous: true + secretKey: b8a41781b2c1ba2ecf49e4e7 + rclone: + command: "rclone copy -P badhouseplants-public:/badhouseplants-net/ee4efc6107541657f405a3dd9b7ee238d0e69e7b /static" repoURL: https://git.badhouseplants.net/api/packages/badhouseplants/helm diff --git a/kube/project.yaml b/kube/project.yaml deleted file mode 100644 index f302767..0000000 --- a/kube/project.yaml +++ /dev/null @@ -1,32 +0,0 @@ -apiVersion: argoproj.io/v1alpha1 -kind: AppProject -metadata: - name: badhouseplants - namespace: platform - finalizers: - - resources-finalizer.argocd.argoproj.io -spec: - description: BadHouseplants Blog - sourceRepos: - - '*' - - destinations: - - namespace: development - server: https://kubernetes.default.svc - name: in-cluster - - namespace: production - server: https://kubernetes.default.svc - name: in-cluster - - # Allow all namespaced-scoped resources to be created, except for ResourceQuota, LimitRange, NetworkPolicy - namespaceResourceBlacklist: - - group: '' - kind: ResourceQuota - - group: '' - kind: LimitRange - - group: '' - kind: NetworkPolicy - - # Enables namespace orphaned resource monitoring. - orphanedResources: - warn: false diff --git a/kube/values-main.yaml b/kube/values-main.yaml index 4d25e03..1d90eba 100644 --- a/kube/values-main.yaml +++ b/kube/values-main.yaml @@ -1,72 +1,24 @@ ---- -values: | - hugo: - image: - tag: $ARGO_APP_IMAGE_TAG - env: - HUGO_PARAMS_GITCOMMIT: $ARGO_APP_IMAGE_TAG - ingress: - enabled: true - className: ~ - annotations: - kubernetes.io/ingress.class: traefik - kubernetes.io/tls-acme: "true" - kubernetes.io/ingress.allow-http: "false" - kubernetes.io/ingress.global-static-ip-name: "" - cert-manager.io/cluster-issuer: badhouseplants-issuer-http01 - link.argocd.argoproj.io/env: https://badhouseplants.net/ - link.argocd.argoproj.io/build: $DRONE_BUILD_LINK - pathtype: ImplementationSpecific - hosts: - - host: badhouseplants.net - paths: - - path: / - pathType: ImplementationSpecific - - host: www.badhouseplants.net - paths: - - path: / - pathType: ImplementationSpecific - tls: - - secretName: badhp-tls - hosts: - - badhouseplants.net - - www.badhouseplants.net - - remark42: - settings: - secret: $ARGO_REMARK_SECRET - admin: - sharedEmail: allanger@badhouseplants.net - oauth: - github: - enabled: true - key: 1fb3d33a62b074bc0ea0 - secret: $ARGO_GITHUB_OAUTH_KEY - google: - enabled: true - key: 966815964055-m9t7leuj1arqimqu2pvbs1k10cg54gcg.apps.googleusercontent.com - secret: $ARGO_GOOGLE_OAUTH_KEY - storage: - requestedSize: 300Mi - ingress: - enabled: true - className: ~ +- value: | + hugo: + image: + tag: $ARGO_APP_IMAGE_TAG + istio: annotations: - kubernetes.io/ingress.class: traefik - kubernetes.io/tls-acme: "true" - kubernetes.io/ingress.allow-http: "false" - kubernetes.io/ingress.global-static-ip-name: "" - cert-manager.io/cluster-issuer: badhouseplants-issuer-http01 + link.argocd.argoproj.io/env: https://badhouseplants.net/ + link.argocd.argoproj.io/build: $DRONE_BUILD_LINK link.argocd.argoproj.io/remark42: https://remark42.badhouseplants.net/web - ## Hosts - hosts: - - host: remark42.badhouseplants.net - paths: - - path: / - pathType: ImplementationSpecific - - tls: - secretName: chart-example-tls - hosts: - - remark42.badhouseplants.net - \ No newline at end of file + remark42: + settings: + secret: $ARGO_REMARK_SECRET + oauth: + github: + enabled: true + key: 1fb3d33a62b074bc0ea0 + secret: $ARGO_GITHUB_OAUTH_KEY + google: + enabled: true + key: 966815964055-m9t7leuj1arqimqu2pvbs1k10cg54gcg.apps.googleusercontent.com + secret: $ARGO_GOOGLE_OAUTH_KEY + storage: + requestedSize: 300Mi + diff --git a/kube/values-preview.yaml b/kube/values-preview.yaml index c618bd8..46b774d 100644 --- a/kube/values-preview.yaml +++ b/kube/values-preview.yaml @@ -1,62 +1,32 @@ --- -values: | - ingress: - enabled: true - className: ~ - annotations: - kubernetes.io/ingress.class: traefik - kubernetes.io/tls-acme: "true" - kubernetes.io/ingress.allow-http: "false" - kubernetes.io/ingress.global-static-ip-name: "" - cert-manager.io/cluster-issuer: badhouseplants-issuer-http01 - link.argocd.argoproj.io/env: https://$ARGO_APP_HOSTNAME/ - link.argocd.argoproj.io/build: $DRONE_BUILD_LINK - pathtype: ImplementationSpecific - hosts: - - host: $ARGO_APP_HOSTNAME - paths: - - path: / - pathType: ImplementationSpecific - tls: - - secretName: badhp-$ARGO_APP_BRANCH-tls - hosts: - - $ARGO_APP_HOSTNAME - - hugo: - image: - tag: $ARGO_APP_IMAGE_TAG - baseURL: https://$ARGO_APP_HOSTNAME/ - buildDrafts: true - env: - HUGO_PARAMS_GITBRANCH: $ARGO_APP_BRANCH - HUGO_PARAMS_COMMENTS_REMARK42_HOST: https://remark42-$ARGO_APP_HOSTNAME - HUGO_PARAMS_GITCOMMIT: $ARGO_APP_IMAGE_TAG - remark42: - settings: - url: https://remark42-$ARGO_APP_HOSTNAME/ - auth: - anonymous: true - secretKey: $ARGO_REMARK_SECRET - ingress: - enabled: true - className: ~ - annotations: - kubernetes.io/ingress.class: traefik - kubernetes.io/tls-acme: "true" - kubernetes.io/ingress.allow-http: "false" - kubernetes.io/ingress.global-static-ip-name: "" - cert-manager.io/cluster-issuer: badhouseplants-issuer-http01 - link.argocd.argoproj.io/remark42: https://remark42-$ARGO_APP_HOSTNAME/ - ## Hosts +- value: | + namespace: + name: badhouseplants-$ARGO_APP_BRANCH + labels: + istio-injection: disabled + istio: hosts: - - host: remark42.badhouseplants.net - paths: - - path: / - pathType: ImplementationSpecific - - tls: - secretName: remark-$ARGO_APP_BRANCH-tls + - $ARGO_APP_HOSTNAME + annotations: + link.argocd.argoproj.io/env: https://$ARGO_APP_HOSTNAME/ + link.argocd.argoproj.io/remark42: https://remark42-$ARGO_APP_HOSTNAME/web + link.argocd.argoproj.io/build: $DRONE_BUILD_LINK + hugo: + image: + tag: $ARGO_APP_IMAGE_TAG + baseURL: https://$ARGO_APP_HOSTNAME/ + buildDrafts: true + env: + HUGO_PARAMS_GITBRANCH: $ARGO_APP_BRANCH + HUGO_PARAMS_REMARK42URL: https://remark42-$ARGO_APP_HOSTNAME + remark42: + istio: hosts: - remark42-$ARGO_APP_HOSTNAME - rclone: - command: 'rclone copy -P badhouseplants-public:/badhouseplants-net/$ARGO_APP_IMAGE_TAG /static' + settings: + url: https://remark42-$ARGO_APP_HOSTNAME/ + auth: + anonymous: true + secretKey: $ARGO_REMARK42_SECRET + rclone: + command: "rclone copy -P badhouseplants-public:/badhouseplants-net/$ARGO_APP_IMAGE_TAG /static" diff --git a/src/layouts/partials/remark42.html b/layouts/partials/comments.html similarity index 100% rename from src/layouts/partials/remark42.html rename to layouts/partials/comments.html diff --git a/src/layouts/partials/comments.html b/layouts/partials/remark42.html similarity index 87% rename from src/layouts/partials/comments.html rename to layouts/partials/remark42.html index a43970b..3404e56 100644 --- a/src/layouts/partials/comments.html +++ b/layouts/partials/remark42.html @@ -1,4 +1,7 @@
+
+

Comments are in the beta testing stage.

+