feat: flox pull --copy in sharing guide #29
Conversation
|
🚀 Deployed on https://66edece4ae905e7c629e3379--floxdocs.netlify.app |
|
🚀 Deployed on https://66ededa43e2f92727b948fc9--floxdocs.netlify.app |
There was a problem hiding this comment.
This is great!
Where do you think the other use case of pull --copy should go? When you want to sever the connection to an env you've pushed (and possibly deleted or renamed). Part of the man page for flox pull for sure, but I'm not sure it fits on the sharing guide. Wdyt?
|
|
||
| ### Pulling a remote environment without connecting to FloxHub | ||
|
|
||
| Sometimes you may want to create a FloxHub remote environment that serves as a template starting point for your project but will grow to have different environment definitions across multiple projects. |
There was a problem hiding this comment.
Sometimes you may want to create a FloxHub remote environment that serves as a template starting point
Depending on who you address i think it might find a broader audience if you said
"Sometimes you want to use a FloxHub remote environment as a template, a starting point for your project."
| Sometimes you may want to create a FloxHub remote environment that serves as a template starting point for your project but will grow to have different environment definitions across multiple projects. | ||
| In this cases, you may want to [`flox pull --copy`][flox_pull] instead of [`flox pull`][flox_pull]. | ||
|
|
||
| [`flox pull --copy`][flox_pull], like [`flox pull`][flox_pull], will create a `.flox` folder to the directory you are in. However, this environment will **not be linked to FloxHub**. |
There was a problem hiding this comment.
| [`flox pull --copy`][flox_pull], like [`flox pull`][flox_pull], will create a `.flox` folder to the directory you are in. However, this environment will **not be linked to FloxHub**. | |
| [`flox pull --copy`][flox_pull], like [`flox pull`][flox_pull], will create a `.flox` folder to the directory you are in. However, this environment will **not be linked to FloxHub**, instead it will be entirely local as if created from scratch using [`flox init`][flox_init] and can be pushed under a new name or owner. |
or something similar, i think "not be linked to floxhub" is not making the implications obvious
Adds
flox pull --copyto sharing guide