Where your local data lives

When work runs on your machine, some of it lives on your machine. The runtime's database, its keys, and Studio project files always stay in Foreman's own folder. Rendered files, attachments, and encrypted daily backups live in a storage folder you can move.

Moving files off this Mac

Point the storage folder at a cloud drive that streams — Google Drive, OneDrive, or Dropbox with online-only files on. Files upload, then stop taking up space here; opening one later downloads it again.

1. In Settings → Hosting → Storage Location, choose Change folder….
2. Pick a folder such as "Foreman" inside your drive (in Google Drive, inside My Drive).
3. Foreman checks the folder and tells you what it will do. Confirm, and the runtime restarts.

You're done when the card shows "Streams to" your drive and work still runs.

Relocating requires the device-management capability, because it moves where a workspace's local files physically sit — not something a member should do to someone else's machine.

What Foreman refuses

• Mirrored folders. A folder your sync app mirrors keeps a full copy on this Mac, so it frees nothing.
• Foreman's own folder, or anything that contains it. That is where the database and keys live, and a sync app rewriting them underneath a running process corrupts them. Never add Foreman's own folder to a sync app yourself, either.

Gotchas

• Your drive app must be running. While it is quit, files that were moved off this Mac can't be opened; Settings shows the folder as unreachable until it is back.
• Backups need this Mac's keys. The backups in your drive are encrypted with a key that stays on this Mac, so they restore only with this install's data.
• Moving storage does not move your workspace. Central data stays central.