You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to have the ability to run CI/CD pipelines on my local, and I decided to go with [Dagger.io](https://dagger.io/). It not only fed my need and also added a lot of instresting features. In this post I'll share how I added dagger.io to my personal website.
9
+
10
+
## Requirements
11
+
12
+
My personal website is a static site generated using [Gatsby](https://www.gatsbyjs.com/). I have some scripts that I run locally to lint, build and publish the site, they are located in `scripts` directory.
13
+
14
+
I'm hosting my website on [Github Pages](https://pages.github.com/), using 3 environments: `development`, `staging` and `production`. These environments are hosted on:
I want to apply "Trunk Based Development", so whenever I push a commit to `main` branch, the site should be published to `development`. Whenever a merge request is merged to `release-<version>` branch, the site should be published to `staging`. And when I create a release(a tag), the site should be published to `production`.
Copy file name to clipboardExpand all lines: app/content/posts/personal-website/p1.mdx
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,7 @@
2
2
nanoId: ucxy00ef02qe3z4sn5vop
3
3
title: (wip) How I built my personal website (Part 1)
4
4
date: 2024-04-12
5
+
wip: true
5
6
---
6
7
7
8
In this series of posts, I'll take you through the process of how I built my own website, exploring the tools, technologies, and decisions I made along the way.
0 commit comments