Fig's configuration is done via a series of JSON files that are each expected to contain a single object/dictionary. When Fig wants a value for a particular name, it searches the list and stops at the first value it finds. Note that it is possible to specify null as a value and that will override any value in a lower-priority file.

At present, there are three files that Fig looks at. They are, in order from highest to lowest priority, the value of the --figrc option, ~/.figrc, and in _meta/figrc in the repository, i.e. $FIG_REMOTE_URL/_meta/figrc. You can suppress use of ~/.figrc via the --no-figrc command-line option and the use of $FIG_REMOTE_URL/_meta/figrc via the --no-remote-figrc option.

A URL for a remote repository to use when the FIG_REMOTE_URL environment variable is not set. Unsurprisingly, specifying a value for this in $FIG_REMOTE_URL/_meta/figrc is pointless, but it can be useful in ~/.figrc.

An array of names of environment variables to include in comments at the top of published packages.

A path to a Log4r configuration file (YAML or XML). Overridable via the --log-config command-line option.

An array of named warnings to turn off. Values currently looked for are "include statement missing version" and "unused retrieve". Thus, to avoid specifying the --suppress-warning-include-statement-missing-version command-line option all the time, you could have the following in ~/.figrc:

{
    "suppress warnings": ["include statement missing version"]
}

A string or array of strings of base URLs to allow in asset statements.

{
    "url whitelist": ["http://host1/whatever", "ftp://yadda/"]
}