If no services are specified, stops all running services and starts new
services using the latest build of the environment. If one or more
services are running, then the specified services are started using the
service config that the running services were started with.
If one or more services are running, the specified services will be
started using the service config that the running services were started
with.
When all services are restarted, they are started from an ephemeral
activation that uses the latest build of the environment. This may not
be the build of the environment that your shell has activated, so the
environment variables present for services may be different from the
ones in your shell. To ensure that your shell and the services have the
same environment, reactivate your environment after making edits to the
manifest.
An error is displayed if the specified service does not exist.
OPTIONS
-d, --dir
Path containing a .flox/ directory.
<name>
The name(s) of the services to restart.
Environment Options
If no environment is specified for an environment command, the
environment in the current directory or the active environment that was
last activated is used.
-d, --dir
Path containing a .flox/ directory.
-r, --remote
A remote environment on FloxHub, specified in the form <owner>/<name>.
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.
EXAMPLES:
Restart a single service:
$ flox services restart myservice
✅ Service 'myservice' restarted.
Restart all services:
$ flox services restart
✅ Service 'service1' restarted.
✅ Service 'service2' restarted.
✅ Service 'service3' restarted.