A single portable Windows .exe that runs the complete GIRP platform locally —
no Docker, no Node.js, no manual setup on the target machine. After the first
start everything runs fully offline.
On Start: launches a persistent local MongoDB, both backends (in Electron's bundled Node), and serves the frontends; seeds a demo admin user and the demo playbook on first run; then opens the frontend tabs in your browser.
Services (fixed ports): Backend-SOCView API 3000, Backend-Inputform API 4000, Frontend-Inputform 4173, Frontend-SOCView 5173, MongoDB 27017.
The portable GIRP-Launcher.exe is attached to the GitHub Releases:
https://github.com/BavariaByte/launcher/releases
Just download and double-click — no installation.
The demo credentials are intentional and shown in the launcher window:
- Email:
demo@girp.local - Password:
girp-demo
The Formbuilder (visual playbook editor) is not bundled with the Launcher. The "Formbuilder" button opens the hosted editor at https://builder.girp.bavariabyte.com in your default browser.
Building requires all sibling repos cloned side by side with these exact
lowercase directory names next to launcher/:
├── backend-socview/
├── backend-inputform/
├── frontend-socview/
├── frontend-inputform/
└── launcher/ (this repo)
Then:
cd launcher
npm install
npm run build:frontends # builds the Vue apps into resources/frontends
npm run build:backends # prod-installs backends + copies seed into resources
npm run build # electron-builder --win -> dist/GIRP-Launcher.exeNote: npm run build targets Windows, so it needs Windows (or Linux + wine).
The frontend/backend resource builds run anywhere.
The build reads its consolidated configuration from the workspace root,
i.e. ../.env relative to this repo (GIRP/.env in the layout above — note
that this is outside the launcher repo). If that file does not exist yet,
npm run build (via scripts/ensure-env.js) creates it from
launcher.env.example; an existing .env is never
overwritten. Edit GIRP/.env to configure ports, demo login, auth flags and
secrets, then rebuild.
Two kinds of variables (marked in the file):
- (Runtime) — read when the exe starts; rebuilding the exe is enough.
- (Build) — baked into the frontends; requires rebuilding them
(
npm run builddoes this automatically).
npm run build:frontends && npm run build:backends
npm startnpm test # node:test unit tests (config/env/static/seed/wait/mongo)
node scripts/e2e-smoke.js # headless full-stack smoke test (needs built resources)This project is source-available under the Sustainable Use License — see LICENSE.md.
The packaged GIRP-Launcher.exe bundles MongoDB Community Server
(mongod.exe), which is licensed under the Server Side Public License v1
(SSPL-1.0) — see THIRD-PARTY-NOTICES.md for the
component details and the full license text.
Please report security vulnerabilities to security@bavariabyte.com — see SECURITY.md. Do not open public issues for vulnerabilities.