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

Auto-update blog content from Obsidian: 2025-05-25 21:27:38
All checks were successful
Deploy / Deploy (push) Successful in 5s
Details

Browse Source
This commit is contained in:
Gitea Actions
2025-05-25 21:27:38 +00:00
parent f6c5b9279d
commit 3ae8bd84da
10 changed files with 13 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -95,17 +95,18 @@ 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](img/Pasted_image_20250502230954.png)
![New runner visible in Gitea](img/gitea-runners-management.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](img/Pasted_image_20250501235521.png)
![New personal access token creation in Gitea](img/gitea-new-pat.png)
I added this token as secret `REPO_TOKEN` in the repository
![Pasted_image_20250501235427.png](img/Pasted_image_20250501235427.png)
![Add secret window for repository in Gitea](img/gitea-add-repo-secret.png)
I needed to create the workflow that will spin-up a container and do the following:
1. When I push new/updated files in the `Blog` folder