[Feature]: Staging Environments with connected database and subdomain

[GALASIO]

Problem

Instatic currently has no built-in way to run a persistent staging version of a site against separate infrastructure. Testing changes against a real database and a public subdomain (e.g. staging.domain.com) means either working directly on production or setting up a fully separate, manually maintained Instatic instance. There's no lightweight, repeatable way to spin up or sync a staging environment once the connection details are in place.

Proposed solution

Add a one-time, optional Staging Environment setup where a second database and a subdomain (e.g. staging.domain.com) can be connected. Once configured:

• A staging version can be created or refreshed with one click, similar to how SiteGround handles staging
• Staging can run in parallel to production without affecting the live site
• Ideally, syncing is granular — full database, or only selected tables, rather than an all-or-nothing push

Alternatives considered

Alternatives considered
Manually maintaining a second, fully separate Instatic instance for staging works but requires ongoing manual setup and sync, and doesn't offer one-click parallel staging or granular data control.

Area

Deployment