termainer 0.4.0__tar.gz → 0.5.1__tar.gz

termainer-0.5.1/MANIFEST.in

@@ -0,0 +1 @@
+recursive-include src/termainer/ui *.tcss *.png

{termainer-0.4.0 → termainer-0.5.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: termainer
-Version: 0.4.0
+Version: 0.5.1
 Summary: Container observability and operations directly from your terminal
 Author: Alan Stefanov
 License: MIT
@@ -31,6 +31,7 @@ Building scalable platforms, leading teams, and optimizing cloud operations.
 [![LinkedIn](https://img.shields.io/badge/LinkedIn-Alan_Stefanov-blue?style=for-the-badge&logo=linkedin)](https://www.linkedin.com/in/alanstefanov/)
 [![Email](https://img.shields.io/badge/Email-alan.emanuel.stefanov@gmail.com-red?style=for-the-badge&logo=gmail)](mailto:alan.emanuel.stefanov@gmail.com)
 [![GitHub](https://img.shields.io/badge/GitHub-AlanStefanov-black?style=for-the-badge&logo=github)](https://github.com/AlanStefanov)
+[![Web](https://img.shields.io/badge/Web-astefanov.com-10b981?style=for-the-badge&logo=vercel)](https://astefanov.com)
 
 </div>
 
@@ -159,9 +160,84 @@ Depending on how you installed Termainer:
 
 ---
 
+## Quick Start
+
+```bash
+# Just run it — Termainer auto-detects local Docker, Podman, kubectl, or oc
+termainer
+
+# If no local runtime is found, configure remote servers via ~/.ssh/config
+# (see below) and restart, or click any technology card to probe SSH servers
+```
+
+Termainer works **with zero configuration** for local environments. For remote servers, just add entries to `~/.ssh/config` — no config file needed.
+
+---
+
 ## Configuration
 
-Termainer uses a **YAML config file** to manage multiple servers. Create `~/.config/termainer/config.yaml`:
+### SSH Config Auto-Discovery (Recommended)
+
+Termainer automatically discovers servers from your **`~/.ssh/config`** file. This is the **recommended approach** — no YAML or `.env` file needed.
+
+Simply define your remote servers in `~/.ssh/config`:
+
+```
+Host prod-web
+    HostName ec2-54-123-45-67.us-east-1.compute.amazonaws.com
+    User ubuntu
+    IdentityFile ~/.ssh/production.pem
+
+Host staging-k8s
+    HostName k8s-staging.example.com
+    User admin
+    IdentityFile ~/.ssh/staging-key
+
+Host dev-docker
+    HostName 192.168.1.100
+    User devuser
+    IdentityFile ~/.ssh/dev-key
+```
+
+Then launch Termainer — all SSH entries appear in the server dropdown automatically:
+
+```bash
+termainer
+```
+
+When you select a technology card (e.g. "Kubernetes"), Termainer shows a **server selection dialog** with checkboxes for all configured SSH servers. Selected servers are probed **in parallel** for the chosen provider, and successful connections open the dashboard. Server preferences are cached in `~/.config/termainer/provider_servers.json`.
+
+You can also **add and remove servers directly from the UI** via the "Manage servers" button. Custom servers are persisted in `~/.config/termainer/servers.json`.
+
+> **⚠️ Docker/Swarm note:** For Docker and Swarm over SSH, Termainer uses SSH port
+> forwarding to tunnel the remote Docker socket to a local Unix socket. The remote
+> user must have access to the Docker daemon (be in the `docker` group) without `sudo`.
+> Kubernetes, Podman, and OpenShift commands run directly over SSH, no tunnel needed.
+
+### Dashboard server switching
+
+Within a dashboard, switching servers only probes the **current provider** on the target server (no multi-probe). If the server doesn't have that provider, a notification is shown and the dashboard stays on the current server.
+
+#### SSH Authentication Methods
+
+| Method | How to use |
+|---|---|
+| **Key (`.pem`)** | Set `IdentityFile` in `~/.ssh/config` |
+| **Password** | `--ssh-password 'mypass'` or `TERMAINER_REMOTE_PASSWORD` in `.env` (requires `sshpass`) |
+
+For password-based auth, install `sshpass`:
+
+```bash
+# Debian/Ubuntu
+sudo apt install sshpass
+
+# RHEL/CentOS/Fedora
+sudo yum install sshpass
+```
+
+### Multi-Server via config.yaml (Advanced)
+
+For advanced setups, create `~/.config/termainer/config.yaml`:
 
 ```yaml
 lang: en
@@ -186,9 +262,9 @@ servers:
 
 See the full [Configuration Reference](guide/configuration-reference.md) for all options.
 
-### Quick single-server (.env)
+### Single-server via .env
 
-For a single remote server, you can use `.env` or CLI flags instead:
+For a quick single remote server, use `.env` or CLI flags:
 
 ```bash
 termainer --host ec2-54-123-45-67.us-east-1.compute.amazonaws.com \
@@ -223,93 +299,41 @@ termainer --provider openshift
 
 ### Remote (SSH)
 
-Connect to remote servers running Docker or Kubernetes:
-
 ```bash
-# Using CLI flags
+# Using --host flag (single server)
 termainer --host ec2-54-123-45-67.us-east-1.compute.amazonaws.com \
           --ssh-user ubuntu \
           --ssh-key ~/.ssh/production.pem \
           --provider docker
 
-# Using .env (recommended for frequent use)
+# Using .env (recommended for frequent single-server use)
 cp .env.example .env
 # Edit .env with your server details
 termainer
 ```
 
-#### SSH Config Auto-Discovery (Recommended)
-
-Termainer automatically discovers servers from your **`~/.ssh/config`** file. This is the **recommended approach** for multi-server setups—no `.env` file needed!
-
-Simply define your remote servers in `~/.ssh/config`:
-
-```
-Host prod-web
-    HostName ec2-54-123-45-67.us-east-1.compute.amazonaws.com
-    User ubuntu
-    IdentityFile ~/.ssh/production.pem
-
-Host staging-k8s
-    HostName k8s-staging.example.com
-    User admin
-    IdentityFile ~/.ssh/staging-key
-
-Host dev-local
-    HostName 192.168.1.100
-    User devuser
-    IdentityFile ~/.ssh/dev-key
-```
-
-Then launch Termainer:
-
-```bash
-termainer
-```
-
-You'll see all servers from your SSH config automatically loaded in the server dropdown. No configuration files needed!
+For multi-server setups, use `~/.ssh/config` entries (see [Configuration](#ssh-config-auto-discovery-recommended)).
 
-> **⚠️ Important:** Remote servers must have the Docker CLI installed and the Docker
-> daemon socket accessible **without `sudo`**. The user connecting via SSH must be
-> a member of the `docker` group (or equivalent) so that `docker ps`, `docker inspect`,
-> etc. work without privilege escalation. Termainer uses SSH port forwarding to
-> tunnel the remote Docker socket to a local Unix socket, so all Docker commands
-> run locally against the forwarded socket — this avoids issues with remote Docker
-> versions, PATH, and `--format` compatibility.
+### Server Selection & Caching
 
-#### SSH Authentication Methods
+When you click a technology card (e.g. "Kubernetes") and don't have it locally, Termainer shows:
 
-| Method | How to use |
-|---|---|
-| **Key (`.pem`)** | `--ssh-key ~/.ssh/key.pem` or `TERMAINER_REMOTE_KEY_PATH` in `.env` |
-| **Password** | `--ssh-password 'mypass'` or `TERMAINER_REMOTE_PASSWORD` in `.env` (requires `sshpass`) |
+1. **Server selection modal** — checkboxes for all SSH servers (`~/.ssh/config` + app-added)
+   - Pre-selected based on **cached preferences** (`~/.config/termainer/provider_servers.json`)
+   - "Manage servers" button to add/remove servers via the UI
+2. **Parallel probing** — selected servers are probed simultaneously for the chosen provider
+3. **Auto-cache** — successful server-provider mappings are saved for next launch
 
-For password-based auth, install `sshpass`:
-
-```bash
-# Debian/Ubuntu
-sudo apt install sshpass
-
-# RHEL/CentOS/Fedora
-sudo yum install sshpass
-```
+Within a dashboard, the server dropdown lets you switch servers. Switching only probes the **current provider** on the target server — no unnecessary Docker/K8s/Podman probes.
 
 ### Multi-Server Dashboard
 
-The environment screen is technology-first (`Docker`, `Swarm`, `Kubernetes`, `Podman`, `OpenShift`).
+When multiple servers are connected (via parallel selection or pre-configured connections), each technology dashboard aggregates its related servers. You can:
 
-When you configure multiple servers (via `config.yaml` or `~/.ssh/config`), each technology dashboard can aggregate its related servers. You can:
-
-- **Server dropdown** at the top of the dashboard to select a specific server
-- **"Todos" (All)** option to see resources from all servers for that technology
-- **Switch servers anytime** using the server dropdown in the sidebar
+- Use the **server dropdown** to select a specific server
+- **Switch servers anytime** — only the current provider is probed
 - Each container shows its **server name** prefix when in multi-server mode
 
-The sidebar dropdown automatically populates with:
-- **Local** (your machine)
-- SSH servers from `~/.ssh/config`
-- Servers from `config.yaml` (if configured)
-
 ### Keyboard Shortcuts
 
 #### Technology selection screen
@@ -364,6 +388,7 @@ CLI (termainer)
         ├── server_manager.py ← Multi-server connection manager
         ├── remote/           ← Remote connection module
         │   └── ssh.py        ←   SSH via subprocess (key + password)
+        ├── storage.py        ← Persistent cache & user servers (JSON files)
         ├── config.py         ← .env parser and SSH builder
         ├── providers/        ← Multi-provider abstraction layer
         │   ├── base.py       ←   Abstract Protocol
@@ -406,6 +431,19 @@ CLI (termainer)
 
 ---
 
+## Troubleshooting
+
+| Problem | Solution |
+|---------|----------|
+| **"Not installed" on all technology cards** | No local runtime detected and no SSH servers configured. Add entries to `~/.ssh/config` or use the "Manage servers" button in the app |
+| **SSH server shows in dropdown but fails to connect** | Verify the host is reachable (`ssh <alias>`) and the container runtime is installed on the remote host |
+| **Docker SSH tunnel fails** | The remote user must be in the `docker` group. Try `ssh <host> docker info` manually |
+| **Kubernetes/Podman/OpenShift over SSH not detected** | Ensure the CLI binary (`kubectl`, `podman`, `oc`) is in the remote user's `PATH` |
+| **Server selection modal is empty** | No SSH servers configured in `~/.ssh/config` or the app's server manager. Use "Manage servers" to add one |
+| **App crashes with "no runtime"** | This was fixed in v0.4.1+. Update to the latest version or just configure SSH servers |
+
+---
+
 ## License
 
 MIT — [Alan Emanuel Stefanov](https://github.com/AlanStefanov)

{termainer-0.4.0 → termainer-0.5.1}/README.md

@@ -9,6 +9,7 @@ Building scalable platforms, leading teams, and optimizing cloud operations.
 [![LinkedIn](https://img.shields.io/badge/LinkedIn-Alan_Stefanov-blue?style=for-the-badge&logo=linkedin)](https://www.linkedin.com/in/alanstefanov/)
 [![Email](https://img.shields.io/badge/Email-alan.emanuel.stefanov@gmail.com-red?style=for-the-badge&logo=gmail)](mailto:alan.emanuel.stefanov@gmail.com)
 [![GitHub](https://img.shields.io/badge/GitHub-AlanStefanov-black?style=for-the-badge&logo=github)](https://github.com/AlanStefanov)
+[![Web](https://img.shields.io/badge/Web-astefanov.com-10b981?style=for-the-badge&logo=vercel)](https://astefanov.com)
 
 </div>
 
@@ -137,9 +138,84 @@ Depending on how you installed Termainer:
 
 ---
 
+## Quick Start
+
+```bash
+# Just run it — Termainer auto-detects local Docker, Podman, kubectl, or oc
+termainer
+
+# If no local runtime is found, configure remote servers via ~/.ssh/config
+# (see below) and restart, or click any technology card to probe SSH servers
+```
+
+Termainer works **with zero configuration** for local environments. For remote servers, just add entries to `~/.ssh/config` — no config file needed.
+
+---
+
 ## Configuration
 
-Termainer uses a **YAML config file** to manage multiple servers. Create `~/.config/termainer/config.yaml`:
+### SSH Config Auto-Discovery (Recommended)
+
+Termainer automatically discovers servers from your **`~/.ssh/config`** file. This is the **recommended approach** — no YAML or `.env` file needed.
+
+Simply define your remote servers in `~/.ssh/config`:
+
+```
+Host prod-web
+    HostName ec2-54-123-45-67.us-east-1.compute.amazonaws.com
+    User ubuntu
+    IdentityFile ~/.ssh/production.pem
+
+Host staging-k8s
+    HostName k8s-staging.example.com
+    User admin
+    IdentityFile ~/.ssh/staging-key
+
+Host dev-docker
+    HostName 192.168.1.100
+    User devuser
+    IdentityFile ~/.ssh/dev-key
+```
+
+Then launch Termainer — all SSH entries appear in the server dropdown automatically:
+
+```bash
+termainer
+```
+
+When you select a technology card (e.g. "Kubernetes"), Termainer shows a **server selection dialog** with checkboxes for all configured SSH servers. Selected servers are probed **in parallel** for the chosen provider, and successful connections open the dashboard. Server preferences are cached in `~/.config/termainer/provider_servers.json`.
+
+You can also **add and remove servers directly from the UI** via the "Manage servers" button. Custom servers are persisted in `~/.config/termainer/servers.json`.
+
+> **⚠️ Docker/Swarm note:** For Docker and Swarm over SSH, Termainer uses SSH port
+> forwarding to tunnel the remote Docker socket to a local Unix socket. The remote
+> user must have access to the Docker daemon (be in the `docker` group) without `sudo`.
+> Kubernetes, Podman, and OpenShift commands run directly over SSH, no tunnel needed.
+
+### Dashboard server switching
+
+Within a dashboard, switching servers only probes the **current provider** on the target server (no multi-probe). If the server doesn't have that provider, a notification is shown and the dashboard stays on the current server.
+
+#### SSH Authentication Methods
+
+| Method | How to use |
+|---|---|
+| **Key (`.pem`)** | Set `IdentityFile` in `~/.ssh/config` |
+| **Password** | `--ssh-password 'mypass'` or `TERMAINER_REMOTE_PASSWORD` in `.env` (requires `sshpass`) |
+
+For password-based auth, install `sshpass`:
+
+```bash
+# Debian/Ubuntu
+sudo apt install sshpass
+
+# RHEL/CentOS/Fedora
+sudo yum install sshpass
+```
+
+### Multi-Server via config.yaml (Advanced)
+
+For advanced setups, create `~/.config/termainer/config.yaml`:
 
 ```yaml
 lang: en
@@ -164,9 +240,9 @@ servers:
 
 See the full [Configuration Reference](guide/configuration-reference.md) for all options.
 
-### Quick single-server (.env)
+### Single-server via .env
 
-For a single remote server, you can use `.env` or CLI flags instead:
+For a quick single remote server, use `.env` or CLI flags:
 
 ```bash
 termainer --host ec2-54-123-45-67.us-east-1.compute.amazonaws.com \
@@ -201,93 +277,41 @@ termainer --provider openshift
 
 ### Remote (SSH)
 
-Connect to remote servers running Docker or Kubernetes:
-
 ```bash
-# Using CLI flags
+# Using --host flag (single server)
 termainer --host ec2-54-123-45-67.us-east-1.compute.amazonaws.com \
           --ssh-user ubuntu \
           --ssh-key ~/.ssh/production.pem \
           --provider docker
 
-# Using .env (recommended for frequent use)
+# Using .env (recommended for frequent single-server use)
 cp .env.example .env
 # Edit .env with your server details
 termainer
 ```
 
-#### SSH Config Auto-Discovery (Recommended)
-
-Termainer automatically discovers servers from your **`~/.ssh/config`** file. This is the **recommended approach** for multi-server setups—no `.env` file needed!
-
-Simply define your remote servers in `~/.ssh/config`:
-
-```
-Host prod-web
-    HostName ec2-54-123-45-67.us-east-1.compute.amazonaws.com
-    User ubuntu
-    IdentityFile ~/.ssh/production.pem
-
-Host staging-k8s
-    HostName k8s-staging.example.com
-    User admin
-    IdentityFile ~/.ssh/staging-key
-
-Host dev-local
-    HostName 192.168.1.100
-    User devuser
-    IdentityFile ~/.ssh/dev-key
-```
-
-Then launch Termainer:
-
-```bash
-termainer
-```
-
-You'll see all servers from your SSH config automatically loaded in the server dropdown. No configuration files needed!
+For multi-server setups, use `~/.ssh/config` entries (see [Configuration](#ssh-config-auto-discovery-recommended)).
 
-> **⚠️ Important:** Remote servers must have the Docker CLI installed and the Docker
-> daemon socket accessible **without `sudo`**. The user connecting via SSH must be
-> a member of the `docker` group (or equivalent) so that `docker ps`, `docker inspect`,
-> etc. work without privilege escalation. Termainer uses SSH port forwarding to
-> tunnel the remote Docker socket to a local Unix socket, so all Docker commands
-> run locally against the forwarded socket — this avoids issues with remote Docker
-> versions, PATH, and `--format` compatibility.
+### Server Selection & Caching
 
-#### SSH Authentication Methods
+When you click a technology card (e.g. "Kubernetes") and don't have it locally, Termainer shows:
 
-| Method | How to use |
-|---|---|
-| **Key (`.pem`)** | `--ssh-key ~/.ssh/key.pem` or `TERMAINER_REMOTE_KEY_PATH` in `.env` |
-| **Password** | `--ssh-password 'mypass'` or `TERMAINER_REMOTE_PASSWORD` in `.env` (requires `sshpass`) |
+1. **Server selection modal** — checkboxes for all SSH servers (`~/.ssh/config` + app-added)
+   - Pre-selected based on **cached preferences** (`~/.config/termainer/provider_servers.json`)
+   - "Manage servers" button to add/remove servers via the UI
+2. **Parallel probing** — selected servers are probed simultaneously for the chosen provider
+3. **Auto-cache** — successful server-provider mappings are saved for next launch
 
-For password-based auth, install `sshpass`:
-
-```bash
-# Debian/Ubuntu
-sudo apt install sshpass
-
-# RHEL/CentOS/Fedora
-sudo yum install sshpass
-```
+Within a dashboard, the server dropdown lets you switch servers. Switching only probes the **current provider** on the target server — no unnecessary Docker/K8s/Podman probes.
 
 ### Multi-Server Dashboard
 
-The environment screen is technology-first (`Docker`, `Swarm`, `Kubernetes`, `Podman`, `OpenShift`).
+When multiple servers are connected (via parallel selection or pre-configured connections), each technology dashboard aggregates its related servers. You can:
 
-When you configure multiple servers (via `config.yaml` or `~/.ssh/config`), each technology dashboard can aggregate its related servers. You can:
-
-- **Server dropdown** at the top of the dashboard to select a specific server
-- **"Todos" (All)** option to see resources from all servers for that technology
-- **Switch servers anytime** using the server dropdown in the sidebar
+- Use the **server dropdown** to select a specific server
+- **Switch servers anytime** — only the current provider is probed
 - Each container shows its **server name** prefix when in multi-server mode
 
-The sidebar dropdown automatically populates with:
-- **Local** (your machine)
-- SSH servers from `~/.ssh/config`
-- Servers from `config.yaml` (if configured)
-
 ### Keyboard Shortcuts
 
 #### Technology selection screen
@@ -342,6 +366,7 @@ CLI (termainer)
         ├── server_manager.py ← Multi-server connection manager
         ├── remote/           ← Remote connection module
         │   └── ssh.py        ←   SSH via subprocess (key + password)
+        ├── storage.py        ← Persistent cache & user servers (JSON files)
         ├── config.py         ← .env parser and SSH builder
         ├── providers/        ← Multi-provider abstraction layer
         │   ├── base.py       ←   Abstract Protocol
@@ -384,6 +409,19 @@ CLI (termainer)
 
 ---
 
+## Troubleshooting
+
+| Problem | Solution |
+|---------|----------|
+| **"Not installed" on all technology cards** | No local runtime detected and no SSH servers configured. Add entries to `~/.ssh/config` or use the "Manage servers" button in the app |
+| **SSH server shows in dropdown but fails to connect** | Verify the host is reachable (`ssh <alias>`) and the container runtime is installed on the remote host |
+| **Docker SSH tunnel fails** | The remote user must be in the `docker` group. Try `ssh <host> docker info` manually |
+| **Kubernetes/Podman/OpenShift over SSH not detected** | Ensure the CLI binary (`kubectl`, `podman`, `oc`) is in the remote user's `PATH` |
+| **Server selection modal is empty** | No SSH servers configured in `~/.ssh/config` or the app's server manager. Use "Manage servers" to add one |
+| **App crashes with "no runtime"** | This was fixed in v0.4.1+. Update to the latest version or just configure SSH servers |
+
+---
+
 ## License
 
 MIT — [Alan Emanuel Stefanov](https://github.com/AlanStefanov)

{termainer-0.4.0 → termainer-0.5.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "termainer"
-version = "0.4.0"
+version = "0.5.1"
 description = "Container observability and operations directly from your terminal"
 readme = "README.md"
 requires-python = ">=3.10"
@@ -38,6 +38,11 @@ dev = [
 termainer = "termainer.app:main"
 
 
+
+
+[tool.setuptools]
+include-package-data = true
+
 [tool.setuptools.packages.find]
 where = ["src"]
 
@@ -48,7 +53,7 @@ branch = "main"
 commit_message = "chore(release): {version}"
 major_on_zero = false
 upload_to_pypi = false
-upload_to_release = false
+upload_to_release = true
 build_command = ""
 
 [tool.semantic_release.changelog]

{termainer-0.4.0 → termainer-0.5.1}/src/termainer/app.py

@@ -3,6 +3,11 @@ from __future__ import annotations
 import asyncio
 import argparse
 import os
+import shutil
+import subprocess
+import sys
+from importlib.resources import files
+from pathlib import Path
 from typing import List, Optional, Type
 
 from textual.app import App
@@ -22,9 +27,96 @@ from .ui.splash import BootScreen
 from .version import VERSION
 
 
+def _check_command(command: list[str]) -> bool:
+    try:
+        subprocess.run(
+            command,
+            stdout=subprocess.DEVNULL,
+            stderr=subprocess.DEVNULL,
+            check=True,
+        )
+        return True
+    except (OSError, subprocess.CalledProcessError):
+        return False
+
+
+def _print_doctor_line(ok: bool, label: str, detail: str = "") -> None:
+    mark = "✓" if ok else "✗"
+    suffix = f" {detail}" if detail else ""
+    print(f"{mark} {label}{suffix}")
+
+
+def run_doctor() -> int:
+    print("Termainer Doctor")
+    print("────────────────────────────────────")
+    print()
+
+    checks: list[bool] = []
+    core_checks: list[bool] = []
+
+    python_ok = sys.version_info >= (3, 10)
+    checks.append(python_ok)
+    core_checks.append(python_ok)
+    _print_doctor_line(python_ok, f"Python {sys.version_info.major}.{sys.version_info.minor}")
+
+    docker_cli = shutil.which("docker") is not None
+    checks.append(docker_cli)
+    _print_doctor_line(docker_cli, "Docker CLI detected")
+
+    docker_api = docker_cli and _check_command(["docker", "info"])
+    checks.append(docker_api)
+    _print_doctor_line(docker_api, "Docker API available")
+
+    ssh_ok = shutil.which("ssh") is not None
+    checks.append(ssh_ok)
+    _print_doctor_line(ssh_ok, "SSH support enabled")
+
+    try:
+        import textual  # noqa: F401
+
+        textual_ok = True
+    except ImportError:
+        textual_ok = False
+    checks.append(textual_ok)
+    core_checks.append(textual_ok)
+    _print_doctor_line(textual_ok, "Textual installed")
+
+    try:
+        import rich  # noqa: F401
+
+        rich_ok = True
+    except ImportError:
+        rich_ok = False
+    checks.append(rich_ok)
+    core_checks.append(rich_ok)
+    _print_doctor_line(rich_ok, "Rich installed")
+
+    config_dir = Path(os.environ.get("XDG_CONFIG_HOME", Path.home() / ".config")) / "termainer"
+    config_ok = config_dir.exists() or os.access(config_dir.parent, os.W_OK)
+    checks.append(config_ok)
+    core_checks.append(config_ok)
+    _print_doctor_line(config_ok, "Configuration directory", str(config_dir))
+
+    checks.append(True)
+    core_checks.append(True)
+    _print_doctor_line(True, "Version", VERSION)
+
+    print()
+    if all(checks):
+        print("Everything looks good.")
+        return 0
+
+    if all(core_checks):
+        print("Core checks passed. Some optional runtime checks failed.")
+        return 0
+
+    print("Some checks failed.")
+    return 1
+
+
 class TermainerApp(App):
     TITLE = "Termainer"
-    CSS_PATH = "ui/styles.tcss"
+    CSS_PATH = files("termainer.ui").joinpath("styles.tcss")
 
     def __init__(self, server_manager: ServerManager) -> None:
         super().__init__()
@@ -126,7 +218,7 @@ async def build_server_manager(
         # Local auto-detect mode: solo proveedores locales, sin conexiones SSH al startup
         available = await detect_available_providers(ssh=None)
         if not available:
-            raise RuntimeError(_("app.error.no_runtime"))
+            return ServerManager([])
         for provider in available:
             label = _("app.server.local_label", provider=provider.name.capitalize())
             connections.append(ServerConnection(label=label, provider=provider, ssh=None))
@@ -143,6 +235,12 @@ def parse_args() -> argparse.Namespace:
     parser = argparse.ArgumentParser(
         description="Termainer — Container observability and operations from your terminal"
     )
+    parser.add_argument(
+        "command",
+        nargs="?",
+        choices=("doctor",),
+        help="Run a non-interactive environment diagnostic",
+    )
     parser.add_argument(
         "--provider",
         choices=("auto", "docker", "swarm", "podman", "kubernetes", "k8s", "openshift"),
@@ -202,6 +300,9 @@ def main() -> None:
     locale_init()
     args = parse_args()
 
+    if args.command == "doctor":
+        raise SystemExit(run_doctor())
+
     env_file = args.env_file
     env = load_env_file(env_file) if os.path.isfile(env_file) else {}
     locale_init(env)