Nginx Proxy Manager is a full-stack web application that provides a graphical user interface and REST API for managing Nginx reverse proxy configurations, SSL/TLS certificates (via Let's Encrypt or custom uploads), TCP/UDP streams, access control lists, and user permissions. The system is designed to run as a Docker container and is primarily used by self-hosting enthusiasts and small-to-medium deployments to simplify the otherwise complex task of configuring Nginx and maintaining certificates. The architecture is a classic three-tier web application: a Node.js/Express backend (ES modules) with Objection.js/Knex ORM supporting SQLite, MySQL, and PostgreSQL; a React 18/19 frontend built with TypeScript, Vite, TanStack Query, and Tabler UI; and a set of s6-overlay managed services (backend, frontend, Nginx) inside a single Docker image. The backend generates Nginx configuration files from Liquid templates and reloads Nginx on any change. External dependencies include Nginx, Certbot (for Let's Encrypt), OpenSSL, and optionally a database server. Key entry points are `backend/index.js` (server startup, migration, setup, Express app) and `frontend/src/main.tsx` (React bootstrap). The primary data flow is: user creates or modifies a proxy host, redirection, stream, or certificate via the UI → API call → backend validates permissions and data → persists to database → regenerates relevant Nginx config files → tests configuration → reloads Nginx. The system also periodically checks for certificate expiration and renews via Certbot, and fetches IP ranges from Cloudflare/Cloudfront for access control. The codebase demonstrates solid engineering practices: a consistent internal service layer with access control and audit logging, a well-typed API client with automatic camelCase/decamelize conversion, a reusable table framework built on TanStack Table, and a comprehensive i18n system supporting 24+ locales. While some modules (e.g., certificate management) are large and could benefit from refactoring, the overall structure is clean and maintainable.
This repository provides a Docker Compose-based setup for running WordPress, designed for both local development and production environments. It orchestrates MySQL and WordPress services with optional WP-CLI access, using environment variables for configuration and named volumes for persistent storage. The production configuration includes resource limits, restart policies, and integration with reverse proxy networks (via VIRTUAL_HOST/LETSENCRYPT variables) for HTTPS support. Key components include environment-specific compose files (docker-compose.yml for production, docker-compose-local.yml for local dev), helper scripts for backup/restore/setup, and WP-CLI wrappers. The setup follows Docker best practices: separating concerns via networks, using volumes for data persistence, and leveraging environment-specific configuration. While not innovative, it implements a solid, maintainable pattern for deploying WordPress with Docker. The codebase demonstrates basic but correct usage of Docker Compose features, with clear separation between local and production configurations. Helper scripts automate common tasks like database dumps and file backups/restores using Docker exec and cp commands. There's no evidence of technical debt or outdated practices; the configuration aligns with current Docker and WordPress ecosystem standards.
This repository provides a comprehensive, modular set of Bash scripts to automate the installation and configuration of Apache Guacamole—an open-source remote desktop gateway. The primary orchestrator '1-setup.sh' handles interactive prompts and silent install variables to deploy Guacamole server and client from source, integrate MySQL/MariaDB as the backend database, set up Nginx as a reverse proxy, and optionally configure TLS (self-signed or Let's Encrypt), multi-factor authentication (TOTP, Duo, LDAP), and extra UI features like quick-connect and session recording storage. The scripts are well-structured with extensive error checking, logging, distro-specific workarounds, and support for modular post-install add-ons. Though not a library for reuse, the code demonstrates solid shell scripting craftsmanship, security hardening (fail2ban integration, firewall rules), and separation of concerns. The repository serves as a turnkey deployment toolkit for production-grade Guacamole environments.
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 repository provides Docker images and deployment configurations for running Thumbor, an open-source photo thumbnail service. It builds three main components: the core Thumbor image service, an nginx-based caching proxy (nginx-proxy-cache), and a remote computer vision service (remotecv) for asynchronous smart cropping and feature detection. The project includes build scripts, CI/CD workflows, testing infrastructure, benchmarking tools, and deployment recipes (docker-compose and Kubernetes) to facilitate easy deployment and scaling of Thumbor-based image processing systems. The architecture follows a microservices pattern where Thumbor handles image processing, nginx-proxy-cache provides caching and reverse proxying, and remotecv offloads heavy computer vision tasks.