feat(api): declarative container command/entrypoint + file injection - #144
Merged
Merged
Conversation
Projects can set a container command/entrypoint and inject files without VM or Docker access.
- command/entrypoint thread through the deploy API and moor_deploy MCP into the
Docker create body, set only when provided (image defaults unchanged otherwise).
- files ({path, content, mode}) are written into the container via a tar archive
PUT before start, on every (re)create, honoring the mode in the tar header.
Motivating case: run cloudflare/cloudflared with command [tunnel, run] + a
TUNNEL_TOKEN env and an injected TLS cert, with zero repo Dockerfile and zero ssh.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Lets a project set its container command/entrypoint and inject files without anyone opening the VM or running docker by hand. Today changing either means ssh-ing in or baking a one-off Dockerfile; this moves both into the declarative project model, alongside env and volumes.
The case that motivated it: running cloudflare/cloudflared with command [tunnel, run] plus a TUNNEL_TOKEN env and an injected TLS cert, with no repo Dockerfile and no ssh.
Verified: bunx biome check, tsc -p apps/api/tsconfig.json, and bun test all pass; new tests cover the create body (Cmd/Entrypoint present only when set) and the archive-before-start ordering with the file mode.