twc-rs

A fast, single-binary CLI and interactive TUI dashboard for Timeweb Cloud.

Servers, databases, S3, Kubernetes, balancers, domains, firewalls and more — managed from one native binary. No Python, no pip, no virtualenv.

English · Русский

Table of contents

• Why twc-rs
• The dashboard
• Install
  • Direct downloads
  • Supported platforms
• Authenticate
• Usage
• Shell completions
• Benchmarks
• Building from source
• License

Why twc-rs

The official Timeweb CLI (timeweb-cloud/twc) is a Python application. twc-rs matches its command coverage and beats it on speed, footprint, and experience — every number below is measured, not estimated (see docs/COMPARISON.md for the full report and the reproducible benchmark).

Measured on an AMD Ryzen AI MAX+ 395 (Linux 7.1, rustc 1.96) against twc-cli v2.15.2, 50 runs each. The Python tool pays ~350 ms of interpreter and import startup before any application code runs.

The dashboard

The headline feature the Python CLI does not have: a live, k9s-style TUI (twc-rs dashboard).

• Context action menu per resource (reboot / shutdown / clone / delete) with a confirmation step for destructive actions.
• Create resources and switch account profile without leaving the dashboard.
• Live per-resource metrics (CPU / RAM / network sparklines), fetched off the UI thread so input never blocks on the network.
• Drill into a project to see the resources it contains; live event log.
• Customizable layout, hide-empty-tabs, 4 true-color themes and EN/RU — all persisted to the config file.

Install

Pick the channel that fits your platform. Every channel ships with the interactive TUI dashboard enabled by default. For a lean, headless CLI, build without it: cargo install twc-rs --no-default-features --features auth.

Direct downloads

Prebuilt, checksummed archives are attached to the latest release — pick your platform (each archive has a matching .sha256):

The one-line installer detects your OS/arch, downloads the matching tarball from the latest GitHub release and installs to ~/.local/bin (or /usr/local/bin when writable). The .deb package is attached to every tagged release automatically.

twc-rs is not in the official Debian/Ubuntu (apt install twc-rs) or Arch (pacman -S twc-rs) repositories — those require distro maintainership. Use the AUR package, the .deb, the installer, or cargo install.

Supported platforms

Every tagged release ships prebuilt, checksummed binaries for:

Authenticate

twc-rs auth flow                       # guided browser flow, stored in the OS keyring
# or
twc-rs config set-token --token <TOKEN>

The token is resolved from the OS keyring, the config file, --token, or the TWC_TOKEN environment variable, in that order. Multiple accounts are supported via named profiles:

twc-rs config set-token --profile staging --token <TOKEN>
twc-rs --profile staging server list

Usage

Every resource type is a subcommand; run twc-rs <group> --help to see its actions and flags.

twc-rs server list                        # list cloud servers
twc-rs server info --id 12345             # server details
twc-rs database list -f json              # JSON output
twc-rs ssh attach --server 12345 --key 42 # attach an SSH key to a server
twc-rs project resources --id 678         # drill into a project
twc-rs apps logs my-api --today           # app runtime logs by name or ID (also --since, --tail)
twc-rs apps list-deploys my-api           # deploy history, newest first
twc-rs apps deploy-logs my-api            # build/deploy logs of the latest deploy
twc-rs doctor                             # detect conflicting installs in PATH
twc-rs update                             # self-update via the detected package manager
twc-rs dashboard                          # interactive TUI (k9s-style)

Resource groups: server, database, s3, kubernetes, registry, balancer, domain, firewall, apps, image, ip, vpc, ssh, project, account. The full command coverage versus the official CLI is in docs/COMPARISON.md, and the complete CLI reference — auto-generated from the command definitions on every deploy — lives at raprogramm.github.io/twc-rs.

Global flags:

Shell completions

twc-rs completions nushell > ~/.config/nushell/completions/twc-rs.nu
twc-rs completions zsh     > ~/.zfunc/_twc-rs
twc-rs completions bash    > /etc/bash_completion.d/twc-rs

Supported shells: bash, zsh, fish, powershell, elvish, nushell. The AUR package ships completions for bash, zsh, fish and nushell in the standard vendor directories, so they work out of the box.

Dynamic completions

Static scripts complete commands and flags; the dynamic engine also completes live values — twc-rs apps logs <TAB> offers your actual apps by name and ID, fetched from the API (silently skipped when offline).

Register it instead of (or on top of) the static script:

Nushell keeps the static script (the dynamic engine does not support it yet).

Benchmarks

All performance claims are reproducible. docs/COMPARISON.md documents the test environment and methodology; rerun it with:

cargo build --release --features tui
python3 -m venv /tmp/twcbench && /tmp/twcbench/bin/pip install twc-cli
benches/compare.sh ./target/release/twc-rs /tmp/twcbench/bin/twc

Prefer CI? The Benchmarks workflow runs the same comparison on demand (Actions → Benchmarks → Run workflow) and prints the head-to-head table in the run summary. It is manual only — never on push — so it never slows down regular CI.

Building from source

git clone https://github.com/RAprogramm/twc-rs && cd twc-rs
cargo build --release                   # full binary (TUI dashboard is on by default)
cargo install --path .                  # install from the checkout
# headless, no TUI:
cargo build --release --no-default-features --features auth

Requires Rust 1.96+. The crate is linted under clippy pedantic + nursery and the SDK is generated from the official OpenAPI spec via timeweb-rs.

License

MIT © RAprogramm