PortKiller is a cross-platform desktop application for developers to monitor, manage, and kill processes listening on TCP ports. It provides a unified interface across macOS (SwiftUI), Windows (.NET 9 / WinUI 3), and Linux (Python GTK3 + Rust core) with features including real-time port scanning, process type detection, favorites and watched ports with notifications, two-stage process termination (SIGTERM → SIGKILL), Kubernetes port-forward management with auto-reconnect, and Cloudflare tunnel integration (quick and named tunnels). The application also includes an onboarding wizard, sponsor/contributor display, Sparkle-based auto-updates (macOS), and extensive keyboard shortcut support. The architecture is platform-native with shared patterns: each platform implements its own UI layer, port scanner, and process killer, while a Rust core library (`portkiller-core`) provides scanning and process termination for Linux. The macOS version uses an actor-based `PortScanner` and observable state management (`AppState`), the Windows version follows MVVM with a system tray mini-window, and the Linux version uses a GTK3 system tray indicator. All platforms share a common feature set but with varying completeness (macOS is the most feature-rich). External dependencies include `lsof`/`ss` (Linux), `kubectl`, `cloudflared`, `socat`, and system utilities for process enumeration. Key data flows: port scanning via platform-specific commands (lsof, ss, GetExtendedTcpTable) → parsing into `PortInfo` models → filtering/searching → display in tree/table views → user actions (kill, watch, favorite, forward, tunnel). Kubernetes port-forwards and Cloudflare tunnels are managed as subprocesses with monitoring loops for reconnection and log streaming. The application persists user preferences (favorites, watched ports, customizations) using platform-native storage (Defaults on macOS, JSON on Windows/Linux).
This repository provides Docker Compose and Kubernetes configuration files for deploying a variety of self-hosted applications and system services. It serves as a template repository for deploying services like AdGuard Home, Bitwarden, MinIO, Traefik, and others, as well as system tools like Fail2ban and acme.sh for certificate management. The architecture is modular, with each application having its own directory containing deployment configurations (docker-compose.yml, Helm charts, Kubernetes manifests). There is no single unified application; instead, it offers reusable deployment patterns for individual services. Key entry points are the docker-compose.yml or Helm chart files within each application's directory. The repository relies on external dependencies like Docker, Kubernetes, and Helm for deployment, and the applications themselves depend on their respective upstream container images.
This is a Home Assistant add-on repository for the Cloudflared add-on, which enables remote access to Home Assistant via a Cloudflare Tunnel without opening ports. The repository itself does not contain the add-on's runtime code (which resides in a separate repository); instead, it serves as a meta-repository that defines the add-on's configuration schema, provides multi-language translations, and hosts documentation and CI/CD infrastructure. The primary functional artifact is the `cloudflared/config.yaml` file, which defines input validation rules (including regex-based parameter validation), port mappings, and optional configuration fields. The repository is not a library or framework but a configuration and distribution hub for the add-on. It is well-maintained with automated dependency updates, linting, and release management.
This repository provides a collection of scripts and lightweight HTTP servers for automated deployment and management of sing-box multi-protocol proxy nodes. It supports VLESS-REALITY, VMess-WebSocket (with optional Cloudflare Argo tunnel), Hysteria2, and TUIC v5 protocols, along with Nezha monitoring agent integration. The primary use case is setting up proxy services on VPS or free hosting platforms like Serv00/CT8, with additional 'toy' implementations for game hosting environments using Go, Node.js, PHP, and Python. The architecture is script-driven: large Bash scripts (sing-box.sh, sb_serv00.sh) handle installation, configuration, and service management via interactive menus or environment variables. They download precompiled binaries, generate sing-box JSON configurations, and manage systemd or OpenRC services. The supplementary HTTP servers (Node.js, Python, PHP) provide subscription endpoints and process lifecycle management, downloading and running a core binary (sbsh) that performs the actual proxy setup. The PHP check.php script offers standalone server environment diagnostics. Code quality is average overall. The Bash scripts are functional but contain significant duplication across Serv00 variants and lack modularity. The Node.js and Python HTTP servers are well-structured and demonstrate clean asynchronous patterns, while the PHP diagnostic script is a polished, self-contained tool. There is no test suite or CI/CD, and external binary URLs are hardcoded, posing medium technical drift risk. The repository is actively maintained by a large community, making it a practical solution for proxy deployment despite its architectural limitations.