Running a published bundle
A published bundle is a self-contained ZIP you can run on your own machine or server. It includes a compiled web UI, a small runtime, and the app's data as a local SQLite file — the person running it (the bundle operator) builds nothing: no git, no npm.
Quick start — unzip, then in that folder:
python -m pip install -r requirements.txtpython run.py— then openhttp://127.0.0.1:8000.- Different host/port:
PORT=9000 HOST=0.0.0.0 python run.py.
Who can sign in. A bundle never registers new accounts. The people who had access when you published are seeded in and sign in with the same email + password. Password reset isn't available in a bundle — use Change password after signing in.
Optional integrations. Set
GOOGLE_AUTH_CLIENT_ID to show "Sign in with Google", and GOOGLE_CLIENT_ID + GOOGLE_API_KEY for Sheets import/export — each read at runtime (no rebuild), and each requires authorizing the bundle's URL in Google Cloud Console. The account must already exist in the bundle.Data & backups. A bundle keeps its data in a local
app.db SQLite file beside run.py; attachments live in its data/ folder. Back those up to preserve records.