-
Notifications
You must be signed in to change notification settings - Fork 11
docs: default-environment recommends FloxHub env #397
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.
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
base: main
Are you sure you want to change the base?
Conversation
f06c050 to
5ab7f6c
Compare
5ab7f6c to
db6b79a
Compare
| ** For FloxHub environments:** | ||
|
|
||
| ```{ .bash .copy } | ||
| eval "$(flox activate -r <your username>/default -m run)" |
There was a problem hiding this comment.
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, |
There was a problem hiding this comment.
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
db6b79a to
24a8b2e
Compare
| In fact, initializing default environments on other machines | ||
| will link to the environment that is already on FloxHub. |
There was a problem hiding this comment.
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
| In fact, initializing default environments on other machines | |
| will link to the environment that is already on FloxHub. |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Has that merged?
There was a problem hiding this comment.
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
24a8b2e to
08bb2df
Compare
Guide needs to be adapted with changed output of the auto onboarding flow addressed in <flox/flox#3867>.
08bb2df to
340fd46
Compare
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).