Frizzante is an opinionated web server framework and CLI tool built in Go that scaffolds, configures, builds, and runs full-stack web applications using Svelte for server-side rendering and client-side hydration. The CLI provides a TUI menu system for project creation, dependency management (Go, Bun, Air, sqlc), development with live reload, building production binaries, testing, and more. The scaffolded project includes a complete web server with session management, SQLite database, guards, and a todo list example. The architecture separates the CLI layer (menus, actions, generations) from the scaffolded project's library (core, views, security, servers, routes). The codebase demonstrates strong Go engineering with build tags for conditional compilation, extensive use of embedded files, and a well-structured TUI using Bubble Tea.
Coolify is a self-hosted Platform-as-a-Service (PaaS) that enables users to deploy and manage applications, databases, and services on their own infrastructure. It serves as an open-source alternative to Heroku, Netlify, or Vercel, supporting Docker-based deployments with Git integration (GitHub, GitLab, Gitea, Bitbucket), multiple build packs (Railpack, Nixpacks), and one-click service templates. The system manages servers, reverse proxies (Traefik/Caddy), SSL certificates, scheduled backups, and multi-channel notifications (email, Discord, Slack, Telegram, Pushover, webhook). The architecture is a Laravel monolith with a Livewire + Alpine.js frontend for the v4 UI and a React + TypeScript canvas-based interface for the v5 UI. Background jobs are handled by Laravel Horizon with dedicated queues for deployments, cron tasks, and reconciliation. Real-time updates use Soketi (a Pusher-compatible WebSocket server) and Laravel Echo. The system integrates with cloud providers (Hetzner, Vultr, DigitalOcean) for server provisioning and Stripe for subscription billing. A Model Context Protocol (MCP) server exposes resources and tools for AI assistant integration. Key data flows include: webhook ingestion from Git providers triggering deployment jobs, SSH-based remote command execution on managed servers, Docker Compose parsing and environment variable injection, database backup scheduling with S3 storage, and proxy configuration generation. The v5 architecture introduces a control-plane/agent split with Flux (HTTP socket) and coold (gRPC) components for improved scalability and isolation. External dependencies include Docker, PostgreSQL, Redis, Soketi, Stripe API, cloud provider APIs, and various notification service endpoints. The codebase is actively developed with frequent schema migrations and a dual v4/v5 code path, indicating ongoing architectural evolution.
LOA Logs is a desktop damage meter and combat log parser for the MMORPG Lost Ark, built as a Tauri application with a Rust backend and Svelte 5 frontend. In production, it captures combat data from the game client through file watching or low-level network interception (WinDivert on Windows, packet capture helpers on Linux), parses entity/skill/buff events, and renders live DPS meters, encounter statistics, and post-raid progression analysis via ECharts dashboards. It persists encounter history to SQLite through a repository pattern with connection pooling, and enriches combat data with static game data (skill tables, NPC windows, encounter definitions) bundled as generated TypeScript/JSON files. The architecture is a hybrid desktop app: the Rust backend (src-tauri) handles log ingestion, packet parsing, entity tracking, and database persistence, while the Svelte frontend uses reactive state classes (EntityState, SkillState, BuffState) and a typed column configuration system (LogColumn) to drive tables and charts. Key entry points include the Tauri command layer, the EntityTracker module, and Svelte routes for settings and statistics. External dependencies include the Lost Ark game client, WinDivert, SQLite, and several generated game data files that must be updated with each game patch. The codebase is actively maintained (recent commits, v1.51.1 tag, 30+ tests) but carries notable technical debt: a ~6000-line repository file tightly coupled to multiple modules, legacy components (LegacyLogRDPSBreakdown.svelte) alongside new implementations, live/log component duplication, and heavy use of debug_print! macros. Game data files drift from the live game without an update mechanism, and the Node.js >=24 requirement may cause compatibility issues. Despite this, several clean patterns—composable stat modifiers, entity lifecycle management, reactive model-view state, and type-safe column configs—are genuinely reusable. This is primarily an application repo, though it embeds substantial data-processing and game-data components that give it a hybrid character.