docs: updates for vars and on-deactivate - #83
Merged
Conversation
Flox 1.15.0 sources the interpreter's profile.d scripts, exports the manifest's [vars], and only then sources plugin profile.d scripts, so plugin scripts can read [vars] entries. Reorder the timeline diagram to match and describe the precedence: a plugin's export wins over a same-named [vars] entry, and hook.on-activate is the way to override it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TaaEqpV6jLfLPJWSXKc7MZ
Two shells can share one activation, and the deactivation section didn't say what happens when each of them leaves. Add a sequence diagram and prose: profile.deactivate runs for every flox deactivate, the activation stays up while another shell is attached, and only the last detach tears it down — stopping services, then running hook.on-deactivate in the background process. Note the same once-per-activation property in the hook.on-activate summary, since that is where readers look for what a hook does: the hook runs for the first flox activate, and its on-deactivate bookend when the last activation detaches. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TaaEqpV6jLfLPJWSXKc7MZ
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
The plugins concept page reached docs.json without a regeneration, so the committed llms.txt has been missing it since. check-llms-txt runs on any PR that touches an .mdx file, so this drift fails CI here. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TaaEqpV6jLfLPJWSXKc7MZ
stephenyeargin
approved these changes
Aug 27, 2026
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
2 participants
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.
docs(activation): set [vars] before plugin profile.d scripts
Flox 1.15.0 sources the interpreter's profile.d scripts, exports the
manifest's [vars], and only then sources plugin profile.d scripts, so
plugin scripts can read [vars] entries. Reorder the timeline diagram to
match and describe the precedence: a plugin's export wins over a
same-named [vars] entry, and hook.on-activate is the way to override it.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
docs(activation): diagram teardown when the last shell exits
Two shells can share one activation, and the deactivation section didn't
say what happens when each of them leaves. Add a sequence diagram and
prose: profile.deactivate runs for every flox deactivate, the activation
stays up while another shell is attached, and only the last detach tears
it down — stopping services, then running hook.on-deactivate in the
background process.
Note the same once-per-activation property in the hook.on-activate
summary, since that is where readers look for what a hook does: the hook
runs for the first flox activate, and its on-deactivate bookend when the
last activation detaches.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com