Apps
Register Shell federated or standalone product apps — packaging for UI and domains, not the Coderunner deploy path.
Apps are optional product packaging in a workspace. Use them for Shell Module Federation remotes or a thin standalone product wrapper around services. Deploying runnable code uses Coderunner, not App creation.
Pillar #6· App Management✅ Live
Do not create an App solely to run a function, job, schedule, or service (D-061). Use Developers (gf deploy / MCP) or the Coderunner portal page.
App kinds
| Kind | Purpose |
|---|---|
| Shell federated | Module Federation remotes loaded in Groundfloor Shell (remoteEntry.js, releases, bootstrap) |
| Standalone | Product boundary over a primary service coderunner, shared domains, and optional helper coderunners |
One App can group many modules or helpers. Prefer one product App — not one App per module.
What you can do
- List and create apps (portal filters product kinds: Shell + Standalone)
- Configure name, slug, manifest, and repo metadata on the app detail page
- Shell publish — release upload (presigned), public by-slug bootstrap for Shell hosts
- Bind helper coderunners with
app_idwhen packaging a multi-workload product - Promote published Shell releases across environments
Shell federated flow
For register → build → publish → load in Shell:
Portal location
Sidebar → Build → Apps, or workspace detail → Apps.
Related API
GET/POST /v1/workspaces/{id}/apps- App detail, releases, and promote/compare under
/v1/workspaces/{id}/apps/… - Shell bootstrap: public by-slug endpoints (see Shell docs)
Related
- Coderunner — deploy and run workloads
- Environment Promotion
- Authentication — end-user login for Shell products