nimbus-cli assumes that
xcrun are on the
PATH. If they are not (or aren't spelled
adb.exe), then you can configure them via the
XCRUN_PATH environment variables.
export ADB_PATH="/Applications/Android Studio.app/platform-tools/bin/adb"
Experimenter URLs are used for accessing experiments via the
/api/v6 endpoints. They're hardcoded into
nimbus-cli for both stage and production versions. However, just occassionally you may want to change these URLs.
e.g. for a local development version of experimenter with
Remote Settings URLs
URLs for Remote Settings are also hardcoded into
nimbus-cli for both the stage and release versions. Like Experimenter, you may occassionally want to change these URLs.
This has been helpful in the past when trying to debug a problem with CDN, or Remote Settings has moved.
Note: while the Remote Settings represents what the live apps see, there is approximately 1 hour latency between changing an experiment on Experimenter and it being synced to Remote Settings.
Manifest Cache Directory
The manifest downloading happens on each invocation of the
You can speed this up by setting directory as the cache for downloading the manifests:
However, it should be noted that for some files (especially downloading from
main), they change even though the URL remains the same.
For this, you should consider putting into your
.profile file something like
export NIMBUS_MANIFEST_CACHE=$HOME/.local/state/fml/$(date -Idate)
so as to only use the cache for one day.
Suppressing update checking
nimbus-cli periodically checks for a new version. This can be disabled by setting the following environment variable.
The server host and port
By default, the server that is started with
nimbus-cli start-server uses the machine's network interface to derive the external IP address.
Communicating with the server is done by other instances of
nimbus-cli by posting to the
/post endpoint. The port and host can be configured with the following environment variables.