workie

To set up isolated PostgreSQL databases for each git worktree in Phoenix, you use the workie bootstrap process. It automatically generates per-worktree `.branch` identifiers and configures branch-specific `APP_NAME_<branch_id>_dev` and `_test` databases to prevent data contamination across parallel features.

Workie supports detecting environment variables with Dotenvy, .env scripts, or System.get_env for Phoenix worktrees. It automatically wires the project's environment-loading strategy during the bootstrap process to ensure each isolated worktree operates with the correct database configuration.

To safely tear down a git worktree and its associated branch database, the system performs safety checks for uncommitted changes and unpushed commits before finishing. It includes optional PR awareness and executes database cleanup scripts to remove the branch-specific PostgreSQL state securely.

Branch-isolated databases for parallel feature development in PostgreSQL eliminate the risk of running multiple feature branches against a single shared database. This isolation reduces test and data contamination between branches, ensuring clean, repeatable environments for every worktree.

You need an environment bootstrap strategy like workie to run parallel Phoenix feature branches effectively. It bootstraps a `.workie.yaml` configuration, integrates your environment-loading strategy, and generates database setup scripts to ensure consistent, isolated dev and test PostgreSQL state across all worktrees.