Docker on Ponfertato

Docker Configuration Evolution: From Scattered Containers to Managed Stacks

Mon, 01 Jan 0001 00:00:00 +0000

Previously, each service lived in a separate repository with minimal docker-compose.yml:

# Old approach: garrysmod-server/
services:
 garrysmod-server:
 image: ceifa/garrysmod:latest
 ports:
 - "27015:27015"
 volumes:
 - ./garrysmod:/data
 restart: unless-stopped

Problems:

❌ No resource control - one service could consume all memory
❌ No health checks - crashed services went undetected
❌ No log rotation - logs grew until disk full
❌ No network isolation - all services in default network
❌ Manual per-service updates - high risk of human error

New Approach: Stacks with Explicit Contracts
#

Now related services are grouped into a single repository with unified configuration:

Hugo: Static Site Architecture & CI/CD

Mon, 01 Jan 0001 00:00:00 +0000

Using Hugo for static site generation delivers maximum performance with minimal overhead. All projects in the *.potatoenergy.ru stack share a unified methodology for configuration, building, and deployment.

Core principles:

🔹 Declarative configuration via hugo.toml and config/_default/
🔹 Multilingual support via translationKey without logic duplication
🔹 Parameter inheritance via cascade in front matter
🔹 Asset optimization via Hugo Pipes (minification, fallbacks, hashing)
🔹 Build environment isolation via Docker

🗂 Project structure
#

project/
├── config/_default/
│ ├── hugo.toml # Base settings: baseURL, theme, outputs
│ ├── params.toml # Global theme params and custom variables
│ ├── menus.toml # Navigation configuration
│ └── languages.*.toml # Localization: displayName, copyright, author
├── content/
│ ├── {section}/
│ │ ├── _index.{ru,en}.md # Listing page with section description
│ │ └── {slug}/
│ │ ├── index.{ru,en}.md # Content with translation via translationKey
│ │ └── assets/ # Page-bundled resources
│ └── _index.{ru,en}.md # Homepage
├── layouts/
│ ├── _default/ # Default templates: single.html, list.html
│ ├── partials/ # Reusable components: head, footer, svg
│ ├── shortcodes/ # Custom shortcodes: audio, toggle, icon
│ └── shortcodes/ # Theme template overrides (if needed)
├── static/ # Files copied as-is: robots.txt, favicons
├── assets/ # Hugo Pipes sources: CSS/JS for processing
└── docker-compose.yml # Local development environment

🌐 Multilingual without duplication
#

Translation linking is handled via translationKey in front matter:

Many Projects. One Structure. No Chaos.

Mon, 01 Jan 0001 00:00:00 +0000

When you have more than ten projects, questions arise:

Where is the config for this service?
Which environment variable to set on deploy?
Why does one container consume all memory while another stays silent on crash?
How to quickly deploy all this on a new machine?

Answer: unified structure, unified rules, unified approach.

🗂 Unified Repository Structure
#

Every active project follows one template:

Source Servers on ARM64: Docker Images for Games

Mon, 01 Jan 0001 00:00:00 +0000

A series of Docker images for running Source Engine servers on ARM64 architectures (Orange Pi, Raspberry Pi 4/5, AWS Graviton).

Repository	Game	Tags	Image Size
garrysmod-docker	Garry’s Mod	`latest`	~2.1 GB
tf2-docker	Team Fortress 2	`latest`	~1.8 GB
css-docker	Counter-Strike: Source	`latest`	~1.6 GB
l4d2-docker	Left 4 Dead 2	`latest`	~2.3 GB
hl2dm-docker	Half-Life 2: Deathmatch	`latest`	~1.5 GB
dods-docker	Day of Defeat: Source	`latest`	~1.6 GB
l4d-docker	Left 4 Dead	`latest`	~2.0 GB

All images share a unified build and configuration architecture.

Docker on Ponfertato

Docker Configuration Evolution: From Scattered Containers to Managed Stacks

New Approach: Stacks with Explicit Contracts #

Hugo: Static Site Architecture & CI/CD

🗂 Project structure #

🌐 Multilingual without duplication #

Many Projects. One Structure. No Chaos.

🗂 Unified Repository Structure #

Source Servers on ARM64: Docker Images for Games

New Approach: Stacks with Explicit Contracts
#

🗂 Project structure
#

🌐 Multilingual without duplication
#

🗂 Unified Repository Structure
#