Repository navigation
demo: ask the investigator with the token compose resolved — the shell, then ./.env, then the default - #14
Merged
Merged
Conversation
…l, then ./.env, then the default
Compose interpolates ${HOOKPROBE_TOKEN:-quickstart-token} from the shell environment, then ./.env, then the default; demo.sh read only the shell and fell back to the default, so a directory whose .env sets the token gave a stack the demo could not talk to: every lookup from step 5 on answered 401 (2026-10-19, from a checkout whose .env is a deployment's). The script now resolves the token in compose's order with a four-line dotenv reader (export prefix, quotes, last line wins) and says in its health section when the token came from ./.env.
Read back from a scratch directory whose .env set a different token: the default token answered 401 on /v1/runs, the demo printed the new line, ran all nine steps and exited 0; the stack was removed with down -v.
docs/releasing.md keeps the empty-directory rule and says why it still stands (the same .env also chooses the runtime and the model) and lists 0.7.0 among the releases whose tag message is the note.
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.
Compose interpolates
${HOOKPROBE_TOKEN:-quickstart-token}from the shell environment, then./.env, then the default.demo.shread only the shell and fell back to the default, so a directory whose.envsets the token gave a stack the demo could not talk to: every lookup from step 5 on answered 401. That is what happened on 2026-10-19 running the 0.7.0 check from a checkout whose.envis a deployment's, and it cost one false alarm before the token hashes were compared.The script now resolves the token in compose's order with a four-line dotenv reader (
exportprefix, single or double quotes, last line wins, prefix names do not match) and says in its health section when the token came from./.env.Read back from a scratch directory holding the compose file, the script and a
.envsetting a different token: the default token answered 401 on/v1/runs(so compose had taken the.envvalue), the demo printedinvestigator token: taken from ./.env, as compose did, ran all nine steps and exited 0;down -vremoved the stack.docs/releasing.mdkeeps the empty-directory rule and says why it still stands (the same.envalso chooses the investigator's runtime and model, and a stranger has neither), and lists 0.7.0 among the releases whose tag message is the note.Gate: STACK GATE GREEN locally; CI read back before merging.