A recipe and nutrition blog celebrating healthy, natural cooking. Published by Emely Oviedo Aviles, the site covers dozens of categories — breakfasts, salads, soups, mains, desserts, and vegetarian dishes — with a philosophy rooted in simple, seasonal ingredients and culinary diversity.
The site runs on WordPress, a proven content platform that lets the author write, edit, and publish without touching code. The full stack — WordPress application and database — runs inside a Podman container on a Linux VPS, keeping the deployment self-contained and portable.
flowchart TD
classDef visitor fill:#f9f9f9,stroke:#333,stroke-width:2px;
classDef infra fill:#e1f5fe,stroke:#01579b,stroke-width:2px;
classDef runtime fill:#e8f5e9,stroke:#2e7d32,stroke-width:2px;
classDef backup fill:#fff3e0,stroke:#ef6c00,stroke-width:2px;
Visitor([Browser])
subgraph VPS [VPS — Linux]
NGINX["NGINX · TLS termination"]
subgraph Container [Podman container]
WP["WordPress"]
DB["MySQL / MariaDB"]
end
BackupCron["Scheduled backup\ncron — DB dump + uploads"]
BackupStore[("Backup storage\ncompressed archives")]
end
Visitor -->|HTTPS| NGINX
NGINX --> WP
WP --- DB
BackupCron -->|daily| DB
BackupCron -->|daily| WP
BackupCron --> BackupStore
class Visitor visitor;
class NGINX infra;
class WP,DB runtime;
class BackupCron,BackupStore backup;
NGINX handles TLS termination and reverse-proxies traffic into the container. WordPress and its database run as a single Podman pod, which makes the whole stack easy to move or restart without leaving state scattered across the host.
Automated daily backups capture both the database (a compressed SQL dump) and the uploads directory (images and media). Archives are retained on the VPS and can be restored with a single command if anything goes wrong — protecting against accidental deletion, database corruption, or migration errors.
WordPress · MySQL · Podman · NGINX · Linux VPS