Reference
Web app / Single Droplet
Run the web app on one Droplet with DNS, firewall, and reserved IP for a straightforward host-based setup.
Overview
Variant overview
Run the web app on one Droplet with DNS, firewall, and reserved IP for a straightforward host-based setup.
Manifest file
Edit web-app-vm.environment.yaml to change the scenario.
Rendered output
OPSd renders the manifest into OpenTofu under rendered/web-app-vm.
Supported changes
The variant defines which add, remove, and scale operations are supported.
Good fit
you want a simple VM-based starting point; host-level access matters; the team is comfortable owning more operating detail directly
Tradeoff
More operating responsibility sits with the team from the start.
What gets created for this setup
This diagram shows the result you get after rendering the selected variant.
Infrastructure shape
Before you start
Shared setup is covered in Installation and the Introduction. This section lists the minimum things you need before the first render for DigitalOcean.
- Installation install the shared OPSd CLI.
- Introduction understand the workflow boundary and required toolchain.
- Have a container image or build artifact ready.
Initialize this variant
This is the first-run path when no scenario has been initialized yet.
Initialization sequence
opsd list blueprints
opsd init blueprint web-app web-app-vm.environment.yaml --variant vm
opsd validate manifest web-app-vm.environment.yaml
opsd render manifest web-app-vm.environment.yaml --output rendered/web-app-vm
cd rendered/web-app-vm
tofu init
tofu plan
# review the rendered output before planning
cd rendered/web-app-vm
tofu init
tofu plan Edit the manifest
After the first deployment, the supported path is still manifest first. Use the supported opsd add, remove, and scale commands for this variant, then validate and render again.
Supported change commands
Keep the initial shape
Make only supported manifest changes for this variant.
opsd validate manifest web-app-vm.environment.yaml Edit, validate, render
# edit web-app-vm.environment.yaml
# validate the config before rendering
opsd validate manifest web-app-vm.environment.yaml
# render the updated output and review it
opsd render manifest web-app-vm.environment.yaml --output rendered/web-app-vm
cd rendered/web-app-vm
# plan and apply only after the diff is clear
tofu plan
tofu apply Supported changes
These examples come from the variant capability map and show the supported add, remove, and scale operations for this setup.
Keep the initial shape
Make only supported manifest changes for this variant.
opsd validate manifest web-app-vm.environment.yaml Changes are not active yet
Editing the manifest changes the desired state. To make it real, validate the manifest, render the updated output, and then run `tofu apply` against the rendered directory.
opsd validate manifest web-app-vm.environment.yaml
opsd render manifest web-app-vm.environment.yaml --output rendered/web-app-vm
cd rendered/web-app-vm
tofu plan
tofu apply Related variants
Use the scenario overview to compare the other supported variants for the same blueprint.