zrok is a production-grade, self-hostable secure resource sharing platform built on OpenZiti overlay networking. It enables users to share web services, files, TCP/UDP tunnels, and VPN connections through firewalls and NAT without requiring inbound connectivity. The system supports both public and private sharing modes, OAuth authentication (GitHub, Google, OIDC), and includes a full REST API (v2), a CLI tool (`zrok2`), a React web console, a background agent daemon with gRPC remote control, and SDKs in Go, Python, and Node.js. Architecturally, zrok follows a controller-agent pattern. The controller is a Go REST server that manages accounts, environments, shares, accesses, frontends, namespaces, organizations, and bandwidth limits. It uses SQLite3 or PostgreSQL for persistence with versioned migrations, and integrates with InfluxDB for usage metrics and RabbitMQ (AMQP) for dynamic proxy mapping updates. The agent runs as a background process on the user's machine, managing child processes for each share/access and exposing a gRPC API for remote management. Frontend proxies (public, dynamic, socks, Caddy) handle incoming traffic with OAuth, basic auth, and interstitial pages. Key entry points include the CLI commands under `cmd/zrok2/` (e.g., `share`, `access`, `enable`, `admin`), the controller REST handlers in `controller/`, the agent gRPC service in `agent/agentGrpc/`, and the SDK packages in `sdk/golang/sdk`, `sdk/python/src/zrok2`, and `sdk/nodejs/sdk`. The system also includes a canary testing framework for continuous health validation and a comprehensive metrics/limits engine for bandwidth enforcement. External dependencies include OpenZiti (overlay network), InfluxDB (metrics), RabbitMQ (messaging), Caddy (optional web server), and various OAuth providers. The project is actively maintained with frequent commits, automated CI/CD, and multi-platform release pipelines (Linux, macOS, Windows, Docker).
The repository ruanyf/weekly hosts the weekly tech newsletter '็งๆ็ฑๅฅฝ่ ๅจๅ' (Tech Lover's Weekly) curated by ้ฎไธๅณฐ. Each issue is a markdown file in the `docs/` directory, following a standardized template that includes sections such as cover image, main topic, tech dynamics (short news), articles (annotated links), tools (software recommendations), resources (reference links), images, excerpts, quotes, past issues, and acknowledgements. The newsletter has been published every Friday since 2018, with issues numbered sequentially. The repository serves as an open-source, community-curated archive of technology news, tools, and resources. It accepts contributions via GitHub issues for article submissions and job postings ('่ฐๅจๆไบบ'). While the content is rich and well-organized, the repository contains no data processing code or build system; it relies entirely on manual curation and external links. This makes the long-term reproducibility dependent on the availability of external resources (images via CDN.beekka.com and linked articles). Despite this, the newsletter remains a valuable resource for tracking technology trends over time.