otty / dotfiles

All tools/sake

sake

sake is a command runner for local and remote hosts.

Detected by sake | macOS, Linux, Windows |sakecli.com

Sync it sake.toml

Sync rules

What travels, what stays, what never leaves

sake in your home directory Every rule on this page, by file

servers.*.identity_fileknown_hosts_file

Each machine keeps its own copy of these.

servers.*.password

Lifted into your secret store; the rest of the file syncs.

servers.*.identity_fileknown_hosts_file

Each machine keeps its own copy of these.

servers.*.password

Lifted into your secret store; the rest of the file syncs.

Only what the catalog names. A directory that syncs brings everything inside it except what is listed as excluded here.

apps/sake.tomlThe file this page is generated from

id = "sake"

name = "sake"

homepage = "https://sakecli.com"

description = "sake is a command runner for local and remote hosts."

# The project's own mark, from its home page.

icon = "https://sakecli.com/img/logo.svg"

detect = ["sake"]

# There are several unrelated tools called `sake`; this entry is alajmo/sake,

# the Go task runner documented at sakecli.com, which is the one on the

# binary-name list. Its docs/config.md "Files" section: sake "will import (if

# found) a config file from: Linux: $XDG_CONFIG_HOME/sake/config.yaml or

# $HOME/.config/sake/config.yaml if $XDG_CONFIG_HOME is not set". The macOS and

# Windows spellings come from the code rather than that sentence, which is

# stale: getUserConfigFile() in core/dao/config.go takes Go's

# os.UserConfigDir() — ~/.config, ~/Library/Application Support, %APPDATA%,

# which is [appData] — joins "sake", and tries config.yaml then config.yml. The

# project's own sake.yaml belongs to the repository, not here.

paths = [

"[appData]/sake/config.yaml",

"[appData]/sake/config.yml",

]

exclude = []

# The user config is servers, tasks, themes and specs. Only the per-server

# password is a credential, and it is lifted out below.

secret = []

# Read once when a sake command starts.

side_effect = false

# docs/config.md documents a per-server `password`: "Set password. Accepts

# either a string or a shell command". Both names are listed: config.yml is the

# same file under the other extension sake accepts, which the sibling check

# cannot see from the name, so it goes here by hand.

[[secret_paths]]

file = [

"[appData]/sake/config.yaml",

"[appData]/sake/config.yml",

]

match = { key_path = ["servers.*.password"] }

# `identity_file` is the path to a private key as it sits on this machine, and

# `known_hosts_file` is documented as defaulting to "$HOME/.ssh/known_hosts" —

# both are absolute once written out. The servers, tasks and themes around them

# are what the user wants carried everywhere.

# Both name this machine's own key material and trust file, which the user

# needs back to rebuild the box and which mean nothing on another.

[[machine_lines]]

file = [

"[appData]/sake/config.yaml",

"[appData]/sake/config.yml",

]

match = { key_path = ["servers.*.identity_file", "known_hosts_file"] }

scope = "backup"

Use it with your dotfile manager

Same data, in the shape your tool already reads

Opens Otty and adds this tool to what it syncs

Opens otty://sync/add/sake. Otty ships with this catalog, so the link only has to name the tool — nothing is downloaded.

Every one of these is generated from the same rules as this page. None of them splits servers.*.identity_file and known_hosts_file for you — that part is Otty’s own sync, or a template you write by hand.