Getting started with the Central Registry

The Central Registry empowers teams to standardize and reuse building blocks to spot errors early, scale reliably and control their configuration. Get started with the Central Registry here.

---

Step 1: Install the cue command

The cue command is the essential tool that validates and exports configurations, and communicates with the Central Registry. Begin by Installing CUE, then return here.

---

Step 2: Validate a configuration

Choose a curated module related to software that you use and follow the guide that's linked here:

• Argo Workflows

• Azure Pipelines

• Buildkite Pipelines

• Docker Compose

• GitHub Actions

• GitLab CI/CD

• GoReleaser

If nothing jumps out at you, we suggest following the Docker Compose guide.

---

Next steps: Learn more

Well done! Now you've successfully started to use the Central Registry you can continue to:

• Explore the full range of available modules published by CUE Labs and others. Browse the list of curated modules, or find an official or third-party module by searching the Central Registry.

• Follow the tutorial Publishing modules to the Central Registry. It gives you illustrated, step-by-step instructions that take you through the process of publishing a module to the Central Registry, and then using the published module to validate a configuration in a second module.

• Learn more about CUE on its website, cuelang.org. Popular guides include:

  • The CUE language tour
  • Modules concept guides
  • How CUE works with JSON, and with YAML, and with TOML
  • How CUE enables configuration and How CUE enables data validation