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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
content/page/homelab/index.fr.md
View File

@ -123,6 +123,7 @@ La meilleure solution que j'ai trouvée a été de percer deux trous de 40 mm a
Voici à quoi ça ressemble : Voici à quoi ça ressemble :
![Front view of my homelab with legend](img/homelab-rack-legend.png) ![Front view of my homelab with legend](img/homelab-rack-legend.png)
![Different views of my homelab with open and closed enclosure](img/homelab-enclore-open-closed.png) ![Different views of my homelab with open and closed enclosure](img/homelab-enclore-open-closed.png)
--- ---

1
content/page/homelab/index.md
View File

@ -122,6 +122,7 @@ Inside the rack, I also added two 80mm fans to help with airflow. To keep everyt
Here what is look like: Here what is look like:
![Front view of my homelab with legend](img/homelab-rack-legend.png) ![Front view of my homelab with legend](img/homelab-rack-legend.png)
![Different views of my homelab with open and closed enclosure](img/homelab-enclore-open-closed.png) ![Different views of my homelab with open and closed enclosure](img/homelab-enclore-open-closed.png)

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

@ -96,17 +96,18 @@ container:
``` ```
Le runner apparaît dans `Administration Area`, sous `Actions`>`Runners`. Pour obtenir le token d'enrôlement , on clique sur le bouton `Create new Runner` Le runner apparaît dans `Administration Area`, sous `Actions`>`Runners`. Pour obtenir le token d'enrôlement , on clique sur le bouton `Create new Runner`
![Pasted_image_20250502230954.png](img/Pasted_image_20250502230954.png) ![New runner visible in Gitea](img/gitea-runners-management.png)
### Étape 3 : Configurer les Gitea Actions pour le dépôt Obsidian ### Étape 3 : Configurer les Gitea Actions pour le dépôt Obsidian
J'ai d'abord activé les Gitea Actions. Celles-ci sont désactivées par défaut. Cochez la case `Enable Repository Actions` dans les paramètres de ce dépôt. J'ai d'abord activé les Gitea Actions. Celles-ci sont désactivées par défaut. Cochez la case `Enable Repository Actions` dans les paramètres de ce dépôt.
J'ai créé un nouveau PAT (Personal Access Token) avec autorisation RW sur les dépôts. J'ai créé un nouveau PAT (Personal Access Token) avec autorisation RW sur les dépôts.
![Pasted_image_20250501235521.png](img/Pasted_image_20250501235521.png) ![New personal access token creation in Gitea](img/gitea-new-pat.png)
J'ai ajouté le token comme secret `REPO_TOKEN` dans le dépôt. J'ai ajouté le token comme secret `REPO_TOKEN` dans le dépôt.
![Pasted_image_20250501235427.png](img/Pasted_image_20250501235427.png) ![Add secret window for repository in Gitea](img/gitea-add-repo-secret.png)
J'ai dû créer le workflow qui lancera un conteneur et effectuera les opérations suivantes : J'ai dû créer le workflow qui lancera un conteneur et effectuera les opérations suivantes :
1. Lorsque je crée/met à jour des fichiers du dossier `Blog` 1. Lorsque je crée/met à jour des fichiers du dossier `Blog`

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 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 ### 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 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 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 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: 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 1. When I push new/updated files in the `Blog` folder

2
content/post/proxmox-cloud-init-vm-template.fr.md
View File

@ -31,7 +31,7 @@ Tout d'abord, nous devons télécharger une image compatible cloud-init. Bien qu
Trouvez des images compatibles cloud dans le [Guide des images OpenStack](https://docs.openstack.org/image-guide/obtain-images.html). Trouvez des images compatibles cloud dans le [Guide des images OpenStack](https://docs.openstack.org/image-guide/obtain-images.html).
Dans Proxmox, accédez à **Storage > ISO Images > Upload** pour uploader l'image téléchargée. Dans Proxmox, accédez à **Storage > ISO Images > Upload** pour uploader l'image téléchargée.
![Pasted_image_20250131144754.png](img/Pasted_image_20250131144754.png) ![Download window for ISO images in Proxmox](img/proxmox-download-iso-img.png)
## Créer la VM ## Créer la VM
Ensuite, on crée une VM en utilisant la ligne de commande (CLI) depuis le nœud Proxmox avec la commande suivantes : Ensuite, on crée une VM en utilisant la ligne de commande (CLI) depuis le nœud Proxmox avec la commande suivantes :

3
content/post/proxmox-cloud-init-vm-template.md
View File

@ -31,7 +31,8 @@ First, we need to download an image with cloud-init support. Although Rocky Linu
Find cloud-ready images from the [OpenStack Image Guide](https://docs.openstack.org/image-guide/obtain-images.html). Find cloud-ready images from the [OpenStack Image Guide](https://docs.openstack.org/image-guide/obtain-images.html).
In Proxmox, navigate to **Storage > ISO Images > Upload** to upload the downloaded image. In Proxmox, navigate to **Storage > ISO Images > Upload** to upload the downloaded image.
![Pasted_image_20250131144754.png](img/Pasted_image_20250131144754.png) ![Download window for ISO images in Proxmox](img/proxmox-download-iso-img.png)
## Create the VM ## Create the VM
Next, we create the VM using the command line interface (CLI) from the Proxmox node with the following command: Next, we create the VM using the command line interface (CLI) from the Proxmox node with the following command:

0
static/img/Pasted_image_20250501235427.png → static/img/gitea-add-repo-secret.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 50 KiB

After

Width:  |  Height:  |  Size: 50 KiB

0
static/img/Pasted_image_20250501235521.png → static/img/gitea-new-pat.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 69 KiB

After

Width:  |  Height:  |  Size: 69 KiB

0
static/img/Pasted_image_20250502230954.png → static/img/gitea-runners-management.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 16 KiB

After

Width:  |  Height:  |  Size: 16 KiB

0
static/img/Pasted_image_20250131144754.png → static/img/proxmox-download-iso-img.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 108 KiB

After

Width:  |  Height:  |  Size: 108 KiB