Write a snapshot file
Put the shared setup indefault.snapshot.toml beside the manifests:
default.snapshot.toml. A manifest’s own setup then holds only what its
service needs on top, and you can leave it out when there is nothing more:
setup, then the manifest’s setup,
then dev. On a box that started from a snapshot, the install finds almost
everything in place and finishes quickly.
The disk this setup leaves behind is shared with every box that starts
from it, including teammates’ boxes. Keep anything specific to one box, such
as its address or a per-box secret, in the manifest’s setup or dev.
Give a service its own snapshot
A service that needs a different base names another snapshot file withfrom_snapshot:
How snapshots are made
You don’t build snapshots by hand. The first box that starts blank at a commit runs the snapshot file’ssetup and captures its disk the moment
that setup finishes, before the manifest’s setup, dev, or anyone else
touches the box. The run carries on while the capture finishes in the
background. Boxes that start from a snapshot never make one.
A new box starts from the snapshot nearest its commit, so a box a few
commits ahead of the snapshot still starts warm.
To make the snapshots a commit is missing now, and wait for them:
tesser snapshot create from CI on every push to your default
branch keeps a fresh snapshot waiting for everyone. Agents and
CI covers how CI signs in.