Reference

CMS

Use cms when the workload is best described as Wordpress, Drupal, Editorial Site, Content Site, Agency Site. This page is generated from the provider blueprint definition and stays aligned with the supported implementation.

Current variants

Same scenario, different operating depth. Move from managed runtime toward more control and operational responsibility as the blueprint scales.

DigitalOcean

Single Droplet

Run the CMS on one Droplet with managed MySQL, VPC, firewall, DNS, and an optional bastion host.

Components

Droplet Managed Database / MySQL DigitalOcean DNS Cloud Firewall VPC

Growth boundary

Run the CMS on one Droplet with managed MySQL, VPC, firewall, DNS, and an optional bastion host.

Read variant

DigitalOcean

App Platform

Deploy the CMS on App Platform with managed MySQL for a managed, low-ops content site baseline.

Components

App Platform Managed Database / MySQL

Growth boundary

Deploy the CMS on App Platform with managed MySQL for a managed, low-ops content site baseline.

Read variant

DigitalOcean

Single Droplet

Run the CMS on one Droplet with managed MySQL, VPC, firewall, DNS, and an optional bastion host.

Components

Droplet Managed Database / MySQL DigitalOcean DNS Cloud Firewall VPC

Growth boundary

Run the CMS on one Droplet with managed MySQL, VPC, firewall, DNS, and an optional bastion host.

Read variant

DigitalOcean

App Platform

Deploy the CMS on App Platform with managed MySQL for a managed, low-ops content site baseline.

Components

App Platform Managed Database / MySQL

Growth boundary

Deploy the CMS on App Platform with managed MySQL for a managed, low-ops content site baseline.

Read variant

Not the right fit?

If this blueprint is close but not the right starting point, go back to the catalog or compare nearby paths.