flox pull command¶
<general-options> ] pull [
<options> ] [ --force ] [ (
-m | --main) ]
git) Push or pull metadata to the environment’s
repository, and in the
pull case also proceed to render the
environment. With this mechanism environments can be pushed and pulled
between machines and within teams just as you would any project managed
--force argument flox will forceably overwrite either the
upstream or local copy of the environment based on having invoked
flox (push|pull) will operate on the
“floxmain” branch, pulling user metadata from the upstream repository.
Cannot be used in conjunction with the
flox pull will fetch and incorporate
the latest metadata from upstream but will not actually render or create
links to environments in the store. (Flox internal use only.)
Many flox commands wrap Nix commands of the same name, and will
correspondingly pass on options and arguments directly to the underlying
nix invocation. For more information on the options supported by
specific Nix commands please invoke
flox nix <command> help.
The following options are used specifically by
flox and must be
specified before the
Verbose mode. Invoke multiple times for increasing detail.
Debug mode. Invoke multiple times for increasing detail.
flox installation prefix / Nix store path. (flox internal use
Force execution in
flox-bash (flox internal use only.)
The following option is supported by environment commands:
Selects flox environment to be modified or used. If not provided then flox will fall back to using the default environment.
[ (-m | --main ) ]
operate on the “floxmain” branch, pull user metadata from the upstrea repository. Cannot be used in conjunction with the
[ --force ]
forceably overwrite the upstream copy of the environment
[ --no-render ]
do not render or create links to environments in the store (Flox internal use only.)