Provision a new named environment
Table of Contents
When to use this skill
When the user asks to provision, create, or set up a new environment or worktree — e.g. "provision a new environment", "create a festive-hawking worktree", "set up a new dev env".
How to use this skill
- Check the genesis environment exists at
~/Development/OreStudio/ores_dev_prime_origin. If it is missing, tell the user to clone the repo there first (see the provision recipe). Provision the worktree from the current checkout:
# Auto-generated adjective-noun name: ./projects/ores.compass/compass.sh env provision # Or a specific name: ./projects/ores.compass/compass.sh env provision <adjective-noun> # Light environment (no C++ stack): ./projects/ores.compass/compass.sh env provision --type light # Provision + configure in one step (requires PGPASSWORD): ./projects/ores.compass/compass.sh env provision \ --preset linux-clang-debug-ninja -y
If
--presetwas NOT given, runenv configurein the new worktree:cd ~/Development/OreStudio/ores_dev_<name> ./projects/ores.compass/compass.sh env configure \ --preset linux-clang-debug-ninja -y
For full environments, complete setup:
./projects/ores.compass/compass.sh db recreate -y ./projects/ores.compass/compass.sh services start
Reference
- How do I manage the checkout environment with compass? —
env configure