🏗️ System

This page provides a factual architectural map of the BLLD deployment, detailing the relationship between the private WordPress authoring environment and the public static brochure.

Architectural Map

flowchart LR
    original-export --> postprocess-static-mirror.mjs
    postprocess-static-mirror.mjs --> /home/loca/dev/blld.loca.zone
    /home/loca/dev/blld.loca.zone --> https://blld.loca.zone

    WP["docker compose (WordPress)"] --> Port["127.0.0.1:54321"]
    DB[("MariaDB db_data")] -.-> WP

Source Configuration

The private WordPress environment is defined by the Docker Compose configuration located at /home/loca/dev/blld.loca.zone-private/wp-docker/docker-compose.yml.

Key facts about the configuration:

• Services: It consists of a db service running mariadb:10.6 and a wordpress service running wordpress:latest.
• WordPress State: The wordpress service mounts the local ./wp-content directory to /var/www/html/wp-content inside the container, persisting all media, themes, and plugins.
• Network Binding: The WordPress web interface is bound exclusively to the local loopback interface via port mapping 127.0.0.1:54321:80.
• Database Storage: The database securely persists its data in a local volume directory named db_data.

Output Boundary

There is a strict separation between the internal authoring system and what is accessible to the public internet.

• Public Site Artifacts: The public root (/home/loca/dev/blld.loca.zone) is strictly a static output directory. Only the generated HTML, CSS, JavaScript, and optimized media assets within this directory are served to visitors at https://blld.loca.zone.
• Private Internal Assets: The wp-docker configurations, development tools, database data (db_data), secrets, and the underlying PHP/WordPress engine are securely isolated. They are not public-site artifacts and are completely inaccessible from the outside.

Static Export Processor

The transition from the private dynamic site to the public static site is managed by a non-secret processor script located at:

/home/loca/dev/blld.loca.zone-private/tools/postprocess-static-mirror.mjs

Its precise role is to ingest the static mirror output (original-export), normalize the content (such as rewriting URLs and paths to match the production domain), and cleanly export the finalized files into the public root directory.