ge-aerospace/shopdb-flask
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

distribute prebuilt channel images via GHCR instead of building on pilots

Browse Source 
Pilots behind the inspecting proxy cannot reliably build the frontend from source; npm's many small fetches get reset mid-install. Build the image once in CI on the clean runners and have pilots pull the finished channel image. One resumable image pull survives the proxy where hundreds of npm requests do not, and a pilot now needs only Docker.
This commit is contained in:
benjamin.baker
2026-09-02 09:34:40 -04:00
parent a299e751dc
commit d0e9f80287
4 changed files with 224 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
docs/DEV-BUILD-TEST.md
View File

@@ -1,19 +1,21 @@
# ShopDB dev build - quick test
Two dev builds you can stand up on a Windows box with Docker Desktop. You run
one PowerShell script: it clones the repo, checks your dependencies (offers to
winget-install anything missing), then builds and starts the stack in Docker.
one PowerShell script: it checks your dependencies (offers to winget-install
anything missing), then PULLS a prebuilt image from GHCR and starts the stack in
Docker. Nothing is compiled on your machine - no Node, no npm, no source build -
so it works on a box that has only Docker installed.
## What you need
- Windows with Docker Desktop running.
- Git for Windows (`winget install Git.Git`).
- A GitHub login for this private repo already stored on the box. If you have
cloned this repo before, or signed in to GitHub in Visual Studio or VS Code,
you already have it - the script uses that stored credential automatically, so
there is no token to paste. If you have never signed in, do one manual
`git clone https://github.com/ge-aero/shopdb-flask.git` first (it will prompt
you to sign in), then delete that clone - it is only to seed the credential.
- A GitHub login for this private repo/registry already stored on the box. If
you have cloned this repo before, or signed in to GitHub in Visual Studio or
VS Code, you already have it - the script uses that stored credential
automatically. If Docker cannot pull the image, sign in once with
`docker login ghcr.io` (use a GitHub username and a personal access token that
has `read:packages`), then re-run the launcher.
## Get the launcher
@@ -24,18 +26,20 @@ your Downloads folder) and open PowerShell in that folder.
powershell -ExecutionPolicy Bypass -File .\Start-ShopDBDev.ps1 -Channel edge
Comes up at https://localhost:5011. Red DEV badge in the sidebar.
Comes up at https://localhost:5011. Red DEV badge in the sidebar. Pulls the
`edge` image.
## Stable (main)
powershell -ExecutionPolicy Bypass -File .\Start-ShopDBDev.ps1 -Channel stable
Comes up at https://localhost:5001. No DEV badge.
Comes up at https://localhost:5001. No DEV badge. Pulls the `stable` image.
## Notes
- Both builds can run at the same time - they use different ports and separate
- Both stacks can run at the same time - they use different ports and separate
Docker volumes, so they do not collide and each keeps its own database.
- The code is cloned to `%USERPROFILE%\shopdb-dev` (override with `-TargetDir`).
- Each launch pulls the latest image for the channel, so re-running the launcher
is how you pick up a new build. No local rebuild step.
- First page load shows a self-signed cert warning (expected for a dev box).
- Stop a stack: `docker compose -p shopdb-stable down` (or `shopdb-edge`).