Skip to content

Formalize Valet clone-lab as an optional recipe (macOS-only) with clear guardrails and no core-toolset promotion #28

Description

@noelsaw1

Define scope and success criteria for Valet clone-lab (what problem it solves, who it’s for, what is explicitly out of scope)
Document macOS-only prerequisites and environment checks (Valet, PHP, DNS/hosts assumptions, permissions, required commands)
Add safety guardrails and usage boundaries (non-production warning, data-handling constraints, destructive-action safeguards, temp-only artifacts)
Standardize the workflow steps and flags (clone flow, config options, expected inputs/outputs, failure handling)
Validate on 2-3 real projects and capture edge cases (timing, portability, local setup variance, rollback/recovery notes)
Publish as optional documentation only (recipe + references), with explicit language that it is experimental and not part of the core/default toolset

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions