본문으로 건너뛰기
AI NEWS JOURNAL
Hacker News Show HNAI NEWS / JOURNAL

Show HN: Crow – High density control plane for Linux servers

Article URL: https://github.com/errorware/crow Comments URL: https://news.ycombinator.com/item?id=50530288 Points: 1 # Comments: 0

번역 서비스가 일시 중지되어 원문을 표시합니다.

Native Linux Server Manager over SSH A high-density operator terminal built with Rust and GPUI. Overview • What it does • Security • Providers & Plugins • Getting Started • Keyboard Shortcuts • Acknowledgements • License Crow is in active development. Features change or move between releases, things break, and the vault format can change. Try it on servers you can afford to experiment with, not production. Bug reports are welcome. Overview Crow is a native desktop control plane for Linux server management over plain SSH. Broadly, it gives you what you'd get from a traditional shell, but with the bells and whistles of a dashboard-style UI. It bridges the gap between the grey-bearded SSH artisan and the neophyte, without taking anything away from either. I originally envisioned it as a one-stop shop for all my server management needs. Over the years I've used every combination of shells, shell wrappers, IDEs, external services, web apps and more esoteric things to get done what I can now do in Crow alone. I have way more freedom now than with any single product before. I can deploy a VM, provision and harden it, see patch states, and follow logs and services, without losing the ability to just jump into a shell and do things by hand when that gets me there faster. None of Crow's niceties are mandatory. You can keep working however you did before, and nothing gets in the way. That's by design. Of course, design and usability are subjective, so you're entitled to think it sucks too. It's agentless: Crow talks to your servers over plain SSH, reuses one connection per server, and never installs anything on them. The feel is borrowed from k9s and lazygit, dense and keyboard-driven, just drawn as a GPU-accelerated GUI. I've tested it on Ubuntu, Fedora and macOS with no issues so far. It could probably run on Windows, but I didn't want to complicate my life with PATHs and WSL, so that's backlogged for now. Other quality of life improvements include: crow-config, a small library that parses different config file formats into one common structure Crow understands, so it can show them as structured, validated rows instead of raw text. This is easier said than done, so of course you can always just go and edit your configs the way you always did. A built-in plugin system for extensibility. A fleet map: your managed infrastructure in a more convenient representation. I'm working on editing things from there and adding more nodes and categories (users, networks, etc.) to the visualisation. Website: crow.rs · Community: forum.errorware.net What it does All enrolled servers with health, environment (PROD / STAGE / DEV / LAB) and region (from the cloud provider, metadata service, or set by you). Optional offline IP-to-country lookup via DB-IP; no addresses leave your machine. Add Server verifies the host key, can bootstrap a password-only server onto Crow's SSH key, and reads distro, kernel, memory and disk. Import and provision instances from AWS EC2, Linode, and UpCloud. Local Lab: Spin up or connect local test environments and sandboxes to test configs, playbooks, and commands safely without risking live fleets. Archive servers you no longer manage; their data is purged after a set window. Fleet Setup Multi-server changes preview what they'll do, run one server at a time, and stop at the first failure. Groups, policies and the fleet map, with posture-check risks Patching (apt, dnf, apk) with orderly reboots Rollouts of commands or config files, with a per-server diff first Config drift detection and search across every file Crow has read SSH and firewall hardening, with fixes that verify a fresh login still works or roll back Certificates, user accounts and keys, cross-server log search, external checks (HTTP/TCP/DNS), incidents, DR plans, team roles Audit log of every change Crow made Per server Overview: live CPU, memory, disk, network, pending updates, and CVEs from OSV History: 24h / 7d metrics, sampled while Crow runs Services, processes, sockets: search, filter, act with confirmation Containers: Discover Docker and Podman containers on the host — view health, CPU/memory usage, port bindings, stream container logs, and inspect state without Docker Desktop. Dokku: Manage apps, services, domains, scaling, environment variables, and live logs on Dokku servers. Logs: journalctl with filters, plus optional AI explanations Configs: sshd_config, /etc/hosts, pg_hba.conf and ufw as structured rows via crow-config. Every change is a revision you can roll back; writes are atomic. Firewall: edit ufw and firewalld; read-only nftables/iptables. A lock-out guard asks for confirmation before anything that would block Crow's SSH port. Terminal with tabs and split panes Files: browse, view, chmod, edit in nano (via sudoedit when needed) Users and cron Danger Zone: destructive actions behind a typed keyword. Power and snapshots go through the provider when linked, so they work with SSH down. Fleet-wide rolling reboot, session revocation and host key rotation (verified, or reverted). Settings Timeouts, auto-lock, retention, appearance, cloud providers, AI providers ("Clankers": Anthropic or OpenAI-compatible), background image, font size and language. Languages English by default. A language pack is a single .ftl file in ~/.config/crow/languages/. Spanish and Japanese ship in languages/; see languages/README.md to write one. Security Crow holds provider tokens, AI keys and SSH access to your fleet, so it makes you pick a security stance. The titlebar badge always shows which one you're in. Either way: Secrets are encrypted with ChaCha20-Poly1305; the data key never touches disk unencrypted. Secrets never appear in argv, logs or errors, and are wiped from memory when no longer needed. Host keys are always checked strictly; agent and X11 forwarding are always off. Not encrypted: the rest of crow.db and your SSH keys in ~/.ssh. Full details in docs/security.md. Providers and plugins Plugins are described by crow-config manifests. A plugin implements a category (provider.hosts today, provider.dns next) and declares the capabilities it supports; Crow only offers what's declared. Providers are compiled in as cargo features (provider-linode, provider-upcloud, provider-aws, all on by default). Tokens and credentials live only in the encrypted vault. Your own plugins go in ~/.config/crow/plugins/ as a folder with a plugin.toml and scripts. Crow shows every command a plugin can run before you accept it, disables it if its files change, asks before making changes, and logs every run. Plugins can act on a single server, across the fleet with a canary, or locally against a generated inventory (e.g. Ansible). Validate one with crow --check-plugin . Examples in plugins/, docs in docs/plugins.md. Repository layout crow/ ├── src/ # the app ├── crates/ │ ├── crow-provider-core/ # provider contracts: Provider, ListInstances, PowerControl, Snapshots, Provision; curl-based HTTP │ ├── crow-provider-aws/ # AWS EC2 (IMDS, SigV4, instances, snapshots, provisioning) │ ├── crow-provider-linode/ # Linode API v4 │ └── crow-provider-upcloud/ # UpCloud API 1.3 ├── assets/ # icons, flags, distro logos, fonts (each with its license), i18n/en.ftl ├── languages/ # language packs (Spanish, Japanese) and how to write one └── docs/ crow-config has its own repository. Getting Started Download Prebuilt binaries for Linux (x86_64) and macOS (Apple Silicon) are attached to each GitHub release, alongside SLSA provenance (.intoto.jsonl) you can check with slsa-verifier. Linux: unpack and run the installer. It puts crow in ~/.local/bin and adds Crow (with its icon) to your app launcher; ./install.sh --uninstall removes it. tar -xzf crow-linux-x86_64.tar.gz cd crow-linux-x86_64 && ./install.sh macOS: unpack crow-macos-arm64.tar.gz and drag Crow.app to Applications. The app is ad-hoc signed but not notarized, so Gatekeeper blocks the first launch: right-click it and choose Open, or clear the quarantine flag once: xattr -dr com.apple.quarantine /Applications/Crow.app Updates: Crow checks GitHub releases once a day and shows vX available next to its version (disable in Settings → General). Auto-install is opt-in and only runs after slsa-verifier (must be on your PATH) confirms the release's provenance. Only an installed copy (~/.local/bin/crow, Crow.app) is replaced, and Crow offers a restart rather than restarting itself. Prerequisites A Rust toolchain (1.85+), native windowing and font libraries, and curl (Crow uses it for provider and AI requests). # Fedora / Bazzite sudo dnf install fontconfig-devel libxkbcommon-devel libxcb-devel wayland-devel # Ubuntu / Debian sudo apt install libfontconfig1-dev libxkbcommon-dev libxcb1-dev libwayland-dev For the Open stance on Linux you need a Secret Service provider (GNOME Keyring or KWallet); most desktops have one running. Crow uses JetBrains Mono: brew install --cask font-jetbrains-mono # macOS brew install font-jetbrains-mono # Linux (Homebrew) Build & Run git clone https://github.com/errorware/crow.git cd crow cargo test --workspace cargo run --release Keyboard Shortcuts Ctrl works wherever ⌘ is shown. Acknowledgements Crow builds on GPUI, alacritty_terminal, the RustCrypto crates, SQLite and many more, and ships Tabler Icons, flag-icons, Dashboard Icons and JetBrains Mono. ACKNOWLEDGEMENTS.md lists them all with their licenses; the bundled assets carry their own in assets/. Crow is licensed under the MIT License. Free and open source for personal and commercial use.

자료 출처

원문 읽기 ↗

관련 주제

← 전체 소식 이어 읽기