This repository is Sentry's self-hosted packaging and operations layer, not the Sentry application itself. It bundles upstream Sentry, Relay, Snuba, Symbolicator, Taskbroker, Vroom, uptime-checker, and launchpad images into a large Docker Compose deployment, and provides idempotent install/upgrade scripts, generated config templates, healthchecks, backup/restore tooling, and optional community patches. The primary entry points are install.sh, which sources a sequence of modular install/ steps, plus operator scripts under scripts/ (reset.sh, backup.sh, restore.sh), sentry-admin.sh for Django admin commands, and a reusable GitHub Action (action.yaml) that downstream Sentry repos use to run self-hosted end-to-end tests against their own images. The runtime architecture is a compose stack: nginx terminates HTTP and routes ingestion to Relay, which validates and buffers events before writing to Kafka; Snuba consumer containers move data from Kafka into ClickHouse; Sentry web and consumer containers read from Kafka/Postgres/Redis and the SeaweedFS S3-compatible object store; Symbolicator handles native symbolication; Taskbroker routes async tasks. The compose file supports an errors-only profile that dramatically reduces the service count and a feature-complete profile that enables transactions, metrics, replays, profiling, uptime, logs, and mobile builds. The codebase is notably well-tested for an infrastructure repo, with bash unit tests under _unit-test/ and pytest integration tests under _integration-test/ that install the full stack and verify event ingestion end to end. Maintenance is active and dependency drift is low: images are bumped regularly via Dependabot, shell scripts are linted with ShellCheck and formatted with shfmt, there is a pre-commit pipeline, and the repo tracks recent upstream replacements such as Valkey for Redis, pgbouncer, taskbroker, and ClickHouse upgrades. The main limitation for reuse is that most of the repository is configuration and deployment glue tied to this specific stack; the few genuinely self-contained, extractable components are small utilities around healthchecks, cryptography/migration, and cron containers.
PrivateGPT is a production-grade, private AI assistant platform that provides RAG (Retrieval-Augmented Generation) over ingested documents, tool/function calling, sandboxed code execution, web search, MCP (Model Context Protocol) integration, skill management, and multimodal support. It is built as a FastAPI server with background workers (Celery and ARQ) for asynchronous ingestion and task processing, and exposes a Claude API-compatible streaming interface. The architecture is modular: a core chat engine with an interceptor pipeline for request/response processing, a pluggable component system with registries for LLMs, embeddings, readers, vector stores, and sandboxes, and a two-tier scheduling system (local and distributed) for tool and chat execution. The codebase demonstrates strong engineering practices with dependency injection, registry patterns, and composable interceptors, but its dual scheduling backends, extensive monkey-patching of third-party libraries, and heavy reliance on llama-index introduce maintenance complexity and technical drift. Reusable highlights include the context stack builder for dynamic system prompt assembly, the interceptor chain pattern, the sandbox abstraction for secure code execution, and the citation parser with incremental streaming support. The project is actively maintained by Zylon and powers their enterprise offering, with 57k+ stars and frequent releases.
This repository provides deployment configurations and scripts for self-hosting the UI Bakery low-code platform. It contains Docker Compose files for local, Azure, and external database setups, Kubernetes manifests for orchestration, and shell scripts for installation, setup, and updates. The repository does not include the application source code but rather orchestrates pre-built Docker images of UI Bakery's services (gateway, frontend, backend, etc.). The installation script guides users through environment configuration, secret generation, and service startup via Docker Compose. While functional and demonstrating good practices in input validation and cryptographic secret generation, the update script contains a bug in the external database handling section, and the scripts lack modularity, limiting reusability beyond this specific deployment context.