UTC :: --:--:-- RUST :: stable :: 1.96.0 CLIENT :: browser :: detecting PYPI :: status :: operational CLIENT :: AWS/REGION :: us-east-2 LINUX :: stable_kernel :: 7.0.10 CLOUDFLARE :: pages :: degraded_performance NODE :: lts :: 24.16.0 CLIENT :: os :: detecting CRATES.IO :: crates :: 275k+ GITHUB :: actions :: operational CLIENT :: ip :: masked PYTHON :: stable :: 3.14.x UTC :: --:--:-- RUST :: stable :: 1.96.0 CLIENT :: browser :: detecting PYPI :: status :: operational CLIENT :: AWS/REGION :: us-east-2 LINUX :: stable_kernel :: 7.0.10 CLOUDFLARE :: pages :: degraded_performance NODE :: lts :: 24.16.0 CLIENT :: os :: detecting CRATES.IO :: crates :: 275k+ GITHUB :: actions :: operational CLIENT :: ip :: masked PYTHON :: stable :: 3.14.x
docs::litlaunch :: Integration
~/docs/litlaunch/docs/integration.md

Integration

LitLaunch Docs

./view_on_github
repo
Lattice-Foundry/LitLaunch
path
docs/integration.md
ver
1.0.0rc6
commit
cf08bca4c4
synced
May 29, 2026, 03:35 AM UTC

LitLaunch is designed to sit underneath real Streamlit application workflows: source checkouts, packaged app launchers, internal dashboards, and local-first desktop-style tools. Integration should keep LitLaunch focused on runtime ownership while the downstream application owns product policy, packaging, and user-facing support decisions.

Core Integration Shape

  • Build a LauncherConfig or profile from app-specific settings.
  • Let LitLaunch own backend process startup, health checks, browser launch, graceful shutdown, diagnostics, and reports.
  • Register app cleanup through LitLaunch shutdown hooks when needed.
  • Keep packaging, installer creation, auth, reverse proxies, and app-specific resource discovery outside LitLaunch.

Notes

  • RoleThread Lite describes a concrete product-app integration shape.
  • Packaging Notes describes the runtime seams packaged apps can use without treating LitLaunch as a packaging framework.