feat: add .glama/entrypoint.sh for Glama-deployed builds#12
Merged
Conversation
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
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.
Summary
Adds
.glama/entrypoint.shso the Glama-managed deployment (glama.ai/mcp/servers/intent-driven-software/idf-mcp) can spawn the IDF host + bootstrap the demo domain + hand off tomcp-idfstdio in a single script invocation.Why
Glama's Dockerfile admin is form-based (Base image / Build steps / CMD arguments), not a free-form Dockerfile paste. The cleanest fit is to put the multi-stage logic into a script that lives in the repo, then point CMD arguments at it.
The script:
npm run server) in background on:3001/api/effectshealthcheckinvestdemo domain (typemap + intents POSTed from/opt/idf/src/domains/invest/{ontology,intents}.js)exec mcp-idf— stdio MCP server, foreground; this is what Glama Inspector / "Try in Browser" connects tostderr carries host log + bootstrap chatter; stdout is reserved for the MCP wire-protocol so Inspector doesn't get garbled.
Glama configuration (paste into form fields)
After this PR merges, fill the Dockerfile admin like this:
debian:trixie-slim(default)25(default — works fine, host requires Node ≥20)3.14(default — only used to compilebetter-sqlite3)["/app/.glama/entrypoint.sh"]The shebang (
#!/usr/bin/env bash) + executable bit on the script make it directly invokable; no need for["bash", "/app/.glama/entrypoint.sh"].Bootstrap must happen at runtime (it POSTs to the just-started host), so it intentionally lives in CMD rather than build steps — per Glama's tip, only the actual setup that can't be pre-baked is left for runtime.
Changes
.glama/entrypoint.sh(85 lines, executable)No code, no behavioural changes to the published
@intent-driven/mcp-serverpackage —.glama/is excluded from the npm tarball by the existingfilesarray inpackage.json.