Skip to content

Conversation

@ysndr
Copy link
Contributor

@ysndr ysndr commented Jan 12, 2026

FloxHub environments have become more performant enough to recommend them as "default" environments.
This commit establishes them as an alternative to local only environments in the "Default Env" guide.

Currently, the "Flox as Homebrew laternative" guide still uses language of "local only" default envs, it leans heavily on output of the current auto onboarding, that has yet to be adapted to FloxHub environemnts (flox/flox#3867).

@github-actions github-actions bot added the documentation Improvements or additions to documentation label Jan 12, 2026
@ysndr ysndr force-pushed the push-ynwqryvslnut branch from f06c050 to 5ab7f6c Compare January 12, 2026 12:33
@github-actions
Copy link

@ysndr ysndr force-pushed the push-ynwqryvslnut branch from 5ab7f6c to db6b79a Compare January 12, 2026 12:34
@github-actions
Copy link

** For FloxHub environments:**

```{ .bash .copy }
eval "$(flox activate -r <your username>/default -m run)"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

We should acknowledge that this will perform an interactive login on first use, and potentially trust settings if not owned by the current user (or the current becomes logs out e.g. due to token expiration).

flox init
```

If you plan to use your `default` environment on multiple systems,
Copy link
Contributor

Choose a reason for hiding this comment

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

Per sync convo, we should make the -r flow primary, and we can do something like add a breadcrumb to docs on -d environments or add a footnote about local only environments

@ysndr ysndr force-pushed the push-ynwqryvslnut branch from db6b79a to 24a8b2e Compare January 14, 2026 13:57
Comment on lines 176 to 177
In fact, initializing default environments on other machines
will link to the environment that is already on FloxHub.
Copy link
Contributor

Choose a reason for hiding this comment

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

To me that makes it sound like other machines should run flox init --remote

Suggested change
In fact, initializing default environments on other machines
will link to the environment that is already on FloxHub.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

they might as well..
Ill mention activate as primary reason

Copy link
Contributor

Choose a reason for hiding this comment

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

I still find that confusing. Hypothetically if someone ran flox init -r, it would get linked to an environment that already exists. But a user shouldn't do that, so I don't understand why we'd mention it. Am I misunderstanding?


```{ .bash .copy }
cd ~;
flox pull <your user>/default
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we replace this with a code block that has flox activate -r to use it on another machine?

✅ Authentication complete
✅ Logged in as <youruser>

flox init -r <youruser>/default
Copy link
Contributor

Choose a reason for hiding this comment

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

Has that merged?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

in review flox/flox#3884

@ysndr ysndr force-pushed the push-ynwqryvslnut branch from 24a8b2e to 08bb2df Compare January 14, 2026 16:08
ysndr added 2 commits January 15, 2026 17:59
Guide needs to be adapted with changed output of the auto onboarding flow addressed in <flox/flox#3867>.
@ysndr ysndr force-pushed the push-ynwqryvslnut branch from 08bb2df to 340fd46 Compare January 15, 2026 16:59
@github-actions
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants