-
Notifications
You must be signed in to change notification settings - Fork 6
Explanation
github-actions[bot] edited this page Jul 13, 2026
·
1 revision
These pages build understanding of ccflow — what it is for, the ideas behind its design, and why it leans on the tools it does. They are for reading and reflection rather than for following along at the keyboard; when you want to do something, reach for a How-to Guide or work through a Tutorial instead.
-
Core Concepts — the vocabulary of
ccflow(models, the registry, contexts, results, callable models, evaluators, publishers) and how the configuration half and the workflow half fit together into one framework. -
Design Goals — the problems
ccflowset out to solve for configuration and workflow management, and the requirements that shaped it. -
Configuration and Hydra — why file-based configuration and a command line matter, what
hydraand its config groups bring, and how theModelRegistrycomplements them to enable composable, dispatchable applications.
If you are new, the Design Goals explain the "why does this exist at all", Core Concepts give you the shared language used everywhere else, and Configuration and Hydra motivates the composition style used in the Composing an ETL Application tutorial.
This wiki is autogenerated. To made updates, open a PR against the original source file in docs/wiki.
Tutorials
- Overview
- First Steps
- Configuring Models
- Defining Workflows
- Building an ETL Pipeline
- Composing an ETL Application
- Building a Configurable Calculator
How-to Guides
- Overview
- Install ccflow
- Configure Complex Values
- Bind Logic to Configs
- Run Workflows from the CLI
- Cache Results
- Retry on Failure
Reference
Explanation
Developer Guide