From 72a3ec36461aa974c57fab162f845767c2028116 Mon Sep 17 00:00:00 2001 From: patchwork01 <110390516+patchwork01@users.noreply.github.com> Date: Tue, 4 Aug 2026 09:11:06 +0000 Subject: [PATCH] 7799 Move section on building environment tool to developer guide --- docs/deployment/environment-tool.md | 6 ------ docs/developer-guide.md | 2 ++ 2 files changed, 2 insertions(+), 6 deletions(-) diff --git a/docs/deployment/environment-tool.md b/docs/deployment/environment-tool.md index d60f8e162c3..0ad3ae8f30d 100644 --- a/docs/deployment/environment-tool.md +++ b/docs/deployment/environment-tool.md @@ -31,12 +31,6 @@ once in a given AWS account. Use your account number and region in the command b sleeper cdk bootstrap aws:/// ``` -### Rebuild environment - -If the environment configuration code has been changed it will need to be rebuilt before deployment. -Ensure you are working on the branch that contains the changes and execute ```scripts/cli/environment/buildWithDependencies.sh``` -Once complete you can proceed to deploying an environment. - ### Deploy/connect to an environment The Sleeper environment tool can create a machine in AWS to deploy Sleeper from (an EC2 instance) and a networking diff --git a/docs/developer-guide.md b/docs/developer-guide.md index 06dabf37caf..cce7c299307 100644 --- a/docs/developer-guide.md +++ b/docs/developer-guide.md @@ -104,6 +104,8 @@ To build the Sleeper Docker tools, you can run this script: ./scripts/cli/buildAll.sh ``` +There are also scripts to build individual tools, like `scripts/cli/environment/buildWithDependencies.sh`. + Use `./scripts/cli/runInDocker.sh` to run the built CLI. This will act the same as running the `sleeper` command after installing the CLI. You can manually install it if you copy that script somewhere, rename it to `sleeper`, and put it on the system path. Then `sleeper ...` commands will work as though you'd installed it normally.