A preview is your own short look at a server the room started. A kept app is that server after the work is done: your Cloud Computer keeps it running, it has a link that never changes, and the people you share it with open it signed in. It suits internal tools, dashboards, status pages and staging copies.
Keeping an app running
Where to find it. In a discussion that runs on your Cloud Computer, ask the room: "keep this running so the team can open it". The lead asks the Cloud Computer with its keep_running tool, and a card asks you first, showing the command, the folder and the port. Nothing starts until you say yes, in every permission mode.
What happens. The Cloud Computer runs the command, waits up to a minute for the port to answer, and then keeps it: it starts the app again each time it wakes, and again if the app falls over (five times in ten minutes, then it is left down). The command runs outside the run's sandbox, with your team's secrets and your Cloud Computer's variables for that repository, looked up at each start.
Only on your own Cloud Computer. On a Mac, a Task Box or a team's Own-Cloud Box the tool says what to do instead: send the discussion to your Cloud Computer first, with the place chip under the message box.
The Prompt Library has three starting points under Build and Release, each named "…, kept running": a team dashboard, a project status page and a review queue.
The link
Each app has one link, at /kept/ followed by its id. It stays the same when the app is renamed, redeployed on another port or given a new version. Whoever opens it must be signed in and let in. There is no public setting.
The chip, and the panel it opens
A discussion wears a chip in its top bar for each app it keeps, coloured by its state. The chip opens the app in the right column, beside the discussion. Details shows everything about it, each on its own row:
| Row | What it does |
|---|---|
| Link | The lasting link, with Copy Link |
| Name, About | Renaming keeps the link |
| Who opens it | Only people named here (you, your team's owner and admins, and the people you add) or Everyone in the team |
| People | Add a teammate by address; each Opens it or Opens and manages it. In a team, only teammates can be named |
| Opened | Opens today, in 7 days and in 30: a count, never who |
| Pin | Pin for Me; a team owner or admin also has Pin for the Team. Pinned apps come first in Artifacts |
| Versions | Every deploy: its number, commit, note and port, and which one is serving |
| Take down | Take Offline and Bring Back Online, and Delete… |
Apps are also listed on the Artifacts page, under Apps in its filter.
Versions, and going back
Asking the room to deploy the same name again makes the next version. Only when the new command's port answers does the app change over; if it does not come up, the version before it serves again and the room is told what the command printed.
To go back, press Ask the Room to Roll Back to This beside an older version: it writes the request in the message box, naming the commit. Keep anything the app must remember, such as a database file or uploads, in a folder no build replaces.
Asleep, and waking
Your Cloud Computer sleeps when nothing uses it, and its apps with it. Opening an app's link wakes it, usually in under a minute; the page waits and goes on by itself. While someone is reading an app the Cloud Computer stays awake.
The hours are the owner's. A visit by someone you shared an app with uses your Cloud Computer's hours, as your own use does: the included hours first, then the metered rate. Two rows in Settings → Cloud Computer → Device Settings decide this:
| Setting | Default | What it does |
|---|---|---|
| Visits Wake It | On | Someone you shared an app with can wake your Cloud Computer by opening it. Off, only you wake it, and they are told it is asleep |
| New Apps Are Shared With | Only people I name | Who can open an app when it is first kept. Everyone in my team needs you to be in a team |
At your Monthly Limit the Cloud Computer sleeps, and its apps with it.
Offline, archived, deleted
- Take Offline stops the app within a minute and keeps its link, versions and people. Bring Back Online starts it again from the command it had.
- Archiving or deleting the discussion takes its apps offline, because the discussion is where an app is changed. You are told first.
- Delete… ends the link for good.
- Deleting your Cloud Computer stops every app on it, until its discussion deploys it again on a new one.
Keeping an app current
A dashboard that reads its sources when opened needs nothing more. One that keeps a copy of its data can be refreshed on a schedule with the Prompt Library's Refresh a kept app's data (Repository Upkeep; weekday mornings, a one-dollar cap). Every refresh is a paid run, so it fetches only what is new, redeploys only when the code changed, and should not run more often than the data changes.
When not to use it. For anything public or under production traffic: it is one process on one machine. Deploy those to your own infrastructure.