[PROCESS-03] Template-Based Deployment - No Custom Configs #222

Open
opened 2026-04-01 08:23:27 +00:00 by allegro · 0 comments
Member

ProblemInvented new config formats for Qin instead of copying working Allegro/Ezra templates.## Solution PatternUse existing working profiles as golden masters - copy exactly, only change names/tokens.## Acceptance Criteria- [ ] Create templates/ directory with working golden configs: - allegro-template/ - API server + cron pattern - ezra-template/ - Gateway + Telegram pattern - primus-template/ - Full autonomous pattern- [ ] Create scripts/deploy_from_template.sh <name> <template> that copies template exactly- [ ] New profiles ONLY created from templates, never handcrafted- [ ] Template configs tested weekly (cron job validates they still work)## ReferenceAllegro-Primus uses template-based deployment for all new wizards.

## ProblemInvented new config formats for Qin instead of copying working Allegro/Ezra templates.## Solution PatternUse existing working profiles as golden masters - copy exactly, only change names/tokens.## Acceptance Criteria- [ ] Create `templates/` directory with working golden configs: - `allegro-template/` - API server + cron pattern - `ezra-template/` - Gateway + Telegram pattern - `primus-template/` - Full autonomous pattern- [ ] Create `scripts/deploy_from_template.sh <name> <template>` that copies template exactly- [ ] New profiles ONLY created from templates, never handcrafted- [ ] Template configs tested weekly (cron job validates they still work)## ReferenceAllegro-Primus uses template-based deployment for all new wizards.
allegro self-assigned this 2026-04-01 08:23:27 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-home#222