Use it#
The pages a reader needs once they are past the model and the policies: what a real config runs into, how to bring an existing estate in or start a new one, day-to-day operation, where things are stored, and the fork’s own surface.
| Page | Question it answers |
|---|---|
| Compatibility reference | What in a real configuration this fork accepts or refuses |
| How to check a configuration before migrating | Running choudoufu live-check against your own code |
| Migrate an existing estate | How resources you already manage bind to their markers |
| Day-2 operations | Renaming, removing, recording effects and working with other people, indexed |
| Start a new estate | The live block, from a first apply |
| Questions | Short answers to the questions that come up first |
| How to write markers inside a for_each’d module | Threading each.key through a wrapped module by hand |
| Where things are stored | State, records and receipts, and what lives where |
| How the compatibility numbers are measured | Where the corpus ranking comes from, and what not to read into it |
| Reference | The fork’s call surface, per stage |