magpie

1,126 Commits 1 Branch 0 Tags

2 Commits

Include renames

Author	SHA1	Message	Date
yetone	0bb119f87f	docker: sign-ins and plugins survive a restart, and the image checks its own health (Jorben on Discord) — only /config was a volume, while HOME (/home/nonroot) held the agents' sign-ins (~/.codex, ~/.claude…) and the cache held Bun: a new container lost them all, and distroless/static has no libc, so the Bun magpie downloads couldn't start (fork/exec … no such file or directory). HOME and XDG cache/data/state now live under /config (made on start, so an old volume keeps working), the base is distroless/cc (glibc), and magpie healthcheck backs a HEALTHCHECK with no curl needed. Verified in Docker: an old volume carried over, a market plugin installed and stayed across a recreate without downloading Bun again, the container reported healthy. TestHealthcheck and TestMakeDirs fail without the change.	2026-10-01 11:38:37 +08:00
Shelken glm-5.3-flash yetone	1a704bd6ba	docker: a server image and a multi-arch build workflow (#245 ) * docker: a server image and a multi-arch build workflow The image is the terminal-only binary built with -tags nogui on distroless static, run as nonroot with magpie's files on a /config volume, created and chowned at build time so a fresh named volume is writable by uid 65532. The workflow builds amd64 and arm64 on native runners, smoke-tests each image before anything is pushed (ready probe, unknown-model 4xx JSON, /config write), pushes by digest, merges a multi-arch manifest (semver trio plus latest on v* tags, edge otherwise) and attests build provenance. PR runs build and smoke-test only. The README documents running the image, the web UI mode, and why subscription sign-ins must start where a browser shares loopback with magpie. Co-Authored-By: glm-5.3-flash <hakase@ooooo.space> Generated-By: omp 18.4.3 * docker: README publishes the ports on the host's loopback and says how to require a key — until the gateway is shared from Settings it takes any key from anyone who reaches it, and Docker's -p 3425:3425 puts it on every interface of the host past its firewall. Checked in the built image: with settings lan+lanKey a request from the host through the published port without the key gets 401 and with it 200; without them any key gets 200. --------- Co-authored-by: glm-5.3-flash <hakase@ooooo.space> Co-authored-by: yetone <yetoneful@gmail.com>	2026-09-30 03:21:19 +08:00

Author

SHA1

Message

Date

yetone

0bb119f87f

docker: sign-ins and plugins survive a restart, and the image checks its own health (Jorben on Discord) — only /config was a volume, while HOME (/home/nonroot) held the agents' sign-ins (~/.codex, ~/.claude…) and the cache held Bun: a new container lost them all, and distroless/static has no libc, so the Bun magpie downloads couldn't start (fork/exec … no such file or directory). HOME and XDG cache/data/state now live under /config (made on start, so an old volume keeps working), the base is distroless/cc (glibc), and magpie healthcheck backs a HEALTHCHECK with no curl needed. Verified in Docker: an old volume carried over, a market plugin installed and stayed across a recreate without downloading Bun again, the container reported healthy. TestHealthcheck and TestMakeDirs fail without the change.

2026-10-01 11:38:37 +08:00

1a704bd6ba

docker: a server image and a multi-arch build workflow (#245 )

* docker: a server image and a multi-arch build workflow

The image is the terminal-only binary built with -tags nogui on
distroless static, run as nonroot with magpie's files on a /config
volume, created and chowned at build time so a fresh named volume
is writable by uid 65532.

The workflow builds amd64 and arm64 on native runners, smoke-tests
each image before anything is pushed (ready probe, unknown-model
4xx JSON, /config write), pushes by digest, merges a multi-arch
manifest (semver trio plus latest on v* tags, edge otherwise) and
attests build provenance. PR runs build and smoke-test only.

The README documents running the image, the web UI mode, and why
subscription sign-ins must start where a browser shares loopback
with magpie.

Co-Authored-By: glm-5.3-flash <hakase@ooooo.space>
Generated-By: omp 18.4.3

* docker: README publishes the ports on the host's loopback and says how to require a key — until the gateway is shared from Settings it takes any key from anyone who reaches it, and Docker's -p 3425:3425 puts it on every interface of the host past its firewall. Checked in the built image: with settings lan+lanKey a request from the host through the published port without the key gets 401 and with it 200; without them any key gets 200.

---------

Co-authored-by: glm-5.3-flash <hakase@ooooo.space>
Co-authored-by: yetone <yetoneful@gmail.com>

2026-09-30 03:21:19 +08:00