From 3d348614d2b145453549a132dac8a0a726156cfd Mon Sep 17 00:00:00 2001 From: Ryan Freeman Date: Sun, 22 Sep 2024 20:41:52 +0100 Subject: [PATCH] Update post --- app/writing/migrating-from-vercel-to-raspberry-pi-5/page.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/writing/migrating-from-vercel-to-raspberry-pi-5/page.mdx b/app/writing/migrating-from-vercel-to-raspberry-pi-5/page.mdx index 08a383c..ef13198 100644 --- a/app/writing/migrating-from-vercel-to-raspberry-pi-5/page.mdx +++ b/app/writing/migrating-from-vercel-to-raspberry-pi-5/page.mdx @@ -90,7 +90,7 @@ It was easy to set up thanks to CasaOS, and it offered all the core features I n One of my primary goals was to automate the deployment process. On Vercel, everything was automated out of the box, but I wanted to replicate that seamless workflow on the Raspberry Pi. Gitea Actions turned out to be just the tool I needed. -With Gitea Actions I could easily define my CI/CD pipelines directly within my repositories. Setting up Gitea Actions involved writing a [simple YAML configuration file](https://git.ryansnet.xyz/r-freeman/portfolio/src/branch/main/.gitea/workflows/publish.yml) that would trigger on every push to the main branch. +With Gitea Actions I could easily define my CI/CD pipelines directly within my repositories. Setting up Gitea Actions involved writing a [simple YAML configuration file](https://github.com/r-freeman/portfolio/blob/main/.gitea/workflows/publish.yml) that would trigger on every push to the main branch. ```yaml name: Build And Publish