Skip to content

NimoApps static artifacts ​

Deployments are accepted as durable operations under /app-operations. The worker revalidates membership and uses the provider stored on the environment. Workers for Platforms deploys static assets with a manifest and hashes, uploads only the requested buckets and verifies the URL before switching the route. Pages keeps its capacity reservation for legacy environments that still use it.

The backend compiles every authorized DSL release into a reproducible bundle that can be mounted outside the Angular dashboard. The bundle includes the runtime, styles, public configuration (empty until its schema is approved), the initial document, deferred chunks and a manifest of hashes and versions.

Operations ​

MethodRouteAccessResult
POST/app-projects/:projectId/releases/:releaseId/artifactPlatform user with a live OWNER/ADMIN roleCompiles once and returns the manifest and the immutable artifact URL
GET/app-projects/:projectId/releases/:releaseId/artifactPlatform user with a live OWNER/ADMIN roleReturns the artifact generated for that release
POST/app-operationsLive OWNER/ADMIN + Idempotency-Keydeployment, hosting-migration or hosting-rollback; durable operation per tenant/environment
POST/app-environments/:id/rollbacksPlatform OWNER/ADMIN user or internal Nimo with an authorized scopeQueues restoration of a historical assignment and its configuration; reverts neither data nor payments
POST/internal/workers-for-platforms/resolveWfP dispatcher routing protocolActive, unambiguous mapping only; returns the opaque Worker ID; excluded from the public SDK
GET/app-deployments/:idDeployment UUID; OWNER/ADMIN userState of the active tenant's deployment, URL when available, and sanitized errors
GET/runtime-apps/:artifactHash/:pathPublicReturns the shell; application routes support deep reload
GET/runtime-data/:artifactHash/assets/*pathPublicStatic JS/CSS listed in the manifest; a missing asset answers 404
GET/runtime-data/:artifactHash/document/eagerRestricted runtime sessionEager document of the authorized release
GET/runtime-data/:artifactHash/versions/:version/chunks/:kind/:nameRestricted runtime sessionDeferred chunk of the authorized release

The source fingerprint (sourceHash) and the bundle fingerprint (artifactHash) are separate values. The SHA-256 manifest binds the entry point, files and the exact Node, esbuild, runtime, core, components and SDK versions. The same input and toolchain reproduce the same bytes. Secret fields block the build, and neither floating versions nor CDN dependencies are accepted.

Building and the control plane require a live tenant OWNER/ADMIN membership. The HTML and JS/CSS contain no user data or credentials; the document and chunks require a runtime session and are not stored in public caches. Deep reload serves the shell only on application routes; nonexistent resources and APIs keep their original 404/error.

Administrative operations stay within the platform and internal Nimo. They are not added to the public SDK, external MCP or the embeddable chat.

Verifiable rollback ​

Rollback takes the exact ID of a historical assignment plus the environment/configuration revisions the person reviewed. It reuses the stored artifact and checks its hashes; it does not compile again. A different entity schema or changed external connections block the operation with a reason. If the deployment completes successfully, the backend copies the historical configuration into a new revision and activates release/configuration with a revision comparison. Environment data, payments and earlier external effects stay as they are. Every request requires an idempotency key and rechecks the tenant and the live OWNER/ADMIN role.

Hosting and migration to Workers for Platforms ​

New environments use Workers for Platforms in their platform environment's shared namespace; the backend derives the User Worker identifier and persists the provider ID and hostname on the tenant-scoped environment and release. Customer scripts are not accepted. Existing Pages environments are migrated individually only through hosting-migration, which verifies the same release, the artifact hash and the WfP URL before switching the route. hosting-rollback restores the saved Pages route for that same release. Both paths preserve the configuration revision, the data namespace and the release; a failed migration changes neither the active route nor the Pages deployment.

The dispatcher's local code validates the exact suffix, resolves the host against the release active on that endpoint, compares the Worker ID and only then uses its environment's namespace; unknown or ambiguous hosts return 404 and resolver failures return 503, with no fallback to Pages or another environment. The source does not provision the wildcard route, DNS/TLS, bindings or the API origin, so storing a hostname does not prove it is publicly reachable.

Internal Nimo reads and executes that control plane with app-projects.environments.hosting.get, .migrate and .rollback. The read returns the real route and Worker/deployment, the retained previous route and a single reason per command (READY, ALREADY_ON_TARGET, NO_CURRENT_RELEASE, NO_ACTIVE_ROUTE for migrating; READY, NOT_ON_TARGET, NO_PREVIOUS_MAPPING, RELEASE_MISMATCH for reverting), without calling the provider or exposing the data namespace. Migration is offered only on an active Pages route of the current release, and reversion only while the previous route still points at that same release. Both writes accept only project, environment, release and the reviewed generation: neither the provider, nor the route, nor the Worker, nor the idempotency key are accepted from the model. They are unavailable in public widgets, the public SDK and external MCP, and require their own internal scope (nimo:application-projects:environments:hosting:read|migrate|rollback).