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

Auto-update blog content from Obsidian: 2025-05-03 21:06:42
All checks were successful
Deploy / Deploy (push) Successful in 8s
Details

Browse Source
This commit is contained in:
Gitea Actions
2025-05-03 21:06:42 +00:00
parent 485fd11cbd
commit 78f1a6b8ca
5 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -82,17 +82,17 @@ container:
```
The runner appears in the `Administration Area`, under `Actions`>`Runners`. To obtain the registration token, click on the `Create new Runner` button
![[Pasted image 20250502230954.png]]
![Pasted_image_20250502230954.png](Images/Pasted_image_20250502230954.png)
### Step 3: Set up Gitea Actions for Obsidian Repository
First I enabled the Gitea Actions, this is disabled by default, tick the box `Enable Repository Actions` in the settings for that repository
I created a new PAT (Personal Access Token) with RW permission on the repositories
![[Pasted image 20250501235521.png]]
![Pasted_image_20250501235521.png](Images/Pasted_image_20250501235521.png)
I added this token as secret `REPO_TOKEN` in the repository
![[Pasted image 20250501235427.png]]
![Pasted_image_20250501235427.png](Images/Pasted_image_20250501235427.png)
I needed to create the workflow that will spin-up a container and do the following:
- When I push new/updated files in the `Blog` folder