sprawl dna

DNA Governance

Manages active DNA registry sources and aliases.

📌 1. The Target Problem

1. The Target Problem

"How do I add secondary DNA registries for other teams or projects without polluting my global core DNA guidelines?"

Developers working across multiple clients or teams often need distinct DNA registries. Storing them inside a single global core repository results in conflict, while manually changing registry paths on every workspace is slow.

⚙️ 2. Usage & Options

sprawl dna <list|inspect|update>

Options & Flags

  • list: List all registered DNA sources.
  • inspect: Show the directory tree of the active DNA source.
  • update: Git pull and refresh the active DNA registry source.

🔍 3. How it Works (Under the Hood)

  1. Clones secondary DNA repositories into ~/.sprawl/dna/ folders under alias aliases.
  2. Saves references to registries in the global configuration files database.
  3. Resolves artifacts from active DNA aliases matching settings inside sprawl_manifest.yml during synchronization.

🩺 4. Troubleshooting

  • Error: DNA alias already exists
  • Resolution: You are registering a DNA source under a label that is already taken. De-register the old source or provide a unique name.

🔗 Related Resources & Tutorials