Summary

After the legacy WordPress origin continued to refuse connections from RBX infrastructure, the Kulinaryos institutional website was recovered inside the RBX cluster. The solution preserves the public website experience with a static frontend replica and removes the immediate dependency on the origin machine from the primary request path.

erp.kulinaryos.com remained in its existing environment and was not changed during this intervention.

Published architecture

Traffic now follows this path:

Internet → RBX Traefik edge → Kubernetes Service → Nginx container serving static files

Traefik remains the public edge and is responsible for TLS, routing and redirecting www to the apex domain. Nginx does not replace Traefik: it runs only inside the pod to serve the replica's HTML, CSS, JavaScript, fonts and images.

The workload runs across two replicas and uses an immutable image, a non-privileged process, a read-only root filesystem, health probes, resource limits and declarative GitOps promotion through Argo CD.

What was replicated

The publication is a static copy of the visual layer produced by WordPress and Elementor. It preserves the institutional content, responsive layout and assets required for public navigation.

It is not a new WordPress installation and does not include PHP, a database, wp-admin, server-side plugins or editing capability. Features that depend on server-side WordPress processing are outside the scope of this continuity measure.

Asset and mobile fixes

In the first version, HTML and images loaded, but the website appeared unstyled on mobile devices. The cause was the way version parameters such as ?ver=... had been preserved in filenames during capture: the browser requested the path without the query string and the server returned 404 for part of the CSS and JavaScript.

The generation process was updated to normalise those names, prioritise homepage resources and fail when a required local asset is missing. The final validation covers:

  • 46 normalised query-versioned files;
  • 22 homepage stylesheets;
  • 16 initially loaded scripts;
  • 8 dynamic chunks used by WordPress and Elementor.

A second mobile-viewport test pass identified those dynamic chunks, which are required for behaviours such as the menu, carousels and expandable components. They were added explicitly to both the artifact and automated validation.

Validation

In addition to unit tests for the generator, the work included syntax checks, image construction, asset availability checks and responsive rendering validation. Inspection covered fonts, grids, cards, images and the mobile menu. The apex domain responds through the RBX edge, while the ERP remained isolated from the change.

Current state and next steps

The institutional website is available as a static continuity replica. This approach reduces the operational surface and prevents a block at the legacy origin from taking the public page offline again, but it is not a replacement for an editable WordPress environment.

Restoring full editing and dynamic capabilities will require an authorised export of the database and wp-content, or a rebuild on a platform managed by Kulinaryos. Until then, the replica will be maintained as a versioned, reproducible and monitored artifact in the RBX cluster.