From 811bbd9db4e51c6ecc042254d66164a0dc18d882 Mon Sep 17 00:00:00 2001 From: "A. F. Dudley" Date: Sat, 24 Jan 2026 10:43:12 -0500 Subject: [PATCH] Add TODO.md with planned features and refactoring - Update stack command for continuous deployment workflow - Separate deployer from CLI - Separate stacks from orchestrator repo Co-Authored-By: Claude Opus 4.5 --- TODO.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 TODO.md diff --git a/TODO.md b/TODO.md new file mode 100644 index 00000000..349530c8 --- /dev/null +++ b/TODO.md @@ -0,0 +1,16 @@ +# TODO + +## Features Needed + +### Update Stack Command +We need an "update stack" command in stack orchestrator and cleaner documentation regarding how to do continuous deployment with and without payments. + +**Context**: Currently, `deploy init` generates a spec file and `deploy create` creates a deployment directory. The `deployment update` command (added by Thomas Lackey) only syncs env vars and restarts - it doesn't regenerate configurations. There's a gap in the workflow for updating stack configurations after initial deployment. + +## Architecture Refactoring + +### Separate Deployer from Stack Orchestrator CLI +The deployer logic should be decoupled from the CLI tool to allow independent development and reuse. + +### Separate Stacks from Stack Orchestrator Repo +Stacks should live in their own repositories, not bundled with the orchestrator tool. This allows stacks to evolve independently and be maintained by different teams.