srekit config¶

Manage ~/.srekit.yaml — the optional user configuration that holds author identity and an optional default templates directory.

`config init`¶

Walk the user through filling in ~/.srekit.yaml interactively (TTY) or non-interactively (--yes, piped stdin).

srekit config init                          # interactive
srekit config init --yes                    # non-interactive, defaults from git config
srekit config init --force                  # overwrite existing file
srekit --config ./my.yaml config init       # custom path (honors root --config)

Flags¶

Flag	Description
`--author NAME`	Override resolved author
`--email EMAIL`	Override resolved email
`--templates-dir PATH`	Default templates directory to bake into config
`--force`	Overwrite existing config
`--yes` / `-y`	Non-interactive; accept defaults

Defaults¶

If you omit a flag, srekit fills the default from git config user.name / git config user.email. If neither flag nor git config is set and the command is non-interactive, it errors out instead of writing an invalid file.

Output¶

The generated file looks like:

# srekit user config — generated by `srekit config init` (safe to edit by hand)
author: Mikhail Savin
email: jtprogru@gmail.com
# templates_dir: ~/.srekit/templates  # optional; uncomment to override embedded templates

File mode is 0o600 (user-only). templates_dir: is emitted as a commented-out hint when unset — uncomment to enable, or pass --templates-dir PATH at init time to bake in a real value.

Target path¶

The default target is ~/.srekit.yaml. If you pass --config FILE on the root command (srekit --config FILE config init), the file is written there instead — useful for multi-tenant setups or CI scratch.