Automatic deploys on image build #1

Closed
opened 2026-05-23 20:54:47 +00:00 by coilysiren · 1 comment
Owner

Originally filed by @coilysiren on 2026-05-22T11:08:26Z - https://github.com/coilysiren/lunch-money-k8s/issues/12

Today a deploy is manual: coily exec lunch-money from the infrastructure repo after CI builds the image. Consider an automatic path - a ship job in docker.yml that rolls the kai-server deployment after a successful image build, similar to coilysiren/repo-recall's docker workflow.

Not urgent. Manual deploy is fine for a deployment of one, and arguably safer. File-and-defer until Kai decides she wants it.

_Originally filed by @coilysiren on 2026-05-22T11:08:26Z - [https://github.com/coilysiren/lunch-money-k8s/issues/12](https://github.com/coilysiren/lunch-money-k8s/issues/12)_ Today a deploy is manual: `coily exec lunch-money` from the infrastructure repo after CI builds the image. Consider an automatic path - a `ship` job in `docker.yml` that rolls the kai-server deployment after a successful image build, similar to coilysiren/repo-recall's docker workflow. Not urgent. Manual deploy is fine for a deployment of one, and arguably safer. File-and-defer until Kai decides she wants it.
coilysiren added
P4
and removed
P3
labels 2026-06-04 08:16:51 +00:00
Author
Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.
coilysiren 2026-06-17 08:24:20 +00:00
Sign in to join this conversation.
No description provided.