package-once-red

ONCE with Red

Use the bundled red launcher in the deployment directory. It runs with Bun and resolves immutable package dependencies. Read configuration.md before changing desired state. Read github-deploy.md when adding continuous deployment to an application's repository.

The package calls colors-compute for one host. The library owns provider selection, credentials, remote state and SSH key lifecycle. Update its dependency to obtain provider support; do not add a compute template or provider branch to this package. ONCE owns application configuration, SMTP, DNS and GitHub publishing.

Keep secrets in COLORS_PAR_* environment variables. Ask for variable names and whether they are set, never their values. Do not read .envrc.private or private keys. Never read generated .colors/ as source or edit it. Use one color at a time for a deployment.

For initialization, preserve existing desired state and unrelated files. Copy the bundled launcher, make it executable, and create or revise colors.yml with non-secret settings. Ignore generated output and private environment files. Validate with ./red build and ./red create --dry-run. These commands contact no provider and do not prove credentials or live health.

A real create or delete needs user authorization. Existing authorization for the task applies; do not ask again. Create validates, converges compute, then SMTP, DNS, verification and application configuration. Compute ownership failure stops subsequent resource creation. Delete loads recorded compute inventory, withdraws published credentials and SSH configuration, removes DNS and SMTP, then destroys compute. The library removes its SSH key after successful destroy. Keep compute-prevent-destroy: true in desired state; an authorized delete can use COLORS_PAR_COMPUTE_PREVENT_DESTROY=false for that invocation.

Existing monolithic compute state requires an explicit reviewed migration. Do not run a new create against it to discover what happens. Missing, unreadable or inconsistent state is a refusal, not permission to recreate resources. A failed operation retains state needed for inspection and retry.

Use ./red describe for recorded compute status and application inspection. It reads compute through the library and requires a verified address before SSH. For an application naming a GitHub repository, establish whether continuous deployment is part of the user's request before adding its workflow. Confirm the target repository matches owner/repo; the deployment repository may be a different checkout. Follow the linked reference for the exact published values.

Create and build serialize the package-owned SSH alias stage before remote Ansible. A failed local ownership check stops application convergence; GitHub publication remains after remote convergence.