feat: even more github links 🥳 · trueberryless.org/blog@ded1844

+2 -2

starlight/src/content/docs/blog/accelerating-translations-with-continuous-integration.mdx

··· 8 8 - Plugins 9 9 authors: 10 10 - trueberryless 11 - excerpt: <p>I have been working in OSS on GitHub for over a year now and although I thought I found everything I want to contribute to, I recently discovered <a class="gh-badge" href="https://github.com/pelikhan"><img src="https://github.com/pelikhan.png" alt="pelikhan" width="16" height="16" style="border-radius:9999px;vertical-align:middle;margin-right:0.4em;">Peli's</a> personal project <a href="https://github.com/pelikhan/action-continuous-translation">action-continuous-translation</a> and I am very happy that I started doing regular contributions there and being part of the little community now.</p> 11 + excerpt: <p>I have been working in OSS on [GitHub](https://github.com/github) for over a year now and although I thought I found everything I want to contribute to, I recently discovered <a class="gh-badge" href="https://github.com/pelikhan"><img src="https://github.com/pelikhan.png" alt="pelikhan" width="16" height="16" style="border-radius:9999px;vertical-align:middle;margin-right:0.4em;">Peli's</a> personal project <a href="https://github.com/pelikhan/action-continuous-translation">action-continuous-translation</a> and I am very happy that I started doing regular contributions there and being part of the little community now.</p> 12 12 cover: 13 13 alt: A beautiful cover image with the text "AI Translations" 14 14 image: ../../../../public/blog/accelerating-translations-with-continuous-integration.png ··· 29 29 30 30 Fast-forward three days and I am now an official contributor to the project, making it greater and greater almost daily, mainly focusing on docs and the support for my heart project: Starlight - as you might already have guessed from [my blogs](/blog/tags/starlight/). 31 31 32 - Peli and I have our virtual productivity sessions between 4pm and 8pm UTC, extending longer on weekends. So if you want to join us as an early bird of the project or got interested in using it, feel free to check it out on GitHub: https://github.com/pelikhan/action-continuous-translation 32 + Peli and I have our virtual productivity sessions between 4pm and 8pm UTC, extending longer on weekends. So if you want to join us as an early bird of the project or got interested in using it, feel free to check it out on [GitHub](https://github.com/github): https://github.com/pelikhan/action-continuous-translation

+3 -3

starlight/src/content/docs/blog/setup-argocd-for-kubernetes.md

··· 14 14 image: ../../../../public/blog/setup-argocd-for-kubernetes.png 15 15 --- 16 16 17 - Having read Vegard S. Hagen's article “[Argo CD Kustomize with Helm](https://blog.stonegarden.dev/articles/2023/09/argocd-kustomize-with-helm/)” and decided that their solution was not the way to go for our cluster, we jumped straight into the default Argo CD “[Getting started](https://argo-cd.readthedocs.io/en/stable/getting_started/)” guide. And now we will walk you through the pain of setting up [Argo CD](https://github.com/argoproj) on [k3s](https://github.com/k3s-io) and [Cilium](https://github.com/cilium), continuing from the chapter “[Setup Certificate Manager with Cloudflare](/blog/setup-kubernetes-with-cilium-and-cloudflare#setup-certificate-manager-with-cloudflare)” of our most recent post “[Setting up Kubernetes with Cilium and Cloudflare](/blog/setup-kubernetes-with-cilium-and-cloudflare)”. In this exact recent post we also set up [Keel](https://github.com/keel-hq) at the end, but this step will now be unnecessary because we'll use Argo CD for getting the newest state-of-the-art code from each GitHub repo. Enjoy reading! 17 + Having read Vegard S. Hagen's article “[Argo CD Kustomize with Helm](https://blog.stonegarden.dev/articles/2023/09/argocd-kustomize-with-helm/)” and decided that their solution was not the way to go for our cluster, we jumped straight into the default Argo CD “[Getting started](https://argo-cd.readthedocs.io/en/stable/getting_started/)” guide. And now we will walk you through the pain of setting up [Argo CD](https://github.com/argoproj) on [k3s](https://github.com/k3s-io) and [Cilium](https://github.com/cilium), continuing from the chapter “[Setup Certificate Manager with Cloudflare](/blog/setup-kubernetes-with-cilium-and-cloudflare#setup-certificate-manager-with-cloudflare)” of our most recent post “[Setting up Kubernetes with Cilium and Cloudflare](/blog/setup-kubernetes-with-cilium-and-cloudflare)”. In this exact recent post we also set up [Keel](https://github.com/keel-hq) at the end, but this step will now be unnecessary because we'll use Argo CD for getting the newest state-of-the-art code from each [GitHub](https://github.com/github) repo. Enjoy reading! 18 18 19 19 :::note 20 20 We assume that you followed [our other blog post](/blog/setup-kubernetes-with-cilium-and-cloudflare). ··· 257 257 secretName: mutanuq 258 258 ``` 259 259 260 - These files are basically the exact same files mentioned in the [other post](/blog/setup-kubernetes-with-cilium-and-cloudflare#example-app-mutanuq) but separated into four files because this gives us the advantage to manipulate the manifest from GitHub Actions. But first things first, you'll see how to set up the manifest with GitHub actions in the [next post](/blog/setup-continuous-integration-github-repository). 260 + These files are basically the exact same files mentioned in the [other post](/blog/setup-kubernetes-with-cilium-and-cloudflare#example-app-mutanuq) but separated into four files because this gives us the advantage to manipulate the manifest from [GitHub](https://github.com/github) Actions. But first things first, you'll see how to set up the manifest with GitHub actions in the [next post](/blog/setup-continuous-integration-github-repository). 261 261 262 262 ## Create new application in Argo CD UI 263 263 ··· 294 294 295 295 ## Continuation 296 296 297 - Be continued for our [next blog](/blog/setup-continuous-integration-github-repository) which will describe how to set up a GitHub repository which can then be deployed via Argo CD. 297 + Be continued for our [next blog](/blog/setup-continuous-integration-github-repository) which will describe how to set up a [GitHub](https://github.com/github) repository which can then be deployed via Argo CD.

+2 -2

starlight/src/content/docs/blog/setup-continuous-integration-github-repository.md

··· 14 14 image: ../../../../public/blog/setup-continuous-integration-github-repository.png 15 15 --- 16 16 17 - In today's post, we'll take a quick look at how to set up continuous deployment in a GitHub repository. We're pretty sure that this setup also works for other Git registries, but if you use another, keep in mind that this post is designed for GitHub only. 17 + In today's post, we'll take a quick look at how to set up continuous deployment in a [GitHub](https://github.com/github) repository. We're pretty sure that this setup also works for other Git registries, but if you use another, keep in mind that this post is designed for GitHub only. 18 18 19 - This post also assumes that you use GitHub Actions combined with Argo CD for deploying your applications on a Kubernetes cluster. Follow other [deployment posts](/blog/tags/deployment) of us for further instructions on how to set up both technologies on your personal server. 19 + This post also assumes that you use [GitHub](https://github.com/github) Actions combined with Argo CD for deploying your applications on a Kubernetes cluster. Follow other [deployment posts](/blog/tags/deployment) of us for further instructions on how to set up both technologies on your personal server. 20 20 21 21 ## Preparations 22 22

+1 -1

starlight/src/content/docs/blog/setup-kubernetes-with-cilium-and-cloudflare.md

··· 422 422 423 423 ## Setup Keel 424 424 425 - We always wanted a clean Continuous Integration (CI) and Continuous Delivery (CD) solution for our websites. This means, that a specific commit message should trigger an automated process over GitHub, Docker Hub and our server, which in the end updates the corresponding website after about two minutes. 425 + We always wanted a clean Continuous Integration (CI) and Continuous Delivery (CD) solution for our websites. This means, that a specific commit message should trigger an automated process over [GitHub](https://github.com/github), Docker Hub and our server, which in the end updates the corresponding website after about two minutes. 426 426 427 427 Keel is a robust software tool which enables this feature for Kubernetes. We used Keel for pulling new Docker Images from Docker Hub by polling every few minutes. Moreover, Keel provides a beautiful dashboard where you can control the polling as well. 428 428

+4 -4

starlight/src/content/docs/blog/technically-impressive-github-profile-readme.mdx

··· 20 20 21 21 ## The Beginning: A README That Looked Like a Wikipedia Dump 22 22 23 - Every great story starts with a problem, and mine was simple: my GitHub profile README was a complete mess. It was long. It had too much text. It was overflowing with badges — so many that it looked like I was hoarding every possible internet trophy. Hackathons, GitHub contributions, Astro, roadmap.sh — if there was a badge, I had it. 23 + Every great story starts with a problem, and mine was simple: my [GitHub profile](https://github.com/trueberryless) README was a complete mess. It was long. It had too much text. It was overflowing with badges — so many that it looked like I was hoarding every possible internet trophy. Hackathons, GitHub contributions, Astro, roadmap.sh — if there was a badge, I had it. 24 24 25 25 At first, I thought this was fine. It showed everything about me, right? But one day, I looked at it and realized: 26 26 ··· 34 34 35 35 The first step was simple: mock up my perfect profile in HTML and CSS. And let me tell you, it looked amazing. It had the perfect layout, smooth animations, and just the right balance of content and space. Then reality hit me. This needed to work inside _GitHub-flavored Markdown_. No problem, right? Markdown supports HTML! So I copied my beautiful HTML into my README and hit save. 36 36 37 - > GitHub: *Absolutely not.* 37 + > [GitHub](https://github.com/github): *Absolutely not.* 38 38 39 39 GitHub’s Markdown [strips out a not a huge number of HTML tags, but important ones](https://github.github.com/gfm/#disallowed-raw-html-extension). Security reasons, of course (and I completely respect that, GitHub, really ❤️), but this meant my perfect design was completely **unusable**. 40 40 ··· 141 141 142 142 Isn't that bad compared to the [old README.md](https://github.com/trueberryless/trueberryless/blob/5dce4ad0033b00829f8ec3756827057017447a65/README.md). And don’t comment on why I listen to K-pop! It’s better than you think, trust me. 143 143 144 - Check out the live version on my [GitHub](https://github.com/trueberryless) — if I decided to keep it... — and leave a follow if you're already there if you enjoyed reading! ❤️ 144 + Check out the live version on my GitHub [trueberryless](https://github.com/trueberryless) — if I decided to keep it... — and leave a follow if you're already there if you enjoyed reading! ❤️ 145 145 146 146 --- 147 147 ··· 155 155 156 156 Would I recommend it? Only if you have way too much patience. 😅 157 157 158 - But in the end, I created a GitHub profile README that *shouldn’t exist* — but it does. And I love it. 158 + But in the end, I created a [GitHub](https://github.com/github) profile README that *shouldn’t exist* — but it does. And I love it.

Configure Feed

Configure Feed