From 207f56128c6da3674c378d3853888052a045b08d Mon Sep 17 00:00:00 2001 From: Florian Uhlig Date: Wed, 3 Dec 2025 12:46:48 +0100 Subject: [PATCH] Rebuild --- RebuildGitScript.sh | 15 ++ public/404.html | 40 +++--- public/categories/index.html | 40 +++--- public/categories/index.xml | 8 +- public/index.html | 65 +++++---- public/index.xml | 14 +- public/page/1/index.html | 6 +- public/posts/aboutme/index.html | 42 +++--- public/posts/index.html | 65 +++++---- public/posts/index.xml | 14 +- public/posts/page/1/index.html | 6 +- .../posts/whatimworkingoncurrently/index.html | 130 ++++++++++-------- public/sitemap.xml | 16 +-- public/tags/blog/index.html | 19 ++- public/tags/blog/index.xml | 2 +- public/tags/index.html | 40 +++--- public/tags/index.xml | 8 +- 17 files changed, 285 insertions(+), 245 deletions(-) create mode 100644 RebuildGitScript.sh diff --git a/RebuildGitScript.sh b/RebuildGitScript.sh new file mode 100644 index 0000000..9bd1f26 --- /dev/null +++ b/RebuildGitScript.sh @@ -0,0 +1,15 @@ + +# Pull changes +git pull origin main + +# Rebuild the site +docker compose exec -it hugo hugo --cleanDestinationDir + +# Add +git add . + +# commit +git commit -m "Rebuild" + +# Push +git push origin main diff --git a/public/404.html b/public/404.html index 479fd65..0e6bd9e 100644 --- a/public/404.html +++ b/public/404.html @@ -1,6 +1,6 @@ - + 404 Page not found :: TechnicalBlog @@ -11,50 +11,50 @@ - + - + - + - + - + - + - + - + - + - + - + - + - + - + @@ -62,8 +62,8 @@ - - + + @@ -74,10 +74,10 @@ - + - + @@ -123,7 +123,7 @@

404 — Page not found...

- Back to home page → + Back to home page →
diff --git a/public/categories/index.html b/public/categories/index.html index bd072d8..d4690b2 100644 --- a/public/categories/index.html +++ b/public/categories/index.html @@ -1,6 +1,6 @@ - + Categories :: TechnicalBlog @@ -11,50 +11,50 @@ - + - + - + - + - + - + - + - + - + - + - + - + - + - + @@ -62,8 +62,8 @@ - - + + @@ -74,10 +74,10 @@ - + - + @@ -131,7 +131,7 @@
  • - webdev [1] + webdev [1]
    • diff --git a/public/categories/index.xml b/public/categories/index.xml index cb0799a..1412834 100644 --- a/public/categories/index.xml +++ b/public/categories/index.xml @@ -2,17 +2,17 @@ Categories on TechnicalBlog - http://localhost:1313/categories/ + https://blog.fuhlig.de/categories/ Recent content in Categories on TechnicalBlog Hugo en-us Wed, 03 Dec 2025 00:00:00 +0000 - + Webdev - http://localhost:1313/categories/webdev/ + https://blog.fuhlig.de/categories/webdev/ Wed, 03 Dec 2025 00:00:00 +0000 - http://localhost:1313/categories/webdev/ + https://blog.fuhlig.de/categories/webdev/ diff --git a/public/index.html b/public/index.html index b376c6d..11d8cff 100644 --- a/public/index.html +++ b/public/index.html @@ -1,7 +1,7 @@ - + TechnicalBlog @@ -12,50 +12,50 @@ - + - + - + - + - + - + - + - + - + - + - + - + - + - + @@ -63,8 +63,8 @@ - - + + @@ -75,10 +75,10 @@ - + - + @@ -143,7 +143,7 @@

    - About Me + About Me

    @@ -151,7 +151,7 @@ - #blog  + #blog  @@ -179,7 +179,7 @@ I mainly want to post about what I learned, what inspires me.

    - What am I currently working on + What am I currently working on

    @@ -187,7 +187,7 @@ I mainly want to post about what I learned, what inspires me.

    - #blog  + #blog  @@ -197,13 +197,18 @@ I mainly want to post about what I learned, what inspires me.

    -

    Building a Self-Sustaining Infrastructure: A Two-Server Docker Setup -Overview -Creating a resilient, self-sustaining infrastructure doesn’t require complex enterprise solutions. With two strategically configured servers and a well-thought-out backup strategy, you can achieve both reliability and security for your self-hosted applications.

    -

    The Architecture -Docker Host Server -The primary server runs all application workloads using Docker containers. This containerized approach provides:

    -

    Isolation: Each service runs in its own container with defined resources

    +

    Building a Self-Sustaining Infrastructure: A Two-Server Docker Setup

    +

    Overview

    +

    Creating a resilient, self-sustaining infrastructure doesn’t require complex enterprise solutions. With two strategically configured servers and a well-thought-out backup strategy, you can achieve both reliability and security for your self-hosted applications.

    +

    The Architecture

    +

    Docker Host Server

    +

    The primary server runs all application workloads using Docker containers. This containerized approach provides:

    +
      +
    • Isolation: Each service runs in its own container with defined resources
      • +
    • Portability: Services can be easily migrated or replicated
      • +
    • Consistency: Docker Compose configurations ensure reproducible deployments
      • +
    +

    The Docker host maintains minimal external exposure, with only essential ports opened to the internet. This reduces the attack surface while still providing necessary services.

    diff --git a/public/index.xml b/public/index.xml index 41da23e..e0027da 100644 --- a/public/index.xml +++ b/public/index.xml @@ -2,25 +2,25 @@ WelcomeToMyTechnicalBlog on TechnicalBlog - http://localhost:1313/ + https://blog.fuhlig.de/ Recent content in WelcomeToMyTechnicalBlog on TechnicalBlog Hugo en-us Wed, 03 Dec 2025 00:00:00 +0000 - + About Me - http://localhost:1313/posts/aboutme/ + https://blog.fuhlig.de/posts/aboutme/ Mon, 01 Dec 2025 00:00:00 +0000 - http://localhost:1313/posts/aboutme/ + https://blog.fuhlig.de/posts/aboutme/ <h2 id="who-am-i">Who am I</h2> <p>My name is Florian and I&rsquo;m 22 years old. I work as an IT Technican mainly with Linux Servers in Frankfurt, Germany. My company is midsized around 50 people working here. I mainly want to post about what I learned, what inspires me.</p> <p>Well I dont really, this just seemed like a great idea to waste some time.</p> What am I currently working on - http://localhost:1313/posts/whatimworkingoncurrently/ + https://blog.fuhlig.de/posts/whatimworkingoncurrently/ Wed, 03 Dec 2025 00:00:00 +0000 - http://localhost:1313/posts/whatimworkingoncurrently/ - <p>Building a Self-Sustaining Infrastructure: A Two-Server Docker Setup Overview Creating a resilient, self-sustaining infrastructure doesn&rsquo;t require complex enterprise solutions. With two strategically configured servers and a well-thought-out backup strategy, you can achieve both reliability and security for your self-hosted applications.</p> <p>The Architecture Docker Host Server The primary server runs all application workloads using Docker containers. This containerized approach provides:</p> <p>Isolation: Each service runs in its own container with defined resources</p> + https://blog.fuhlig.de/posts/whatimworkingoncurrently/ + <h1 id="building-a-self-sustaining-infrastructure-a-two-server-docker-setup">Building a Self-Sustaining Infrastructure: A Two-Server Docker Setup</h1> <h2 id="overview">Overview</h2> <p>Creating a resilient, self-sustaining infrastructure doesn&rsquo;t require complex enterprise solutions. With two strategically configured servers and a well-thought-out backup strategy, you can achieve both reliability and security for your self-hosted applications.</p> <h2 id="the-architecture">The Architecture</h2> <h3 id="docker-host-server">Docker Host Server</h3> <p>The primary server runs all application workloads using Docker containers. This containerized approach provides:</p> <ul> <li><strong>Isolation</strong>: Each service runs in its own container with defined resources</li> <li><strong>Portability</strong>: Services can be easily migrated or replicated</li> <li><strong>Consistency</strong>: Docker Compose configurations ensure reproducible deployments</li> </ul> <p>The Docker host maintains minimal external exposure, with only essential ports opened to the internet. This reduces the attack surface while still providing necessary services.</p> diff --git a/public/page/1/index.html b/public/page/1/index.html index 0e4714b..56f362b 100644 --- a/public/page/1/index.html +++ b/public/page/1/index.html @@ -1,10 +1,10 @@ - http://localhost:1313/ - + https://blog.fuhlig.de/ + - + diff --git a/public/posts/aboutme/index.html b/public/posts/aboutme/index.html index eff134d..4637858 100644 --- a/public/posts/aboutme/index.html +++ b/public/posts/aboutme/index.html @@ -1,6 +1,6 @@ - + About Me :: TechnicalBlog @@ -13,50 +13,50 @@ Well I dont really, this just seemed like a great idea to waste some time. - + - + - + - + - + - + - + - + - + - + - + - + - + - + @@ -64,8 +64,8 @@ Well I dont really, this just seemed like a great idea to waste some time. - - + + @@ -78,10 +78,10 @@ Well I dont really, this just seemed like a great idea to waste some time. - + - + @@ -127,14 +127,14 @@ Well I dont really, this just seemed like a great idea to waste some time.

    - About Me + About Me

    - #blog  + #blog  diff --git a/public/posts/index.html b/public/posts/index.html index a3dee56..edcc089 100644 --- a/public/posts/index.html +++ b/public/posts/index.html @@ -1,6 +1,6 @@ - + Posts :: TechnicalBlog @@ -11,50 +11,50 @@ - + - + - + - + - + - + - + - + - + - + - + - + - + - + @@ -62,8 +62,8 @@ - - + + @@ -74,10 +74,10 @@ - + - + @@ -126,14 +126,14 @@

    - About Me + About Me

    - #blog  + #blog  @@ -161,14 +161,14 @@ I mainly want to post about what I learned, what inspires me.

    - What am I currently working on + What am I currently working on

    - #blog  + #blog  @@ -178,13 +178,18 @@ I mainly want to post about what I learned, what inspires me.

    -

    Building a Self-Sustaining Infrastructure: A Two-Server Docker Setup -Overview -Creating a resilient, self-sustaining infrastructure doesn’t require complex enterprise solutions. With two strategically configured servers and a well-thought-out backup strategy, you can achieve both reliability and security for your self-hosted applications.

    -

    The Architecture -Docker Host Server -The primary server runs all application workloads using Docker containers. This containerized approach provides:

    -

    Isolation: Each service runs in its own container with defined resources

    +

    Building a Self-Sustaining Infrastructure: A Two-Server Docker Setup

    +

    Overview

    +

    Creating a resilient, self-sustaining infrastructure doesn’t require complex enterprise solutions. With two strategically configured servers and a well-thought-out backup strategy, you can achieve both reliability and security for your self-hosted applications.

    +

    The Architecture

    +

    Docker Host Server

    +

    The primary server runs all application workloads using Docker containers. This containerized approach provides:

    +
      +
    • Isolation: Each service runs in its own container with defined resources
      • +
    • Portability: Services can be easily migrated or replicated
      • +
    • Consistency: Docker Compose configurations ensure reproducible deployments
      • +
    +

    The Docker host maintains minimal external exposure, with only essential ports opened to the internet. This reduces the attack surface while still providing necessary services.

    diff --git a/public/posts/index.xml b/public/posts/index.xml index 080ee90..8782ce6 100644 --- a/public/posts/index.xml +++ b/public/posts/index.xml @@ -2,25 +2,25 @@ Posts on TechnicalBlog - http://localhost:1313/posts/ + https://blog.fuhlig.de/posts/ Recent content in Posts on TechnicalBlog Hugo en-us Wed, 03 Dec 2025 00:00:00 +0000 - + About Me - http://localhost:1313/posts/aboutme/ + https://blog.fuhlig.de/posts/aboutme/ Mon, 01 Dec 2025 00:00:00 +0000 - http://localhost:1313/posts/aboutme/ + https://blog.fuhlig.de/posts/aboutme/ <h2 id="who-am-i">Who am I</h2> <p>My name is Florian and I&rsquo;m 22 years old. I work as an IT Technican mainly with Linux Servers in Frankfurt, Germany. My company is midsized around 50 people working here. I mainly want to post about what I learned, what inspires me.</p> <p>Well I dont really, this just seemed like a great idea to waste some time.</p> What am I currently working on - http://localhost:1313/posts/whatimworkingoncurrently/ + https://blog.fuhlig.de/posts/whatimworkingoncurrently/ Wed, 03 Dec 2025 00:00:00 +0000 - http://localhost:1313/posts/whatimworkingoncurrently/ - <p>Building a Self-Sustaining Infrastructure: A Two-Server Docker Setup Overview Creating a resilient, self-sustaining infrastructure doesn&rsquo;t require complex enterprise solutions. With two strategically configured servers and a well-thought-out backup strategy, you can achieve both reliability and security for your self-hosted applications.</p> <p>The Architecture Docker Host Server The primary server runs all application workloads using Docker containers. This containerized approach provides:</p> <p>Isolation: Each service runs in its own container with defined resources</p> + https://blog.fuhlig.de/posts/whatimworkingoncurrently/ + <h1 id="building-a-self-sustaining-infrastructure-a-two-server-docker-setup">Building a Self-Sustaining Infrastructure: A Two-Server Docker Setup</h1> <h2 id="overview">Overview</h2> <p>Creating a resilient, self-sustaining infrastructure doesn&rsquo;t require complex enterprise solutions. With two strategically configured servers and a well-thought-out backup strategy, you can achieve both reliability and security for your self-hosted applications.</p> <h2 id="the-architecture">The Architecture</h2> <h3 id="docker-host-server">Docker Host Server</h3> <p>The primary server runs all application workloads using Docker containers. This containerized approach provides:</p> <ul> <li><strong>Isolation</strong>: Each service runs in its own container with defined resources</li> <li><strong>Portability</strong>: Services can be easily migrated or replicated</li> <li><strong>Consistency</strong>: Docker Compose configurations ensure reproducible deployments</li> </ul> <p>The Docker host maintains minimal external exposure, with only essential ports opened to the internet. This reduces the attack surface while still providing necessary services.</p> diff --git a/public/posts/page/1/index.html b/public/posts/page/1/index.html index ac9cba2..7cf7862 100644 --- a/public/posts/page/1/index.html +++ b/public/posts/page/1/index.html @@ -1,10 +1,10 @@ - http://localhost:1313/posts/ - + https://blog.fuhlig.de/posts/ + - + diff --git a/public/posts/whatimworkingoncurrently/index.html b/public/posts/whatimworkingoncurrently/index.html index ef6536b..e3a2956 100644 --- a/public/posts/whatimworkingoncurrently/index.html +++ b/public/posts/whatimworkingoncurrently/index.html @@ -1,6 +1,6 @@ - + What am I currently working on :: TechnicalBlog @@ -8,56 +8,56 @@ - + - + - + - + - + - + - + - + - + - + - + - + - + - + @@ -65,8 +65,8 @@ Isolation: Each service runs in its own container with defined resources - - + + @@ -78,12 +78,12 @@ Isolation: Each service runs in its own container with defined resources - + - + @@ -129,14 +129,14 @@ Isolation: Each service runs in its own container with defined resources

    - What am I currently working on + What am I currently working on

    - #blog  + #blog  @@ -146,45 +146,55 @@ Isolation: Each service runs in its own container with defined resources
    -

    Building a Self-Sustaining Infrastructure: A Two-Server Docker Setup -Overview -Creating a resilient, self-sustaining infrastructure doesn’t require complex enterprise solutions. With two strategically configured servers and a well-thought-out backup strategy, you can achieve both reliability and security for your self-hosted applications.

    -

    The Architecture -Docker Host Server -The primary server runs all application workloads using Docker containers. This containerized approach provides:

    -

    Isolation: Each service runs in its own container with defined resources

    -

    Portability: Services can be easily migrated or replicated

    -

    Consistency: Docker Compose configurations ensure reproducible deployments

    +

    Building a Self-Sustaining Infrastructure: A Two-Server Docker Setup#

    +

    Overview#

    +

    Creating a resilient, self-sustaining infrastructure doesn’t require complex enterprise solutions. With two strategically configured servers and a well-thought-out backup strategy, you can achieve both reliability and security for your self-hosted applications.

    +

    The Architecture#

    +

    Docker Host Server#

    +

    The primary server runs all application workloads using Docker containers. This containerized approach provides:

    +
      +
    • Isolation: Each service runs in its own container with defined resources
      • +
    • Portability: Services can be easily migrated or replicated
      • +
    • Consistency: Docker Compose configurations ensure reproducible deployments
      • +

    The Docker host maintains minimal external exposure, with only essential ports opened to the internet. This reduces the attack surface while still providing necessary services.

    -

    Backup Storage Server -The secondary server serves as a dedicated backup repository with substantial storage capacity. This server is:

    -

    Isolated from the internet: No external access is permitted

    -

    Secured via iptables: Firewall rules prevent unauthorized connections

    -

    Connected via WireGuard VPN: Encrypted tunnel ensures secure communication between servers

    -

    Security Through Network Segmentation -The WireGuard VPN creates a secure, encrypted tunnel between the Docker host and backup server. This architecture provides several benefits:

    -

    Private communication channel for backup operations

    -

    Zero trust model for the backup server (completely isolated from public internet)

    -

    Reduced risk of data exfiltration

    -

    Encrypted data transfer between servers

    -

    Automated Backup Strategy -Daily automated backups capture the critical components:

    -

    Database Backups -All databases are exported and stored, ensuring data consistency and point-in-time recovery capabilities.

    -

    Docker Volume Backups -Persistent data from Docker volumes is systematically backed up, including:

    -

    Application configuration files

    -

    User-generated content

    -

    Service-specific data stores

    +

    Backup Storage Server#

    +

    The secondary server serves as a dedicated backup repository with substantial storage capacity. This server is:

    +
      +
    • Isolated from the internet: No external access is permitted
      • +
    • Secured via iptables: Firewall rules prevent unauthorized connections
      • +
    • Connected via WireGuard VPN: Encrypted tunnel ensures secure communication between servers
      • +
    +

    Security Through Network Segmentation#

    +

    The WireGuard VPN creates a secure, encrypted tunnel between the Docker host and backup server. This architecture provides several benefits:

    +
      +
    • Private communication channel for backup operations
      • +
    • Zero trust model for the backup server (completely isolated from public internet)
      • +
    • Reduced risk of data exfiltration
      • +
    • Encrypted data transfer between servers
      • +
    +

    Automated Backup Strategy#

    +

    Daily automated backups capture the critical components:

    +

    Database Backups#

    +

    All databases are exported and stored, ensuring data consistency and point-in-time recovery capabilities.

    +

    Docker Volume Backups#

    +

    Persistent data from Docker volumes is systematically backed up, including:

    +
      +
    • Application configuration files
      • +
    • User-generated content
      • +
    • Service-specific data stores
      • +

    This comprehensive approach ensures that the entire infrastructure can be restored from backups, making the system truly self-sustaining.

    -

    Benefits of This Approach -Resilience: Hardware failure on the Docker host doesn’t result in data loss -Security: Multi-layered security with network segmentation and minimal exposure -Maintainability: Containerized services are easy to update and manage -Scalability: Additional Docker hosts can connect to the same backup server -Cost-effective: Self-hosted solution with predictable costs

    -

    Conclusion -This two-server architecture strikes an excellent balance between simplicity and robustness. By combining Docker containerization with a dedicated, secured backup server connected via WireGuard, you achieve enterprise-grade reliability without enterprise-level complexity. Daily automated backups provide peace of mind, while the security-first network design protects your data from external threats.

    +

    Benefits of This Approach#

    +

    Resilience: Hardware failure on the Docker host doesn’t result in data loss
    +Security: Multi-layered security with network segmentation and minimal exposure
    +Maintainability: Containerized services are easy to update and manage
    +Scalability: Additional Docker hosts can connect to the same backup server
    +Cost-effective: Self-hosted solution with predictable costs

    +

    Conclusion#

    +

    This two-server architecture strikes an excellent balance between simplicity and robustness. By combining Docker containerization with a dedicated, secured backup server connected via WireGuard, you achieve enterprise-grade reliability without enterprise-level complexity. Daily automated backups provide peace of mind, while the security-first network design protects your data from external threats.

    +
    +

    This setup demonstrates that effective infrastructure doesn’t require massive cloud budgets—just thoughtful design and consistent execution.

    diff --git a/public/sitemap.xml b/public/sitemap.xml index fc2fb8a..481338e 100644 --- a/public/sitemap.xml +++ b/public/sitemap.xml @@ -2,28 +2,28 @@ - http://localhost:1313/ + https://blog.fuhlig.de/ 2025-12-02T00:00:00+00:00 - http://localhost:1313/posts/aboutme/ + https://blog.fuhlig.de/posts/aboutme/ 2025-12-01T00:00:00+00:00 - http://localhost:1313/tags/blog/ + https://blog.fuhlig.de/tags/blog/ 2025-12-03T00:00:00+00:00 - http://localhost:1313/categories/ + https://blog.fuhlig.de/categories/ 2025-12-03T00:00:00+00:00 - http://localhost:1313/posts/ + https://blog.fuhlig.de/posts/ 2025-12-03T00:00:00+00:00 - http://localhost:1313/tags/ + https://blog.fuhlig.de/tags/ 2025-12-03T00:00:00+00:00 - http://localhost:1313/categories/webdev/ + https://blog.fuhlig.de/categories/webdev/ 2025-12-03T00:00:00+00:00 - http://localhost:1313/posts/whatimworkingoncurrently/ + https://blog.fuhlig.de/posts/whatimworkingoncurrently/ 2025-12-03T00:00:00+00:00 diff --git a/public/tags/blog/index.html b/public/tags/blog/index.html index 1487db3..3ce5256 100644 --- a/public/tags/blog/index.html +++ b/public/tags/blog/index.html @@ -179,13 +179,18 @@ I mainly want to post about what I learned, what inspires me.

    -

    Building a Self-Sustaining Infrastructure: A Two-Server Docker Setup -Overview -Creating a resilient, self-sustaining infrastructure doesn’t require complex enterprise solutions. With two strategically configured servers and a well-thought-out backup strategy, you can achieve both reliability and security for your self-hosted applications.

    -

    The Architecture -Docker Host Server -The primary server runs all application workloads using Docker containers. This containerized approach provides:

    -

    Isolation: Each service runs in its own container with defined resources

    +

    Building a Self-Sustaining Infrastructure: A Two-Server Docker Setup

    +

    Overview

    +

    Creating a resilient, self-sustaining infrastructure doesn’t require complex enterprise solutions. With two strategically configured servers and a well-thought-out backup strategy, you can achieve both reliability and security for your self-hosted applications.

    +

    The Architecture

    +

    Docker Host Server

    +

    The primary server runs all application workloads using Docker containers. This containerized approach provides:

    +
      +
    • Isolation: Each service runs in its own container with defined resources
      • +
    • Portability: Services can be easily migrated or replicated
      • +
    • Consistency: Docker Compose configurations ensure reproducible deployments
      • +
    +

    The Docker host maintains minimal external exposure, with only essential ports opened to the internet. This reduces the attack surface while still providing necessary services.

    diff --git a/public/tags/blog/index.xml b/public/tags/blog/index.xml index 215629c..2efa1a2 100644 --- a/public/tags/blog/index.xml +++ b/public/tags/blog/index.xml @@ -20,7 +20,7 @@ https://blog.fuhlig.de/posts/whatimworkingoncurrently/ Wed, 03 Dec 2025 00:00:00 +0000 https://blog.fuhlig.de/posts/whatimworkingoncurrently/ - <p>Building a Self-Sustaining Infrastructure: A Two-Server Docker Setup Overview Creating a resilient, self-sustaining infrastructure doesn&rsquo;t require complex enterprise solutions. With two strategically configured servers and a well-thought-out backup strategy, you can achieve both reliability and security for your self-hosted applications.</p> <p>The Architecture Docker Host Server The primary server runs all application workloads using Docker containers. This containerized approach provides:</p> <p>Isolation: Each service runs in its own container with defined resources</p> + <h1 id="building-a-self-sustaining-infrastructure-a-two-server-docker-setup">Building a Self-Sustaining Infrastructure: A Two-Server Docker Setup</h1> <h2 id="overview">Overview</h2> <p>Creating a resilient, self-sustaining infrastructure doesn&rsquo;t require complex enterprise solutions. With two strategically configured servers and a well-thought-out backup strategy, you can achieve both reliability and security for your self-hosted applications.</p> <h2 id="the-architecture">The Architecture</h2> <h3 id="docker-host-server">Docker Host Server</h3> <p>The primary server runs all application workloads using Docker containers. This containerized approach provides:</p> <ul> <li><strong>Isolation</strong>: Each service runs in its own container with defined resources</li> <li><strong>Portability</strong>: Services can be easily migrated or replicated</li> <li><strong>Consistency</strong>: Docker Compose configurations ensure reproducible deployments</li> </ul> <p>The Docker host maintains minimal external exposure, with only essential ports opened to the internet. This reduces the attack surface while still providing necessary services.</p> diff --git a/public/tags/index.html b/public/tags/index.html index 7079b1e..678999f 100644 --- a/public/tags/index.html +++ b/public/tags/index.html @@ -1,6 +1,6 @@ - + Tags :: TechnicalBlog @@ -11,50 +11,50 @@ - + - + - + - + - + - + - + - + - + - + - + - + - + - + @@ -62,8 +62,8 @@ - - + + @@ -74,10 +74,10 @@ - + - + @@ -141,7 +141,7 @@ Here you can find entry quicker thru my tags
  • - blog [2] + blog [2]
    • diff --git a/public/tags/index.xml b/public/tags/index.xml index f6daa72..5f07559 100644 --- a/public/tags/index.xml +++ b/public/tags/index.xml @@ -2,17 +2,17 @@ Tags on TechnicalBlog - http://localhost:1313/tags/ + https://blog.fuhlig.de/tags/ Recent content in Tags on TechnicalBlog Hugo en-us Wed, 03 Dec 2025 00:00:00 +0000 - + Blog - http://localhost:1313/tags/blog/ + https://blog.fuhlig.de/tags/blog/ Wed, 03 Dec 2025 00:00:00 +0000 - http://localhost:1313/tags/blog/ + https://blog.fuhlig.de/tags/blog/