Returning the hardcoded default from get_caddy_ingress_image() when the spec key was absent meant every `deployment start` would patch a running Caddy back to :latest — silently reverting any image set out-of-band (ansible playbook, prior deployment's spec). Make get_caddy_ingress_image() return Optional[str]. Install path still falls back to the default (needs *some* image to install); the update-on-reuse path treats None as "operator didn't ask, leave the running Caddy alone". Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| images | ||
| CONTRIBUTING.md | ||
| README.md | ||
| adding-a-new-stack.md | ||
| cli.md | ||
| deployment_patterns.md | ||
| docker-compose-deployment.md | ||
| fetching-containers.md | ||
| gitea-with-laconicd-fixturenet.md | ||
| helm-chart-generation.md | ||
| k8s-deployment-enhancements.md | ||
| laconicd-with-console.md | ||
| release-process.md | ||
| spec.md | ||
| webapp.md | ||
README.md
Stack Orchestrator
Here you will find information about the design of stack orchestrator, contributing to it, and deploying services/applications that combine two or more "stacks".
Most "stacks" contain their own README which has plenty of information on deploying, but stacks can be combined in a variety of ways which are document here, for example: