From 0f7bde56b4bba2c427d5608e9c1731518aa2446f Mon Sep 17 00:00:00 2001 From: aramissennyeydd Date: Fri, 10 Apr 2026 15:50:22 -0400 Subject: [PATCH] address PR feedback Signed-off-by: aramissennyeydd --- docs/golden-path/deployment/001-docker.md | 25 +---------------------- 1 file changed, 1 insertion(+), 24 deletions(-) diff --git a/docs/golden-path/deployment/001-docker.md b/docs/golden-path/deployment/001-docker.md index 80549e0021..e93106ecf3 100644 --- a/docs/golden-path/deployment/001-docker.md +++ b/docs/golden-path/deployment/001-docker.md @@ -40,7 +40,7 @@ and produces better caching behavior. From the root of your repository: ```shell -yarn install --immutable +yarn install yarn tsc yarn build:backend ``` @@ -60,29 +60,6 @@ docker run -it -p 7007:7007 backstage You should see logs in your terminal and be able to open `http://localhost:7007` in your browser. -## Running the build in CI - -While you can run this build locally, you will typically run it as part of your -CI pipeline. A GitHub Actions workflow might look like this: - -```yaml -jobs: - build: - runs-on: ubuntu-latest - steps: - - uses: actions/checkout@v4 - - uses: actions/setup-node@v4 - with: - node-version: 24 - - run: yarn install --immutable - - run: yarn tsc - - run: yarn build:backend - - run: docker image build . -f packages/backend/Dockerfile --tag backstage -``` - -After building, push the image to your container registry (ECR, GCR, Docker -Hub, etc.) so that your deployment platform can pull it. - :::tip Troubleshooting If you run into build issues, two Docker flags can help: