Deploy to an isolated namespace

The problem

Publishing into an existing site root can accidentally overwrite unrelated pages.

Practical procedure

Place new static assets under a versioned directory and reject deployment when that destination already exists.

Worked scenario

A route such as /arcade-lab/20261022/ leaves /games/ and /store/ untouched until integration is verified.

Acceptance check

Assert the deployment script never writes templates, database files or Passenger configuration.

Apply the method

Use the related interactive tool to try the concept on an inspectable example. Record the starting assumptions and expected result before changing settings, then compare what the tool actually does. Where the result differs, keep the release marked experimental and document the discrepancy.

Further reading: Relevant primary technical documentation. This guide is an educational procedure, not a substitute for independent usability or compliance review.