All checks were successful
Lint Checks / Run linter (push) Successful in 13s
- Remove init_operation() from restart - don't regenerate spec from commands.py defaults, use existing git-tracked spec.yml instead - Add docs/deployment_patterns.md documenting GitOps workflow - Add pre-commit rule to CLAUDE.md - Fix line length issues in helpers.py Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2.2 KiB
2.2 KiB
Deployment Patterns
GitOps Pattern
For production deployments, we recommend a GitOps approach where your deployment configuration is tracked in version control.
Overview
- spec.yml is your source of truth: Maintain it in your operator repository
- Don't regenerate on every restart: Run
deploy initonce, then customize and commit - Use restart for updates: The restart command respects your git-tracked spec.yml
Workflow
- Initial setup: Run
deploy initonce to generate a spec.yml template - Customize and commit: Edit spec.yml with your configuration (hostnames, resources, etc.) and commit to your operator repo
- Deploy from git: Use the committed spec.yml for deployments
- Update via git: Make changes in git, then restart to apply
# Initial setup (run once)
laconic-so --stack my-stack deploy init --output spec.yml
# Customize for your environment
vim spec.yml # Set hostname, resources, etc.
# Commit to your operator repository
git add spec.yml
git commit -m "Add my-stack deployment configuration"
git push
# On deployment server: deploy from git-tracked spec
laconic-so deploy create \
--spec-file /path/to/operator-repo/spec.yml \
--deployment-dir my-deployment
laconic-so deployment --dir my-deployment start
Updating Deployments
When you need to update a deployment:
# 1. Make changes in your operator repo
vim /path/to/operator-repo/spec.yml
git commit -am "Update configuration"
git push
# 2. On deployment server: pull and restart
cd /path/to/operator-repo && git pull
laconic-so deployment --dir my-deployment restart
The restart command:
- Pulls latest code from the stack repository
- Uses your git-tracked spec.yml (does NOT regenerate from defaults)
- Syncs the deployment directory
- Restarts services
Anti-patterns
Don't do this:
# BAD: Regenerating spec on every deployment
laconic-so --stack my-stack deploy init --output spec.yml
laconic-so deploy create --spec-file spec.yml ...
This overwrites your customizations with defaults from the stack's commands.py.
Do this instead:
# GOOD: Use your git-tracked spec
git pull # Get latest spec.yml from your operator repo
laconic-so deployment --dir my-deployment restart