Backups and templates
Storage is safe: it lives in the EU, independently of any sandbox. A sandbox's own folder
/sandbox is fast but local, and can be lost, for example when the machine it runs on is
replaced. nido backs it up to your storage whenever the sandbox stops.
nido stop scratch # backs up /sandbox, then stops
nido stop scratch --no-backup # stops without a backup
nido restore scratch # puts the last backup back into a running sandbox
nido ls # shows each sandbox's last backup
A backup holds what changed in /sandbox since the sandbox was created; the files that came with
the image are not stored again. If a sandbox's folder was lost, nido start puts the last backup
back by itself and tells you so. Backups count as storage.
Backups of removed sandboxes
Removing a sandbox keeps its backup. nido ls lists the backups of removed sandboxes. A new
sandbox with the same name can take the backup back with nido restore <name>. To delete a backup:
nido rm scratch --backup # removes the sandbox and its backup
Templates
Save a sandbox's work as a template and start new sandboxes from it:
nido save scratch base # template "base" from the running sandbox
nido create other --from base # or from: base in x-nido
nido fork scratch experiment # a new sandbox with the work of a running one
nido save ls
nido save rm base