fuhlig/Blog
1
0
Fork 0
Code Activity

content/posts/WhatImWorkingOnCurrently.md aktualisiert

Browse Source 
Make it look better
This commit is contained in:
Florian Uhlig
2025-12-03 12:46:41 +01:00
parent 53a23ee08c
commit 5767c31162
1 changed files with 38 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files

77
content/posts/WhatImWorkingOnCurrently.md
View File

@@ -5,65 +5,64 @@ tags: ["blog"]
draft: false
---
Building a Self-Sustaining Infrastructure: A Two-Server Docker Setup
Overview
# 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 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
- **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
### 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
Isolated from the internet: No external access is permitted
## Security Through Network Segmentation
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
- 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
Zero trust model for the backup server (completely isolated from public internet)
## Automated Backup Strategy
Reduced risk of data exfiltration
Encrypted data transfer between servers
Automated Backup Strategy
Daily automated backups capture the critical components:
Database Backups
### Database Backups
All databases are exported and stored, ensuring data consistency and point-in-time recovery capabilities.
Docker Volume Backups
### Docker Volume Backups
Persistent data from Docker volumes is systematically backed up, including:
Application configuration files
User-generated content
Service-specific data stores
- 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
## 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
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.*