App Hosting
Goal: Know what App Hosting does today, and how to turn it on with its first hosting plan.
Cloud -> App Hosting (under Foundation) is somewhere for your workspace to run its own containers: a shared container registry and named hosting plans, in your own landing zone and your own Azure subscription.
This window opens as a panel: it floats at the right at first, docks anywhere, and keeps your place when you move it. See Node editors and work windows as panels.
This is a preview. The item is in the menu only when the workspace has a connected cloud and its landing zone, and
you hold the Workspace.Experimental right. It stays gated until App Hosting makes its resources in Azure end to
end; the gate lifts in a later release.
What it creates in your cloud
Turning App Hosting on sets up, in your landing zone's resource group:
- One shared registry. Your images live in your landing zone's container registry. It has no admin user and is never given a password or a token; each app publishes with its own identity.
- Hosting plans. Each plan is a machine your apps share. You name it by what runs on it (for example
OpenX runtimes), not by its size, and you pick its size: small, medium or large. Every app on a plan shares its size.
Hosted Apps are dropped on a surface, and you pick their plan in the Inspector. The words are always "hosting plan", never "environment".
The rights you need
| To do this | You need |
|---|---|
| Open the window and read App Hosting and its hosting plans | Workspace.AppHosting.Read or Workspace.AppHosting.Manage |
| Turn it on, and add, size or remove hosting plans | Workspace.AppHosting.Manage |
Workspace owners hold both through their main cards; anyone else needs an access configuration that confers them. No right implies another.
What the window shows
The window is titled App Hosting. Its status pill reads Not turned on, Waits for Deploy, Ready or Needs attention.
- Before it is turned on: "App Hosting is not turned on yet. Turn it on here to run your own containers in your landing zone."
- After you save it but before the commit runs: "App Hosting is saved. Its registry and plans are made when the commit runs."
- Once the registry exists: "The shared registry is ready. Hosted Apps run on the plans below." and the registry's address, Shared registry: ...
A strip explains how it works: One shared registry, Named hosting plans, Hosted Apps on a surface.
Turn it on
- Open Cloud -> App Hosting.
- Name your first hosting plan and pick its size.
- Press Turn on App Hosting.
- Run the window's commit. This is what makes the registry and the plan in Azure.
Saving alone makes nothing. The registry's address appears once Deploy has made it.
Add, size and remove plans
- Add a hosting plan: the Add a hosting plan tab, a unique Plan name, a size, then Add hosting plan.
- Change a size: open the plan's tab and press Save plan. When apps run on the plan, a note says the change applies to every app on it, on the next Deploy.
- Remove a plan: Remove plan on its tab stages the removal. A plan reads Waits for Deploy, Made or Removal staged. Its tab lists the Hosted Apps on it.
What an AI can do with it
An agent proposes App Hosting with its first plan in one bundle, and a person accepts it in this window with Accept Proposal and Turn On (or Accept Proposal and Add Plan for a later plan). Accepting records the proposal and starts the commit; accepting alone makes nothing in Azure. Never read a green "accepted" as "App Hosting is ready": read the workspace and look for the registry's address.
An agent proposes only a name and a description. The registry, its region and its login server are written by
Deploy, and a proposal that includes them is refused with APP_HOSTING_ACTUATOR_FIELD.
Limits and troubleshooting
- App Hosting is missing from the menu: the workspace has no connected cloud or no landing zone yet (see
Landing Zone), or you do not hold
Workspace.Experimental. - Removing App Hosting is not built. It is refused with
KIND_TEARDOWN_UNSUPPORTED; the registry and plans stay until real teardown lands. Removing it later would also remove every plan and every Hosted App's site. - A proposal is refused: the refusal codes are
APP_HOSTING_ACTUATOR_FIELD,APP_HOSTING_CONFIGURATION_FIELD(the registry settings OpenX fixes),APP_HOSTING_UNKNOWN_FIELD,SECRET_IN_PROPOSAL(App Hosting carries no credential),KIND_TEARDOWN_UNSUPPORTEDandUNKNOWN_ROOT_KEY. Each message says what to leave out. - The live check is not built yet. Until App Hosting's live check arrives, each plan only says whether it is made.
On fathym.com: OpenX →