Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/SGizek/Raiku/llms.txt

Use this file to discover all available pages before exploring further.

raiku config is your interface to ~/.raiku/config.toml — the persistent settings file that controls how Raiku behaves. Rather than editing TOML by hand, the four subcommands (list, get, set, reset) let you inspect and modify every setting safely from the terminal, with automatic type coercion and validation. Changes take effect immediately on the next command invocation; there is no daemon to restart.

​
Usage

raiku config list
raiku config get KEY
raiku config set KEY VALUE
raiku config reset [--yes]

​
Subcommands

SubcommandDescription
listPrint all current configuration values in a table.
get KEYPrint the current value of one key.
set KEY VALUEUpdate KEY to VALUE and save to ~/.raiku/config.toml.
reset [--yes]Restore every key to its default value.

​
Configurable keys

KeyTypeDefaultDescription
safe_modebooltruePrompt for confirmation before executing any package build command.
auto_trustboolfalseWhen true, build commands run without prompting (overrides safe_mode).
verboseboolfalseEnable verbose/debug output for every command by default.
colorbooltrueEnable ANSI colour in CLI output.
index_urlstringGitHub raw URLURL of the remote index.json fetched by raiku sync.
raw_base_urlstringGitHub raw URLBase URL used to fetch raw package files during install.
cache_dirstring~/.raiku/cacheAbsolute path to the local package cache directory. Edit ~/.raiku/config.toml directly to change this value.
readonlyboolfalseWhen true, all cache writes are blocked (useful in CI or shared environments).

​
Accepted boolean values

When setting a boolean key, any of the following strings are accepted:
  • True: true, 1, yes, on
  • False: false, 0, no, off

​
Examples

raiku config list

​
Sample output of raiku config list

╭──── Raiku Configuration  (/home/user/.raiku/config.toml) ────╮
│ Key             Value                 Description              │
│ ─────────────────────────────────────────────────────────── │
│ safe_mode       True                  Always prompt before … │
│ auto_trust      False                 Never silently trust … │
│ verbose         False                 Enable verbose output … │
│ color           True                  Enable colored output  │
│ readonly        False                 Prevent all cache …    │
│ index_url       https://raw.githu…    URL of remote index    │
│ raw_base_url    https://raw.githu…    Base URL for fetching  │
╰────────────────────────────────────────────────────────────────╯
Setting safe_mode = false means build commands embedded in packages will execute without any confirmation prompt. Only disable safe mode if you fully trust all packages you intend to install. Enabling auto_trust = true has the same effect — build commands run silently for every package.
The readonly flag is intended for CI pipelines or shared read-only environments. When enabled, raiku install, raiku uninstall, and any other cache-writing commands are blocked. Use raiku config set readonly false to re-enable writes.

Build docs developers (and LLMs) love

Get started for freeTalk to us