pages/02.linux/dhcp-server-and-routing/default.en.md

@@ -109,7 +109,7 @@ host [HOSTNAME] {
 ### Dynamic DNS
 
 _Needs a supported DNS like BIND or PowerDNS_  
-[Configure your DNS server to accept updates](/linux/services/powerdns)  
+[Configure your DNS server to accept updates](https://wiki.realstickman.net/e/en/linux/services/powerdns)  
 Add the following snippet to your `/etc/dhcp/dhcpd.conf` file  
 How to generate the key is also described in the DNS article
 

pages/02.linux/powerdns/default.en.md

@@ -144,7 +144,7 @@ Enable for domain
 And for reverse-zone  
 `# pdnsutil set-meta (reverse ip).in-addr.arpa TSIG-ALLOW-DNSUPDATE (keyname)`
 
-You also have to configure the DHCP server to provide updates, see [the DHCP article](/linux/services/dhcp-server)
+You also have to configure the DHCP server to provide updates, see [the DHCP article](https://wiki.realstickman.net/en/linux/services/dhcp-server)
 
 ### Testing with nsupdate
 

pages/02.linux/woodpecker-ci/default.en.md

@@ -5,15 +5,10 @@ visible: true
 
 [toc]
 
-This page details installation instructions for Woodpecker CI with a connection to a self-hosted [Gitea](/linux/gitea) instance.  
-Woodpecker will be deployed as a container.
-
 ## Podman
 
 ### Network and Pod
 
-Multiple containers will be created. To separate them from other containers while also simplifying access between member containers, a container network and pod are created.
-
 ```sh
 podman network create net_woodpecker
 podman pod create --name pod_woodpecker --network net_woodpecker -p 8000:8000 -p 9000:9000
@@ -21,8 +16,6 @@ podman pod create --name pod_woodpecker --network net_woodpecker -p 8000:8000 -p
 
 #### Port Mappings
 
-Woodpecker CI uses these ports for outside communication by default.
-
 ```
 8000: Woodpecker HTTP listener, Configurable with "WOODPECKER_SERVER_ADDR"
 9000: Woodpecker gRPC listener, Configurable with "WOODPECKER_GRPC_ADDR"
@@ -30,8 +23,6 @@ Woodpecker CI uses these ports for outside communication by default.
 
 ### Database
 
-The database container is standard PostgreSQL.  
-
 ```sh
 podman run --name woodpeckerdb \
     -e PGDATA=/var/lib/postgresql/data/pgdata \
@@ -47,8 +38,6 @@ podman run --name woodpeckerdb \
 
 > [Official Documentation](https://woodpecker-ci.org/docs/administration/server-config)
 
-These options apply regardless of the Git Forge you want to use.  
-
 ```sh
 podman run --name woodpecker-server -t \
     -e WOODPECKER_HOST=https://(hostname/ip address) \
@@ -68,6 +57,10 @@ If one wanted to add a user manually: `$ woodpecker-cli user add`
 Generate `WOODPECKER_AGENT_SECRET` with this command:  
 `$ openssl rand -hex 32`
 
+#### GitHub
+
+_TODO_
+
 #### Gitea
 
 > [Documentation](https://woodpecker-ci.org/docs/administration/vcs/gitea)
@@ -82,10 +75,10 @@ Add these environment variables to enable Woodpecker for a gitea server.
     -e WOODPECKER_GITEA_SKIP_VERIFY=false \
 ```
 
-I run gitea and woodpecker behind an OPNsense firewall. The default NAT configuration is blocking the connection due to a suspected DNS rebind attack.  
+I run gitea and woodpecker behind an OPNsense firewall. The default NAT configuration alerts due to a suspected DNS rebind attack.  
-A simple workaround is adding an override rule in OPNsense under `Services > Unbound DNS > Overrides`.
+Therefor I set added an override rule for my gitea url in OPNsense (Services > Unbound DNS > Overrides)
 
-> [Helpful Reddit post](https://www.reddit.com/r/OPNsenseFirewall/comments/lrmtsz/a_potential_dns_rebind_attack/)
+> [Reddit post I used as guidance](https://www.reddit.com/r/OPNsenseFirewall/comments/lrmtsz/a_potential_dns_rebind_attack/)
 
 #### GitLab
 
@@ -102,10 +95,6 @@ Add these environment variables to enable GitLab in Woodpecker.
 
 > [Official Documentation](https://woodpecker-ci.org/docs/administration/agent-config)
 
-The Woodpecker agent must be deployed as a separate container.  
-It needs access to the docker socket to spawn new container processes on the host.  
-Podman isn't well supported currently, so I'll be using Docker for this one container instead (See below).
-
 ```sh
 docker run --name woodpecker-agent -t \
     -e WOODPECKER_SERVER=(url/ip):(grpc port) \
@@ -118,9 +107,11 @@ docker run --name woodpecker-agent -t \
     -d docker.io/woodpeckerci/woodpecker-agent:latest
 ```
 
-#### Podman Socket Notes
+The Woodpecker agent needs access to the docker socket to spawn new container processes on the host.  
+For now I'll be using docker to run my agents.
 
 Podman has support for using sockets since version 3.4.0.  
+_TODO: try out socket access once Podman 3.4.0 is on my servers_  
 _Recommended by Woodpecker is at least Podman 4.0_  
 [Podman socket activation](https://github.com/containers/podman/blob/main/docs/tutorials/socket_activation.md)