You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/tutorials/sharing-environments.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,9 +73,9 @@ $ flox push
73
73
74
74
You can also view your new environment in FloxHub's web application.
75
75
76
-
### Directly activating a FloxHub environment
76
+
### Using a local copy of a FloxHub environment
77
77
78
-
As the recipient, you can use the environment in a variety of ways depending on your needs. If you trust the user sending the environment, [`flox activate -r username/environment`][flox_activate] the environment directly. The first time you do this you will be offered a choice about trusting this user in the future.
78
+
As the recipient, you can use the environment in a variety of ways depending on your needs. If you trust the user sending the environment, [`flox activate -r username/environment`][flox_activate] the environment directly. This will implicitly pull the environment and create a local copy of the environment if it doesn't already exist. The first time you do this you will be offered a choice about trusting this user in the future.
79
79
80
80
```console
81
81
$ flox activate -r youruser/example-project
@@ -100,9 +100,9 @@ telnet (GNU inetutils) 2.5
100
100
...
101
101
```
102
102
103
-
### Pulling a FloxHub environment (and pushing updates)
103
+
### Pulling a FloxHub environment into a directory (and pushing updates)
104
104
105
-
If you intend to use the same environments across multiple projects or you want to stage changes before pushing to FloxHub, you may want to [`flox pull`][flox_pull] it instead.
105
+
If you intend to commit the environment to version control, you may want to [`flox pull`][flox_pull] it instead.
106
106
107
107
[`flox pull`][flox_pull] adds a `.flox` folder to the directory you are in that is linked to the FloxHub environment. When using a [FloxHub][floxhub_concept] environment in multiple projects it allows centralized management of the dependencies used across these projects. Run `flox pull` to sync the latest changes from FloxHub:
108
108
@@ -125,8 +125,6 @@ $ flox push
125
125
Use 'flox pull youruser/example-project' to get this environment in any other location.
126
126
```
127
127
128
-
Changes are made to your local copy first. Use `flox push` to sync them to FloxHub so others can access the updates.
129
-
130
128
!!! note "Note"
131
129
Right now, only environment owners can push edits to their environments.
0 commit comments