replace web iex launcher with a save-and-run script

The iex (irm ...) one-liner could never work against a private repo: raw.githubusercontent.com returns 404 without a token, and a git operation's Credential Manager auth does not apply to a plain irm. The prior token-passing workaround (get.ps1, 717387f) asked pilots to paste a PAT, which they will not do and may not have.

Start-ShopDBDev.ps1 is a downloaded FILE, not a web pipe, so only its git clone/fetch need auth - and those go through Git Credential Manager using the login pilots already have from cloning this repo or signing in via Visual Studio / VS Code. No token, no paste. It takes -Channel stable|edge and hands off to dev-bootstrap.ps1. DEV-BUILD-TEST.md is rewritten for the save-and-run flow with a GCM-seeding fallback.
This commit is contained in:
benjamin.baker
2026-09-02 07:43:06 -04:00
parent 717387f665
commit 30b089bc8a
3 changed files with 109 additions and 103 deletions

View File

@@ -1,26 +1,41 @@
# ShopDB dev build - quick test
Two dev builds you can stand up on a Windows box with Docker Desktop. Each is a
single PowerShell line: it clones the repo, checks your dependencies (offers to
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.
## Stable (main)
## What you need
$env:SHOPDB_CHANNEL='stable'; iex (irm https://raw.githubusercontent.com/ge-aero/shopdb-flask/wilm/scripts/get.ps1)
- 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.
Comes up at https://localhost:5001. No DEV badge.
## Get the launcher
You will be sent `Start-ShopDBDev.ps1` directly. Save it anywhere (for example
your Downloads folder) and open PowerShell in that folder.
## Bleeding edge (dev-be)
$env:SHOPDB_CHANNEL='edge'; iex (irm https://raw.githubusercontent.com/ge-aero/shopdb-flask/wilm/scripts/get.ps1)
powershell -ExecutionPolicy Bypass -File .\Start-ShopDBDev.ps1 -Channel edge
Comes up at https://localhost:5011. Red DEV badge in the sidebar.
## Stable (main)
powershell -ExecutionPolicy Bypass -File .\Start-ShopDBDev.ps1 -Channel stable
Comes up at https://localhost:5001. No DEV badge.
## Notes
- You need Git and Docker Desktop. If Git is missing, install it first
(`winget install Git.Git`); the script handles the rest with a prompt.
- Both builds 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`).
- 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`).