Import deploy-flake content from the private deploy repo #1

New issue

Closed

opened 2026-07-17 06:47:51 +01:00 by allod-agent · 1 comment

allod-agent commented

2026-07-17 06:47:51 +01:00

Member

The public allod/deploy repo is currently empty apart from a seeded LICENSE. It is meant to hold the deploy-flake composition consumed by nexus provisioning via DEPLOY_FLAKE — the flake that pins inventory and secrets revisions and names the VM deployment targets. That composition currently lives in a private deploy repo and needs to be copied over into this public repo.

Scope

Copy the deploy-flake composition from the private deploy repo into allod/deploy.
Apply the public-org audit before publishing: no plaintext secrets, no personal identifiers, and no host-specific private addressing. Age-encrypted blobs are fine in public repos by design.
Keep the existing GPL-3.0-or-later LICENSE already present on master.
Add a README for the repo once content lands (there is none yet).

Context

Part of the public release and private-first migration arc; see allod/strategy#11. The LICENSE was seeded ahead of the content import so the repo already carries GPL-3.0-or-later. Because the repo had no commits it could not take a pull request, so the license was committed directly to master as the initial (root) commit.

Refs allod/strategy#11

The public `allod/deploy` repo is currently empty apart from a seeded LICENSE. It is meant to hold the deploy-flake composition consumed by nexus provisioning via `DEPLOY_FLAKE` — the flake that pins `inventory` and `secrets` revisions and names the VM deployment targets. That composition currently lives in a private deploy repo and needs to be copied over into this public repo. ## Scope - Copy the deploy-flake composition from the private deploy repo into `allod/deploy`. - Apply the public-org audit before publishing: no plaintext secrets, no personal identifiers, and no host-specific private addressing. Age-encrypted blobs are fine in public repos by design. - Keep the existing GPL-3.0-or-later LICENSE already present on `master`. - Add a README for the repo once content lands (there is none yet). ## Context Part of the public release and private-first migration arc; see allod/strategy#11. The LICENSE was seeded ahead of the content import so the repo already carries GPL-3.0-or-later. Because the repo had no commits it could not take a pull request, so the license was committed directly to `master` as the initial (root) commit. Refs allod/strategy#11

allod-agent referenced this issue from allod/strategy

2026-07-17 06:48:43 +01:00

License public repos and create Allod landing docs #11