Configuration

The Gofer CLI accepts configuration through a configuration file or environment variables.

When both are used, environment variables win. So if your config file sets namespace = "default" and you export GOFER_NAMESPACE=ops, the CLI uses ops. Some commands also take flags like --namespace that override both for that one command.

Environment variables

Each configuration option can be set as an environment variable by upper casing it and adding a GOFER_ prefix.

For example, setting your API token:

export GOFER_TOKEN=mysupersecrettoken
gofer token whoami

Or pointing the CLI at a different server:

export GOFER_API_BASE_URL=http://localhost:8080

Configuration file

For convenience reasons Gofer can also use a standard configuration file. The language of this file is TOML. Each option is just key = value.

Configuration file locations

Gofer reads the first of these it finds:

1. $HOME/.gofer.toml
2. $HOME/.config/gofer.toml

Development builds of Gofer read $HOME/.gofer_dev.toml and $HOME/.config/gofer_dev.toml instead, so you can work on Gofer without touching the config you use for your real server.

gofer context shows which file was read and, for each setting, whether its value came from that file, an environment variable or the default.

Configuration file options

Example configuration file

# ~/.gofer.toml
api_base_url  = "https://gofer.example.com"
namespace     = "default"
output_format = "spinner"
token         = "mysupersecrettoken"