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

Auto-update blog content from Obsidian: 2025-05-05 12:52:04
All checks were successful
Deploy / Deploy (push) Successful in 7s
Details

Browse Source
This commit is contained in:
Gitea Actions 2025-05-05 12:52:04 +00:00
parent 7a8a7f406f
commit 5087515564
2 changed files with 13 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -3,6 +3,10 @@ title: Blog Deployment featuring Obsidian, Hugo and Gitea Actions
date: 2025-05-02 date: 2025-05-02
draft: true draft: true
tags: tags:
- obsidian
- hugo
- gitea
category: homelab
--- ---
I always wanted to share my own experiences to give others ideas or help them on their projects. I always wanted to share my own experiences to give others ideas or help them on their projects.
@ -32,6 +36,7 @@ To run those workflows, I installed a [Gitea runner](https://gitea.com/gitea/act
[Hugo](https://gohugo.io/) is a fast and flexible static site generator written in Go. It’s perfect for generating content from Markdown files. Hugo is highly customizable, supports themes, and can generate a complete website in seconds. It’s ideal for a blog based on Obsidian notes, and it works beautifully in CI/CD pipelines due to its speed and simplicity. [Hugo](https://gohugo.io/) is a fast and flexible static site generator written in Go. It’s perfect for generating content from Markdown files. Hugo is highly customizable, supports themes, and can generate a complete website in seconds. It’s ideal for a blog based on Obsidian notes, and it works beautifully in CI/CD pipelines due to its speed and simplicity.
---
## 🔁 Workflow ## 🔁 Workflow
The idea is simple: The idea is simple:
@ -45,6 +50,7 @@ The idea is simple:
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.
---
## ⚙️ Implementation ## ⚙️ Implementation
### Step 1: Obsidian Vault Setup ### Step 1: Obsidian Vault Setup
@ -211,6 +217,7 @@ jobs:
``` ```
---
## 🚀 Results ## 🚀 Results
This workflow allows me to focus on what matters most: writing and refining my content. By automating the publishing pipeline — from syncing my Obsidian notes to building the blog with Hugo — I no longer need to worry about manually managing content in a CMS. Every note I draft can evolve naturally into a clear, structured article, and the technical workflow fades into the background. It’s a simple yet powerful way to turn personal knowledge into shareable documentation. This workflow allows me to focus on what matters most: writing and refining my content. By automating the publishing pipeline — from syncing my Obsidian notes to building the blog with Hugo — I no longer need to worry about manually managing content in a CMS. Every note I draft can evolve naturally into a clear, structured article, and the technical workflow fades into the background. It’s a simple yet powerful way to turn personal knowledge into shareable documentation.

8
content/posts/my-first-post.md
View File

@ -1,8 +1,12 @@
--- ---
title: "Welcome to My Homelab Blog" title: Welcome to My Homelab Blog
date: 2025-04-25 date: 2025-04-25
draft: false draft: false
tags: ["homelab", "infrastructure", "docker"] tags:
- homelab
- infrastructure
- docker
- t
--- ---
# 🏡 Welcome to My Homelab # 🏡 Welcome to My Homelab