Keep a workspace awake
Keep a workspace from sleeping for a while, or keep it always running.
A workspace that Sleeps when idle sleeps after its idle timeout without use. That is what you want most of the time, but not during a long build in a terminal you stopped watching. You have three ways to keep it awake, from the lightest to the heaviest.
Open a keep-awake window
A keep-awake window keeps the IDE from sleeping for a while, at most 12 hours. It ends early when the workspace stops or restarts.
Open Workspace settings on the rail and click Keep awake for 2 hours. The panel says "Kept awake until …". Stop keeping awake ends the window.
Workspace settings → Power shows "kept awake by the keep-awake window" while it is open.
Sleep later
The idle timeout is 60 minutes unless your installation sets another default. Give this workspace its own under Workspace settings → Sleep after (minutes): a whole number from 1 to 1440. Use default goes back to the installation's.
For a service, set idleTimeoutMinutes in harthelm.yml and Sync:
services:
worker:
type: steps
steps: [{run: ./worker}]
idleTimeoutMinutes: 240Keep it always running
Workspace settings → Availability → Always running keeps the IDE running around the clock.
Switching a sleeping workspace to Always running wakes it. hart ws create --no-sleep creates a workspace that is
always running, and a service never sleeps with availability: always.
Always running has costs
A workspace that is always running holds its share of the team's quota all the time, and it is never archived: workspace backups are taken only while a workspace sleeps.
Put it to sleep now
Done for the day? Workspace settings → Put to sleep now stops the IDE, the terminals and running steps at once. Files are kept, and opening the workspace wakes it again.