πŸ’» Code Repositories

Code Repositories #

All Deevnet projects are hosted on GitHub: github.com/deevnet


Repository Layout #

home/
β”œβ”€β”€ ansible-collection-deevnet.builder/
β”œβ”€β”€ ansible-collection-deevnet.mgmt/
β”œβ”€β”€ ansible-collection-deevnet.net/
β”œβ”€β”€ ansible-inventory-deevnet/
β”œβ”€β”€ deevnet-image-factory/
β”œβ”€β”€ deevnet-tenant-fabric/
β”œβ”€β”€ deevnet-tenant-tdemo/           the demo tenant
β”œβ”€β”€ deevnet-tenant-<name>/          one per tenant
└── deevnet-docs/

All repositories are designed to be cloned into a common parent directory (typically ~/home/ or /srv/home/).

Tenants get their own repositories #

A tenant is not a directory inside a substrate repo. Each one is deevnet-tenant-<name>, and that repository is the tenant: its network, its workloads and its DNS records are declared there and rebuilt from there ( ADR-0006).

The split is what makes the tenant contract real rather than aspirational β€” a tenant’s recurring lifecycle touches no substrate repository at all. New tenants are created by copying examples/tenant/ out of the tenant factory, never by copying a live tenant.


Getting Started #

# Clone all repositories
mkdir -p ~/home && cd ~/home
git clone git@github.com:deevnet/ansible-collection-deevnet.builder.git
git clone git@github.com:deevnet/ansible-collection-deevnet.mgmt.git
git clone git@github.com:deevnet/ansible-collection-deevnet.net.git
git clone git@github.com:deevnet/ansible-inventory-deevnet.git
git clone git@github.com:deevnet/deevnet-image-factory.git
git clone git@github.com:deevnet/deevnet-tenant-fabric.git
git clone git@github.com:deevnet/deevnet-tenant-tdemo.git
git clone git@github.com:deevnet/deevnet-docs.git

Standards Authority #

deevnet-docs is authoritative β€” if a project conflicts with standards defined here, standards win.

Other repos may include it as a git submodule at docs/deevnet/.

Page last modified: September 17, 2026