This repository implements `spc`, a CLI tool for building fully static PHP executables with selected extensions, SAPIs, and dependency libraries. It orchestrates downloading source archives or prebuilt binaries, extracting them, compiling dependency libraries (using autoconf, CMake, or Meson), patching PHP source code, and assembling the final static binary. The architecture is modular: a Symfony Console application with a registry/plugin system that loads package definitions from YAML and PHP classes, an artifact downloader supporting multiple source types (GitHub releases, PECL, git, URL, etc.), a build executor abstraction for Unix and Windows (autoconf/CMake with static/PIC flags), a dependency resolver for topological ordering, and a doctor module for environment health checks with auto-fix. Cross-platform support covers Linux, macOS, and Windows, with toolchain abstractions for GCC, Clang, MSVC, and Zig. The project is under active development (v3 rewrite) with extensive version-specific patches for PHP source (8.0-8.6) and support for 100+ extensions. It is primarily a build system tool, not a data analysis or research project.
This repository is a large collection of Bash scripts that automate the deployment, configuration, and update of self-hosted services on Proxmox VE, primarily through LXC containers and VMs. It is a provisioning and automation framework rather than a runtime application: each ct/*.sh script declares resource variables (CPU, RAM, disk, OS template) and an optional update_script(), while install/*.sh scripts run inside an existing container to install a specific application. Usage is typically a one-line curl command executed as root on the Proxmox host, after which the script creates a container/VM, installs dependencies, generates credentials, writes systemd units or OpenRC init scripts, and configures databases and reverse proxies. The architecture is layered: hundreds of app-specific scripts wrap a smaller set of shared Bash function libraries in the misc/ directory (build.func, install.func, vm-core.func, core.func, error_handler.func). These shared functions handle common operations such as fetching GitHub releases, setting up language runtimes, creating databases, backing up configs before updates, and standardizing error handling. Update flows generally stop the service, back up configuration/data, fetch the latest release, restore the backup, run migrations, and restart the service. This consistency is the project's main strength and makes adding a new container recipe relatively straightforward. Weaknesses are typical of a large community-driven shell-script collection: no unit tests, heavy reliance on third-party installers fetched via curl|bash, some hardcoded versions, and external dependencies on GitHub release asset names and remote core-library URLs. Many scripts assume Debian/Ubuntu or Alpine bases and run as root with no signature verification. Despite these risks, the codebase is actively maintained, consistently formatted, and the shared function libraries are practical examples of reusable Bash abstractions for Proxmox automation.
This repository contains a collection of deployment and management scripts for setting up and maintaining a multi-protocol proxy server (sing-box) on VPS and free hosting platforms (Serv00/Hostuno). The system automates the installation of five proxy protocols (Vless-reality, Vmess-ws, Hysteria-2, Tuic-v5, Anytls), generates TLS certificates, configures Cloudflare Argo tunnels for CDN proxying, and provides keep-alive mechanisms via cron, GitHub Actions, Cloudflare Workers, and a Node.js web server to prevent service downtime on free hosts. The primary entry points are interactive bash scripts (`sb.sh` for VPS, `serv00.sh` for Serv00) and a non-interactive keep-alive script (`serv00keep.sh`). The architecture is a set of loosely coupled shell scripts and a small Express.js application, not a monolithic service. External dependencies include sing-box, cloudflared, and standard Linux utilities. The code is functional and widely used (10k+ stars) but exhibits typical script-level craftsmanship: long monolithic functions, global variable usage, and tight coupling to specific hosting environments. The last commit date (2026-10-13) appears anomalous and likely a data error, but the repository shows active maintenance with recent stars and forks.
Daijin is a container management tool designed for Android devices running Termux. It provides a menu-driven interface to create, run, remove, and manage Linux containers using either the ruri backend (a lightweight container implementation) or proot (a chroot alternative). The application orchestrates container lifecycle operations by integrating with submodules rurima (for running Docker/LXC images without Docker/LXC) and rootfstool (for obtaining container rootfs from mirrors). Key functionalities include downloading container images, setting up container environments with proper permissions and networking, managing container configurations, and providing launch mechanisms. The architecture is monolithic with modular shell scripts handling specific operations, all built as a Debian package for Termux deployment.
This repository builds Docker images containing the Android SDK for use in CI/CD environments. It provides two flavors (standalone and lazydl) across two base OS options (Ubuntu and Alpine). The standalone flavor bakes the SDK into the image during build, while lazydl downloads the SDK into a shared volume at runtime. The core functionality resides in the tools/ directory, particularly android-sdk-update.sh which handles SDK installation and licensing. The project uses GitHub Actions to automate multi-architecture builds and publishes to Docker Hub. While functional, the code shows some coupling to specific directory paths and relies on hardcoded package versions, limiting reuse outside its intended context.