Since a Lair's development environment has a single file system representation, supporting multiple developers working in the same repo simultaneously requires provisioning multiple Lairs.

Allocating Lairs for a Development Project

When working with an external VCS, we recommend one Lair designated to only the 'main' branch, and one additional Lair per developer. The 'main' Lair is used to serve your 'customers' and should be deployed with the latest in the 'main' branch. Other lairs should be used for development only. Deploying to these lairs would be analogous to deploying to a test environment.
To keep lairs organized, use naming conventions for such as{repo_name}-{dev_name}, and/or add tags to your lairs.


For a developer developing in a feature branch locally, life should feel the same as it always did. As a developer you will make and commit changes as you normally do. Then, whenever you need the power of WayScript to help test your code, simply spin up the Desktop App and open your development lair (or keep it open) to sync your local changes to the hosted Lair environment.


When a feature branch is ready to be merged to the main branch, use your normal workflow to make it so. Normally this involves opening a pull request, seeking reviews, running tests, etc. Once the main branch is updated, and you're ready to use WayScript to ship your new code to your customers, you will:
  1. 1.
    Ensure your local directory reflects the latest code in the main branch
  2. 2.
    Open your production Lair used for this repo
  3. 3.
    Connect your lair to the local directory containing your latest code
  4. 4.
    Wait for updates to finish syncing to your Lair development environment
  5. 5.
    Inspect your Lair development environment and ensure changes are correct.
  6. 6.
    Deploy your lair to production.