# Pilot Onboarding Guide

Use this path for a first customer test of a real Drupal site on Two Small Clouds.

## Before you start

- Invite the customer user and add them to the pilot organisation.
- Set quota for the organisation with `drupal-basic` enabled.
- Confirm the customer has an OpenSSH public key available.
- Decide whether the first environment will use a custom domain now or a generated hostname first.

## Run your first site

1. Sign in to the dashboard.
2. Open Overview and follow **First real site**.
3. Register the site.
4. Add a `drupal-basic` environment.
5. Register an SSH key.
6. Open preflight checks and resolve blockers.
7. Launch the environment from Deployments.
8. Wait for the environment status to become live, then open the site URL.

## Deploy from CI

1. Create a deploy token for the environment.
2. Open CI Templates and generate the provider template.
3. Store the token as `TSC_DEPLOY_TOKEN` in the CI provider.
4. Commit the generated workflow to the customer repository.

## Backups, rollback, and refresh

- Use Tasks to run manual database and files backups.
- Use Deployments to rollback to a previous successful code release.
- Use Tasks > Refresh only for non-production targets.
- Rollback is code-only; database changes are not automatically reversed.

## Known pilot limits

- Billing and exact AWS cost reporting are not automated yet.
- The first pilot path targets `drupal-basic`; `demo` is for internal smoke tests.
- Custom-domain DNS still needs operator/customer coordination.
- Support may ask for the dashboard support summary from a failed deployment or task.