Add CLI config file management #4

New issue

Open

opened 2026-03-16 21:14:03 +00:00 by austin · 0 comments

austin commented

2026-03-16 21:14:03 +00:00

Owner

The CLI needs to know which server to talk to and what token to use. This is the foundation for all CLI commands.

What needs to happen

Create config management (e.g., internal/cli/config.go) that reads/writes ~/.config/vektor/config.json with fields:

server_url — the Vektor server URL
token — the API token from vektor login

Add a vektor config set-server <url> command.

Respect environment variable overrides:

VEKTOR_SERVER overrides server_url
VEKTOR_TOKEN overrides token

Use os.UserConfigDir() for cross-platform config directory resolution. This is straightforward file I/O and JSON marshaling — a good early Go exercise.

The CLI needs to know which server to talk to and what token to use. This is the foundation for all CLI commands. ## What needs to happen Create config management (e.g., `internal/cli/config.go`) that reads/writes `~/.config/vektor/config.json` with fields: - `server_url` — the Vektor server URL - `token` — the API token from `vektor login` Add a `vektor config set-server <url>` command. Respect environment variable overrides: - `VEKTOR_SERVER` overrides `server_url` - `VEKTOR_TOKEN` overrides `token` Use `os.UserConfigDir()` for cross-platform config directory resolution. This is straightforward file I/O and JSON marshaling — a good early Go exercise.