Skip to content

Commit 99dba53

Browse files
mkenigszmitchell
authored andcommitted
docs: rework sharing since dropping remote
Some of the distinctions betweeen when to use `-r` vs `-d` have changed
1 parent 621cc23 commit 99dba53

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

docs/tutorials/sharing-environments.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -73,9 +73,9 @@ $ flox push
7373

7474
You can also view your new environment in FloxHub's web application.
7575

76-
### Directly activating a FloxHub environment
76+
### Using a local copy of a FloxHub environment
7777

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.
7979

8080
```console
8181
$ flox activate -r youruser/example-project
@@ -100,9 +100,9 @@ telnet (GNU inetutils) 2.5
100100
...
101101
```
102102

103-
### Pulling a FloxHub environment (and pushing updates)
103+
### Pulling a FloxHub environment into a directory (and pushing updates)
104104

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.
106106

107107
[`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:
108108

@@ -125,8 +125,6 @@ $ flox push
125125
Use 'flox pull youruser/example-project' to get this environment in any other location.
126126
```
127127

128-
Changes are made to your local copy first. Use `flox push` to sync them to FloxHub so others can access the updates.
129-
130128
!!! note "Note"
131129
Right now, only environment owners can push edits to their environments.
132130

0 commit comments

Comments
 (0)