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

Auto-update blog content from Obsidian: 2025-10-12 17:20:19
All checks were successful
Blog Deployment / Check-Rebuild (push) Successful in 6s
Details
Blog Deployment / Build (push) Has been skipped
Details
Blog Deployment / Merge (push) Successful in 6s
Details
Blog Deployment / Deploy-Production (push) Successful in 10s
Details
Blog Deployment / Test-Production (push) Successful in 2s
Details
Blog Deployment / Clean (push) Has been skipped
Details
Blog Deployment / Notify (push) Successful in 3s
Details
Blog Deployment / Deploy-Staging (push) Successful in 10s
Details
Blog Deployment / Test-Staging (push) Successful in 2s
Details

Browse Source
This commit is contained in:
Gitea Actions
2025-10-12 17:20:19 +00:00
parent 0644be25dc
commit 3b55a96d88
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/post/13-migration-opnsense-proxmox-highly-available.md
View File

@@ -78,4 +78,4 @@ While these routers are not managing the networks, I give them my current OPNsen
## Configure OPNsense
Initially I thought about restoring my current OPNsense config on the VM, but as I didn't documented the first time, I take the opportunity to start over.
Initially I thought about restoring my current OPNsense config on the VM. But as I didn't document the configuration process the first time, I take the opportunity to start over.