Puter is a full-stack, self-hosted 'internet computer' — a browser-based desktop environment (file manager, app launcher, AI services, static-site hosting, serverless workers) backed by a Node.js kernel. The repo is a monorepo of five interlocking sub-packages: a TypeScript backend kernel (`src/backend`), a browser GUI (`src/gui`), a published JavaScript SDK (`src/puter-js`), a CLI (`src/cli`), and a Cloudflare-Worker port (`src/worker`) plus an MCP connector (`src/mcp-connector`). The kernel is the centerpiece: it layers clients (MySQL/Postgres/SQLite, DynamoDB, S3, Redis, email, alarms), stores (user, app, FS entry, session, share, permission, group, KV, OIDC, notification, subdomain), services (auth, FS, metering, permission, ACL, broadcast, notification, OIDC, app-icon, health), controllers (REST + WebDAV + WISP + Peer endpoints), and drivers (AI chat/TTS/STT/image/video/OCR, KV, apps, subdomains, notifications, workers) behind a custom `PuterServer` that wires them together with ordered peer-dependency construction. Configuration is a three-tier deep-merge (config.default.json → config.json → PUTER_CONFIG_PATH) computed at startup. The backend is well-tested with vitest unit, integration, and benchmark suites; the SDK ships with Playwright e2e tests. The GUI is a large, jQuery-based desktop UI with its own webpack build and a component system. Notable engineering: a type-safe permission/ACL system with rewriters and implicators, a metering/subscription model in microcents, a multi-engine database abstraction with ordered migrations, a driver pattern with per-operation cost tables, a token v1→v2 silent-migration path, a reauth coordinator with shared in-flight promises, and a worker-types package that provides template-literal route-param inference for the worker runtime. The codebase is actively maintained (June 2026), uses current Node 24 / TypeScript 5.9 / Express 5 tooling, and has CI for backend tests, docs builds, release-please, and Docker image publishing.
SynoCommunity/spkrepo is a production-grade web application for hosting and distributing Synology package (.spk) repositories. It provides a full DSM-compatible catalog API for NAS devices, an admin interface for package lifecycle management (upload, sign, activate, archive), user registration with role-based access, and background task processing via Celery. The system is built with a hexagonal (ports-and-adapters) architecture, separating domain logic from Flask web transports, SQLAlchemy persistence, and Celery task execution. It manages package metadata, versioning, firmware compatibility, and download statistics. The codebase is well-structured, with extensive test coverage including import isolation enforcement, Alembic migrations for PostgreSQL and SQLite, and CI/CD via GitHub Actions. Dependencies include Flask, Celery, PostgreSQL, Redis, Bootstrap, and Chart.js. The architecture is clean and modular, making it suitable for both small community repos and larger installations.
This repository is the RR (Redpill Recovery) bootloader for Synology DSM, a tool that enables installing and booting Synology DiskStation Manager on non-Synology hardware. It provides an interactive initrd-based environment (TUI via dialog/whiptail) for configuring DSM model, version, addons, kernel modules, boot parameters, and then building a patched boot image. The system supports multiple deployment targets (raw image, OVA, VMX, VMDK, VHD, VHDX) and includes a GitHub Actions workflow for on-demand custom builds triggered by issue submissions. It also offers remote management via web interfaces (TTYD, DUFS, HTTP) and extensive internationalization with 15+ language translations. The architecture is modular with separate scripts for boot, init, menu, addon management, kernel module handling, and configuration persistence via YAML. While primarily an application, it includes data files (JSON/XLSX catalogs of models, addons, modules, patches) that serve as configuration metadata for the build process.
This repository provides a comprehensive Docker Compose configuration for building a self-hosted NAS (Network Attached Storage) system. It orchestrates over 20 services including media management (Sonarr, Radarr, Lidarr, Bazarr, Prowlarr, qBittorrent, Jellyfin, Jellyseer), a WireGuard VPN (PIA), reverse proxy (Traefik with Let's Encrypt), a homepage dashboard (Homepage), automatic updates (Watchtower), and optional services like AdGuard Home, Home Assistant, Immich, Vaultwarden, Paperless, and more. The architecture is a multi-container Docker stack with a shared network, designed to run on any Docker-capable Linux box. The primary data flow involves downloading media via qBittorrent through a VPN, managing it with *arr applications, and serving it via Jellyfin. The repository includes automation scripts for initial configuration (update-config.sh) and port forwarding updates (pia-shared/portupdate-qbittorrent.sh). It is not a software application with custom code but rather a well-documented, opinionated deployment template. The codebase is primarily configuration files (docker-compose.yml, environment files, nginx configs) with a few bash and JavaScript scripts. The quality is good for its purpose: it is organized, documented, and widely used, but it lacks reusable software components that could be extracted into a new project with minimal modification.
This repository contains only a README.md file and a collection of screenshot assets. It serves as a documentation and marketing page for a commercial NAS-based WeChat backup/restore tool called WxBackup. No source code, binaries, or build scripts are present. The README describes features, installation steps, usage guides, and troubleshooting for the product, which is distributed as a proprietary application for FeiniuOS (x86/ARM) with a planned Docker release. The repository is not a functional codebase; it is a static informational resource. There are no reusable software components, no data pipelines, and no engineering artifacts to evaluate. The last commit date is listed as 2026-09-21, which appears erroneous, and there is no evidence of active development or maintenance of code within this repo.