Dasemu c918b32e72 feat: support publishing a container's port to host loopback ...

Some installations need to stay reachable by a native process on the
same host outside the manager's own proxy — e.g. a legacy nginx
location serving media/signed URLs for an app that also happens to be
an MCP server. Previously this required manually recreating the
container outside the manager's lifecycle (lost on the next
build/redeploy). publishHostPort makes it a real, persisted setting.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-10-08 07:05:56 +02:00

..

api

feat: support publishing a container's port to host loopback

2026-10-08 07:05:56 +02:00

build

feat: support an explicit start command override per installation

2026-10-08 06:46:28 +02:00

config

feat: enforce per-container memory/CPU limits

2026-10-08 03:12:44 +02:00

crypto

test: add vitest unit tests and Gitea Actions CI workflow

2026-10-08 03:13:04 +02:00

db

feat: support publishing a container's port to host loopback

2026-10-08 07:05:56 +02:00

docker

feat: support publishing a container's port to host loopback

2026-10-08 07:05:56 +02:00

middleware

test: add vitest unit tests and Gitea Actions CI workflow

2026-10-08 03:13:04 +02:00

proxy

feat: support optional per-installation Basic Auth on the MCP proxy

2026-10-08 05:05:11 +02:00

service

feat: support publishing a container's port to host loopback

2026-10-08 07:05:56 +02:00

types

feat: SQLite-backed installations, REST API, admin auth and web UI

2026-10-08 01:42:06 +02:00

index.ts

fix: scope express.json() to /api so the MCP proxy stops hanging

2026-10-08 04:43:49 +02:00