Skip to content

flox push command


flox-push - send environment to FloxHub


flox [<general-options>] push


Move an environment’s manifest to FloxHub or sync local changes to an environment to FloxHub.

After pushing, the remote environment can be referred to as <owner>/<name>.

A path environment contains a manifest file and lock file which are stored locally and possibly committed to version control. Pushing the environment moves the manifest and lock file to FloxHub, leaving a reference to the revision of the environment stored locally.

Once the environment has been pushed, it can be used directly with the --remote option, or it can be used and edited locally before syncing with flox push. See flox-edit(1), flox-install(1), and flox-remove(1) for editing the environment.

In the same way as a git repo, local changes to an environment that has been pushed may diverge from the environment on FloxHub if flox push is run from a different host. Passing --force to flox push will cause it to overwrite any changes on FloxHub with local changes to the environment.


Push Options

-d, --dir
Directory to push the environment from (default: current directory).

-o, --owner
Owner to push push environment to (default: current user).

-f, --force
forceably overwrite the remote copy of the environment.

General Options

-h, --help
Prints help information.

The following options can be passed when running any flox subcommand but must be specified before the subcommand.

-v, --verbose
Increase logging verbosity. Invoke multiple times for increasing detail.

-q, --quiet
Silence logs except for errors.