Repository navigation
Edge GEX Lab v1.0.1
The Windows install now finishes on a PC with Smart App Control on, and a first run without keys opens on a map that works.
Not financial advice. Not a signal service. Every screenshot is synthetic demo data.
A clean first run on Windows
On Windows 11 with Smart App Control on, setup.bat stopped at the web build: Windows blocked a
native file that the build tool ships ("An Application Control policy has blocked this file"). The
build now uses the WebAssembly version of that tool, so there is nothing for Windows to block.
A new install with no Alpaca keys used to open on SPY and show "Can't load the SPY map". It now
opens on SPX, which needs no keys. Open SPY without keys and the message says exactly which two keys
to put in .env.
Fixed
- Web build blocked by Smart App Control. If
setup.batfailed for you at step 4, run it again
with this release. If you build by hand, deleteweb\node_modulesfirst:npm installon top of
the old folder keeps the blocked file,npm ci(whatsetup.batruns) replaces it. - Keyless first run landed on a map it could not load. It now opens on SPX.
- The SPY error pointed at a setting the README never mentioned. It now names
.env, and that
setting (ALPACA_ENV_FILE) is documented. - No usable quotes read as a neutral map. A chain with no usable quotes is now shown as
unavailable, and an older Cboe file never replaces a newer cached one.
Also
- Demo mode is in the Quick start:
launch.bat demoserves synthetic fixtures with no keys and no
network, badged on every screen, and leaves your real install empty. GEXLAB_PORTchanges the port (8240 by default) forlaunch.bat, the web dev server and the
"API offline" messages.GEXLAB_NO_BROWSER=1stopslaunch.batfrom opening your browser.- Code comments no longer carry internal notes or pointers to files outside this repo.
- A test for the missing keys message.
Install
Download the zip below, unzip it, run setup.bat, then launch.bat. Needs Python 3.11 or newer and
Node.js LTS. Free Alpaca API keys are needed for SPY, QQQ and stocks; SPX and NDX work without them,
and launch.bat demo works with no keys at all. A new install starts empty.
Upgrading
Your keys (.env) and caches (data/) are not part of a release, so updating never touches them.
If you cloned with git: git pull, then setup.bat (the build tool changed, so run it this
time), then launch.bat.
If you downloaded the ZIP: unzip this one into a new folder, copy your .env across, run
setup.bat once, then start it with launch.bat.
old-folder/.env -> new-folder/.env