ArticlePublished: 2 min readSample
Reading shared configuration at build time
Why every app in the ecosystem fetches one registry before it builds, and why a failed fetch should fail the build instead of falling back.
ChronicleSample
Ecosystem Config
Ecosystem Config holds the shared facts every other project reads. Its Chronicle records how consumers use it and the questions that are still open.
- Destination
- Central Station
- Status
- Active
- Logged so far
- 3 logged items
- Project
- Visit project
Logged so far
Milestones, decisions and updates in the order they happened.
MilestoneExploring
One sync script or many?
Weighing a shared consumer script against each project owning its own.
UpdateExploringSample
Ecosystem Config: notes on how consumers read the registry
Each consumer keeps only the fields it needs. Questions worth answering before adding more consumers.
Decision
Consumers keep a minimal projection
Each consumer copies only the fields it shows, so the full registry never reaches a visitor's browser.
Ahead
Milestones that are planned or being explored. Nothing here is finished.
MilestonePlanned
A rule for unknown destinations
Deciding how a consumer should show a destination it doesn't recognise.
Related writing