30b089bc8a
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.
1.7 KiB
1.7 KiB
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.
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.gitfirst (it will prompt you to sign in), then delete that clone - it is only to seed the credential.
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)
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
- 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(orshopdb-edge).