Skip to main content
gat route is Experimental: its interface or behavior may change or be removed between releases. See Feature lifecycle.
Routes map tracked path prefixes to named remotes independently of mount ownership. The most-specific matching path wins; route names identify rules, not their priority. A selects storage for a subtree. An explicit --remote NAME overrides routing for one command. See Using multiple remotes for setup, backups, and moving content between stores. Reads combine routes from all configuration layers. Changes target one layer and leave mounts, tracked entries, and remote definitions intact. See Config inheritance for local overrides, and gat remote to manage the storage locations themselves.

Usage

Subcommands

gat route list

gat route add

gat route update

gat route remove

gat route show

gat route add

Route a path and its descendants to an existing remote. The most-specific matching path wins.

Usage

Examples

Send a tracked subtree to a named remote.

gat route list

List effective routes. The synthetic * row shows the default remote fallback.

Usage

Examples

Show named routes and the default fallback.

gat route remove

Remove a storage rule. Tracked files, mounts, and remote definitions are kept.

Usage

Examples

Delete the route definition. gat route rm datasets is also accepted.

gat route show

Show the route path, remote, and defining scope.

Usage

Examples

Inspect the route’s normalized path, remote, and defining scope.

gat route update

Change the path or remote in the defining scope. Omitted settings are preserved.

Usage

Examples

Update route properties without changing its stable name.