Laravel Forge or Ploi

Forge and Ploi users have a reproducible server, which is the hard part. What is missing is a way for the panel to learn about servers it did not create; until the native adapter exists, the snapshot path works but keeps the panel out of the loop.

Prerequisite work: native adapter not in MVP
Time to set up: half day
Adapter: Snapshot today; native adapter later
Fit: 4 → 8/104 with the snapshot path, 8 once the native adapter exists

Prerequisites, time and fit are the ADR-0028 row for this case. Hetscale's own setup is about 15 minutes in every case; the rest is work on your side.

Steps

01
Move state and TLS off the server
Managed database, external sessions and uploads; TLS terminated at a Hetzner load balancer rather than by the panel’s per-server certificates.
02
Provision one server fully through the panel
That server becomes the seed. Hetscale snapshots it as release v1; new nodes boot from the snapshot with your restart policies bringing the app up.
03
Accept that the panel does not see the nodes
Nodes created from a snapshot are not registered in Forge or Ploi. Deploys go to the seed, followed by a new snapshot and a rolling replace. This is why the fit is 4 today.
04
Observe, rehearse, go Live
Read-only trial first, one Rehearsal, then Live with minimum 2.

FAQ for this case

When does the native adapter come?

After the MVP adapters (snapshot, webhook, Coolify), in the order Observe data justifies. With it, nodes are registered with the panel and the fit rises to 8.