Infrastructure

The DBE Media Infrastructure Stack

DBE Media runs on a controlled hosting stack built for stability, repeatability, and long-term management.

Infrastructure Stack

  • DNS and Edge: Cloudflare
  • Server Provider: DigitalOcean
  • Server Management: RunCloud
  • Web Stack: NGINX, PHP, MySQL, and WordPress
  • Database: MySQL managed through RunCloud
  • SSL: Let’s Encrypt via RunCloud
  • CDN: Cloudflare
  • Backups: Automated daily backups
  • Monitoring: RunCloud and external uptime monitoring

Core Architecture Rules

  • Each website runs as its own RunCloud web application
  • Each application has its own WordPress installation and database
  • Each application has its own database user
  • Each domain receives its own SSL certificate
  • All public domains are routed through Cloudflare
  • Origin SSL is installed before Cloudflare proxy is enabled
  • No stacked caching plugins
  • No uncontrolled plugin sprawl

How the Stack Is Structured

One backbone server. Separate applications. Controlled environments.

Server

A DigitalOcean server managed through RunCloud powers the core DBE Media environment.

Applications

Each site is deployed as its own isolated web application with a separate domain, SSL certificate, database, and database user.

Delivery

Cloudflare handles DNS, CDN delivery, edge protection, and proxy services before traffic reaches the origin server.

Standard Deployment Workflow

1. Deploy

Create a new RunCloud web application, database, and database user, then assign the domain.

2. Secure

Install the origin SSL certificate, connect Cloudflare, and confirm HTTPS redirection.

3. Stabilize

Configure backups, caching, monitoring, permissions, and baseline plugin controls.

Troubleshooting Layers

Every issue lives in one of these layers. Problems are diagnosed one layer at a time.

DNS

Domain records, nameservers, and propagation.

Cloudflare

Proxy, CDN, firewall, and SSL edge behavior.

Server

RunCloud status, firewall, routing, and application availability.

SSL

Origin certificate, HTTPS redirects, and certificate validity.

Database

Database access, credentials, permissions, and connection integrity.

WordPress

Themes, plugins, core files, configuration, and application-level failures.

Hosting Policy

Sites are approved before onboarding. Clean environments, confirmed access, and controlled expectations are required before a site is added to the stack.