Guides
Remote State
Lithos can keep state next to lithos.yml or in an S3-compatible object
store. Remote state is the better choice once more than one machine,
person, or CI job deploys the same project.
Remote state gives every deployer the same current graph and the same recent deployment history.
- CI and local machines read the same state.
- You avoid merging state files in Git.
lithos undosees the same checkpoints everywhere.