This repository is a full-stack, multi-client rental property management platform called 'rightHouse' (ζΏι). It consists of three frontends: a Vue 3 + Arco Design admin panel (RH-admin), a uni-app landlord mobile app (RH-landlord), and a uni-app tenant mobile app (RH-tenant), all backed by an Egg.js Node.js REST API (RH-server) with MySQL, Redis, MinIO, and OSS storage. The system enables landlords to publish houses, tenants to search and apply for rentals, and administrators to manage users, houses, and lease applications. Key workflows include lease application with approval flow, maintenance requests, rental market listings with location-based search, and tenant reviews. The architecture is monolithic on the server side but with separate client applications sharing some UI components (uView UI) and a custom HTTP client (luch-request). The codebase is functional and covers the full rental lifecycle, but suffers from duplicated UI component libraries across mobile apps, mixed Vue 2/Vue 3 frameworks, hardcoded configuration values, and lack of automated tests. The admin panel uses modern Vue 3 tooling, while the mobile apps rely on the older uView 2.0 library. The server side includes JWT authentication, SMS notifications, and file upload capabilities. Overall, it is a solid but not exceptional implementation of a rental management system, useful as a reference for similar multi-tenant applications but with several areas of technical debt.
Yi.Abp.Admin is a full-stack enterprise administration framework built on ASP.NET Core (ABP vNext framework) with multiple Vue 3 frontends (Pure Admin, Vben5, RuoYi, and a BBS variant). It provides RBAC, multi-tenancy, audit logging, setting management, code generation, and OAuth support (QQ, Gitee). The backend follows Domain-Driven Design with modules like Yi.Framework.Rbac and Yi.Framework.TenantManagement, using SqlSugar ORM as a replacement for ABP's default EF Core. The frontends feature dynamic route generation from backend permissions, reusable UI components (dialog, cropper, table bar, form API), and state management with Pinia. The monorepo also includes a CLI tool for scaffolding new modules. Despite some duplication across frontends and ABP customizations that may cause upgrade friction, the codebase demonstrates solid engineering with well-separated concerns and several independently usable components.
LiteOps is a lightweight, self-hosted CI/CD platform built with Django 4.2 (Python 3.9) and Vue 3 (Ant Design Vue). It provides project management, build task configuration, credential storage (GitLab tokens, SSH keys, kubeconfig), environment management, and notification robots (DingTalk, WeChat, Feishu). Builds are executed inside a Docker-in-Docker container that includes Java, Maven, Node, and kubectl, with real-time log streaming via Server-Sent Events (SSE). The system integrates with GitLab for webhook-triggered builds and branch/commit information, supports LDAP authentication, and enforces role-based permissions (function and data scopes). The frontend dashboard displays build statistics, trends, and recent builds using ECharts. The codebase is functional and actively developed, but exhibits several engineering weaknesses: no automated tests, threading for async build execution (no task queue), hardcoded secrets (admin password, database credentials), SHA256 password hashing (not bcrypt), and plaintext storage of GitLab tokens. The Docker image is large and requires privileged mode. Despite these issues, the system is suitable for small teams needing a simple, integrated CI/CD solution without external dependencies beyond GitLab and MySQL.
Stb (εΎεΊ) is a full-stack image hosting service built as a pnpm monorepo. The backend is a Node.js/Express application with MongoDB (Mongoose) providing REST APIs for user authentication, image upload, album management, admin operations, and system configuration. The frontend is a Vue 3 single-page application using Pinia for state management, Vue Router with lazy-loaded views, and a mix of Ant Design Vue and Element Plus UI libraries. The system supports multiple storage backends (local filesystem, S3-compatible, Alibaba OSS, Tencent COS, Qiniu, Upyun, SFTP, FTP, WebDAV, Telegram, GitHub) via a pluggable adapter pattern, and integrates AI-based content moderation (Tencent, Aliyun, NSFWJS). Deployment is Docker-based with a multi-stage build and GitHub Actions CI/CD for multi-architecture images. The application includes a comprehensive admin panel for user, image, log, album, role group, invite code, and configuration management, as well as OAuth login (GitHub, Google, Linux DO), email verification, and a slider captcha component. While the codebase is functional and well-structured with clear separation of concerns, it exhibits some technical debt: mixed UI libraries increase bundle size, the configuration view is monolithic and exposes sensitive credentials to the client, there are no automated tests, and some patterns (e.g., IP detection, Docker entrypoint sed) are fragile. Overall, it is a solid, production-ready image hosting solution with reusable utility modules.
Pangee Cluster is a graphical tool for offline Kubernetes cluster lifecycle management, including installation, upgrade, backup, node operations, and SSH access. The backend is a Go REST API (Gin) that orchestrates Ansible playbooks from versioned resource packages. The frontend is a Vue 3 single-page application (with some legacy Vue 2 patterns) that provides a comprehensive UI for cluster planning, operation execution, real-time log tailing, and SSH terminal. The tool is primarily designed for air-gapped environments where clusters are provisioned from pre-packaged resource bundles containing Kubernetes binaries, container runtimes, and Ansible roles. Despite its functional breadth, the codebase shows signs of technical debt: mixed Vue API styles, heavy mixins, no test suite, and tight coupling to a custom-patched Ansible version. The resource package abstraction and generic form editing components are notable for reusability, but overall the architecture is typical of a production tool that has evolved organically rather than being designed for clean reuse.
This repository is a Vue 3 admin dashboard template (vue3-admin-better) built with Element Plus, Vuex, Vue Router, and Rspack as the build tool. It provides a full-featured management system UI with login, registration, error pages, and over 40 demo CRUD pages for common business modules like projects, teams, tasks, customers, knowledge base, and workflows. The architecture follows a standard SPA pattern with dynamic routing based on RBAC permissions (intelligence/all modes), multiple layout variations (vertical/horizontal), theme customization (three themes persisted to localStorage), and a mock API layer using MockJS. Key entry points include `src/main.js` (app bootstrap), `src/layouts/index.vue` (main layout container), and `src/router/index.js` (route definitions). The state management uses Vuex with modules for user, routes, settings, tabs, and error logs. External dependencies include Vue 3, Element Plus, ECharts, Axios, and vuedraggable. The codebase demonstrates typical admin template patterns but has several maintenance and security concerns: mock interceptors are forced in production (a serious risk), a local `layouts` package dependency, fragile FontAwesome-to-Element-Plus icon mapping, and hardcoded mock data with no real backend integration. These issues limit direct production readiness without significant refactoring.
This repository implements a desktop application for batch processing EPUB ebooks, including reformatting, encryption/decryption (filename obfuscation), font encryption/decryption with OCR-based recognition, image compression and conversion, cover replacement, and Chinese text conversion. The application is built with Tauri 2 (Rust) as the desktop shell, Vue 3 with TypeScript for the frontend, and a Python sidecar for the heavy processing tasks. Communication between the frontend and Python backend uses a JSON Lines protocol over stdin/stdout, with protobuf schemas defining the message envelopes. The architecture follows a clear separation of concerns: the Rust layer manages the application lifecycle, window effects, and sidecar process; the Vue frontend provides a drag-and-drop interface with task panels, persistent state management, and custom UI components; the Python backend implements a task runner that dispatches work to specialized service modules for EPUB structure manipulation, font obfuscation with ONNX OCR inference, image processing, and text conversion. The system includes a comprehensive test suite covering unit tests, integration tests, and protocol contract tests. Notable design patterns include a reusable EPUB workspace abstraction with security validation, a protocol layer with dataclass-based request/response models, safe JSON serialization handling edge cases like lone surrogates, and Vue composables for persistent state and Tauri IPC bridging. The font encryption/decryption services demonstrate advanced CSS cascade emulation and glyph rendering with OCR, though they contain significant code duplication. The README explicitly states that this repository is historical and that EPUB capabilities have been migrated to a Rust implementation (epub_tool_rust). As such, the project is deprecated and no longer actively developed, but the codebase remains a well-structured example of a cross-platform desktop application with a Python sidecar.
This repository is a Vue.js single-page application that demonstrates the use of the Composition API via the @vue/composition-api plugin in a Vue 2 project. It fetches data from the CNode API to display a list of topics, includes a search bar for filtering, and uses WeUI for styling. The application consists of a few components (Header, Search, Panel) and a simple global store for state management. While the code is functional and correctly implements the Composition API patterns, it suffers from tight coupling to the global store, outdated dependencies, and a lack of error handling or loading states, making it suitable for learning but not for production use without significant improvements.