Vezpi/Blog
1
0
Fork 0
Code Issues Pull Requests Actions Wiki Activity

Auto-update blog content from Obsidian: 2025-05-04 18:44:20

Browse Source
This commit is contained in:
Gitea Actions 2025-05-04 18:44:20 +00:00
parent 6dc83bf42f
commit be6e2015be
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
content/posts/blog-deployment.md
View File

@ -10,6 +10,7 @@ I'm constantly tinkering in my homelab, trying new tools and workflows. Instead
I wanted the entire process to be automated, self-hosted, and integrated into the tools I already use. I wanted the entire process to be automated, self-hosted, and integrated into the tools I already use.
---
## 🔧 Tools ## 🔧 Tools
### Obsidian ### Obsidian
@ -34,13 +35,13 @@ To run those workflows, I installed a [Gitea runner](https://gitea.com/gitea/act
## 🔁 Workflow ## 🔁 Workflow
The idea is simple: The idea is simple:
1. I write blog content in my Obsidian vault, under a specific `Blog` folder. 1. I write blog content in my Obsidian vault, under a specific `Blog` folder.
2. When I push updates to that folder, a first Gitea Action is triggered. 2. When I'm done editing the file, the Obisdian Git plugin automatically commits and push updates to the Gitea repository
3. The first action syncs the updated blog content to a separate [blog repository](https://git.vezpi.me/Vezpi/blog). 3. When Gitea receives that push, a first Gitea Action is triggered.
4. In the blog repository, another Gitea Action is triggered. 4. The first action syncs the updated blog content to another separate [Git repository](https://git.vezpi.me/Vezpi/blog) which hosts my blog content.
5. The second Gitea Action generates the static web pages while upgrading Hugo if needed 5. In that blog repository, another Gitea Action is triggered.
6. The blog is now updated (the one you are reading). 6. The second Gitea Action generates the static web pages while upgrading Hugo if needed
7. The blog is now updated (the one you are reading).
This way, I never need to manually copy files or trigger deployments. Everything flows from writing markdown in Obsidian to having a fully deployed website. This way, I never need to manually copy files or trigger deployments. Everything flows from writing markdown in Obsidian to having a fully deployed website.