# DR网页版 **Repository Path**: my-vibe-coding/droiyan-web ## Basic Information - **Project Name**: DR网页版 - **Description**: 利用AI开发DR Web版本。(仅用于技术研究) - **Primary Language**: Unknown - **License**: Not specified - **Default Branch**: master - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 0 - **Created**: 2026-11-12 - **Last Updated**: 2026-11-13 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README # Droiyan Online Codebase Learning and preservation repository for the original Droiyan Online server and related tooling, alongside a cross-platform server rewrite and its client-facing components. ## Repository Layout | Path | Purpose | |------|---------| | `references/Server/`, `references/LoginTool/` | Legacy Windows/MFC implementation, retained as a behavior and protocol reference. | | `server/` | Cross-platform C++17/CMake server rewrite and its build/run instructions. | | `gateway/` | WebSocket-to-TCP gateway for the web client. | | `webclient/` | New web client. | | `protocols/` | Protocol contracts and current interface status. | | `db/` | Database baseline and related scripts; local database files and credentials do not belong here. | | `rag/` | Auxiliary retrieval tools; review its source and local data separately before staging. | Start with [protocols/README.md](protocols/README.md) for component boundaries and protocol documentation, then use each component's README for setup. The legacy tree is not the runtime dependency of the new server. The database baseline is `repo`; the incompatible P3b schema is reference material only. ## Repository Organization Record - 2026-11-12: created `references/` and moved `Server/` and `LoginTool/` into it; renamed `server_new/` to `server/` and `client_new/` to `webclient/`; added `.screenshots/`, `/build`, `/build-*`, `logs/`, and Python artifact ignore rules. Details in [adjust.md](adjust.md). - Existing worktree changes in the legacy tree and previously added new components remain subject to review; this note does not claim that they have been staged, committed, or individually audited. - Before staging, review local configuration and runtime data, credentials, generated build output, reverse-engineering artifacts, downloaded references, and tool state. Keep `.env`, `.screenshots/`, `build/`, `logs/`, `downloads/`, `ref_docs/`, and `ref_net_docs/` out of commits. - Current worktree status and component-level acceptance should be checked before preparing a commit. This record describes the organization boundary, not a claim that a commit has been created.