Skip to content

docs(activation): fix profile.d ordering vs [vars] #55

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
djsauble wants to merge 2 commits into
base: docs/plugins-concept-page
Choose a base branch
from
Open

docs(activation): fix profile.d ordering vs [vars] #55

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3d4ca7e
docs(activation): fix profile.d ordering vs [vars]
djsauble Jul 30, 2026
7d8f210
docs(activation): note profile.d is skipped in run mode
djsauble Aug 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 8 additions & 5 deletions concepts/activation.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -247,8 +247,8 @@ sequenceDiagram
rect rgb(235, 248, 240)
Note over P: bash
P->>P: run setup scripts
P->>P: set user variables
P->>P: source profile.d scripts (plugins)
P->>P: set user variables
P->>P: source hook.on-activate
P->>P: exec FLOX_SHELL
end
Expand Down Expand Up @@ -278,10 +278,13 @@ which is also the variable you can use to override which shell Flox uses when
you activate an environment.

As part of this activation script,
Flox runs some initial setup, then sets the variables you've provided in the
[[vars] section of your manifest](/man/manifest.toml#vars).
It then sources every installed package's `profile.d` scripts — this is how
[plugins](/concepts/plugins) hook into activation.
Flox runs some initial setup, then sources every installed package's
`profile.d` scripts — this is how [plugins](/concepts/plugins) hook into

@tanjadev tanjadev Aug 4, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps we should add the caveat that this is only true in dev (the default) and build modes, in run mode package scripts are deliberately skipped.

activation. This only happens in `dev` (the default) and `build` modes;
`run` mode deliberately skips package `profile.d` scripts. Next, it sets
the variables you've provided in the
[[vars] section of your manifest](/man/manifest.toml#vars) — these aren't
visible to profile.d scripts, only to what runs after them.
Next, the script _sources_ the `hook.on-activate` script that you've provided
in the [[hook] section of your manifest](/man/manifest.toml#hook).
Since this script is run by the Bash shell we're using,
Expand Down