HaHafeng
66255368b7
Features - User Management (Phase 4.1): - Database: Add user_modules table for fine-grained module permissions - Database: Add 4 user permissions (view/create/edit/delete) to role_permissions - Backend: UserService (780 lines) - CRUD with tenant isolation - Backend: UserController + UserRoutes (648 lines) - 13 API endpoints - Backend: Batch import users from Excel - Frontend: UserListPage (412 lines) - list/filter/search/pagination - Frontend: UserFormPage (341 lines) - create/edit with module config - Frontend: UserDetailPage (393 lines) - details/tenant/module management - Frontend: 3 modal components (592 lines) - import/assign/configure - API: GET/POST/PUT/DELETE /api/admin/users/* endpoints Architecture Upgrade - Module Permission System: - Backend: Add getUserModules() method in auth.service - Backend: Login API returns modules array in user object - Frontend: AuthContext adds hasModule() method - Frontend: Navigation filters modules based on user.modules - Frontend: RouteGuard checks requiredModule instead of requiredVersion - Frontend: Remove deprecated version-based permission system - UX: Only show accessible modules in navigation (clean UI) - UX: Smart redirect after login (avoid 403 for regular users) Fixes: - Fix UTF-8 encoding corruption in ~100 docs files - Fix pageSize type conversion in userService (String to Number) - Fix authUser undefined error in TopNavigation - Fix login redirect logic with role-based access check - Update Git commit guidelines v1.2 with UTF-8 safety rules Database Changes: - CREATE TABLE user_modules (user_id, tenant_id, module_code, is_enabled) - ADD UNIQUE CONSTRAINT (user_id, tenant_id, module_code) - INSERT 4 permissions + role assignments - UPDATE PUBLIC tenant with 8 module subscriptions Technical: - Backend: 5 new files (~2400 lines) - Frontend: 10 new files (~2500 lines) - Docs: 1 development record + 2 status updates + 1 guideline update - Total: ~4900 lines of code Status: User management 100% complete, module permission system operational
91 lines
2.1 KiB
Markdown
91 lines
2.1 KiB
Markdown
# 架构实施
|
||
|
||
> **文档定位：** 架构演进、技术改造、工程实践
|
||
> **适用范围：** 技术架构师、技术负责人
|
||
|
||
---
|
||
|
||
## 📋 目录结构
|
||
|
||
```
|
||
09-架构实施/
|
||
├── 02-数据库连接配置.md # ✅ Schema隔离的数据库配置
|
||
├── migration-scripts/ # ⏳ Schema迁移SQL脚本（Week 1创建）
|
||
├── 01-Monorepo架构设计/ # ⏳ Monorepo转换方案
|
||
├── 02-产品打包方案/ # ⏳ 独立产品打包流程
|
||
└── 03-微服务拆分/ # ⏳ 微服务拆分策略
|
||
```
|
||
|
||
---
|
||
|
||
## 🎯 核心内容
|
||
|
||
### 1. Monorepo架构设计
|
||
- Monorepo总体设计
|
||
- 包管理策略（pnpm workspaces）
|
||
- 代码共享与复用
|
||
- 构建和部署
|
||
|
||
### 2. 产品打包方案
|
||
- 独立产品打包流程
|
||
- 依赖管理
|
||
- 构建脚本
|
||
- 版本管理
|
||
|
||
### 3. 微服务拆分
|
||
- 拆分策略和时机
|
||
- 服务间通信
|
||
- API网关配置
|
||
- 数据迁移
|
||
|
||
---
|
||
|
||
## 📅 实施计划
|
||
|
||
### 阶段一：模块化单体（当前）
|
||
- 严格代码隔离
|
||
- Schema隔离（逻辑）
|
||
- 模块化设计
|
||
|
||
### 阶段二：首次拆分（6-18个月）
|
||
- Monorepo转换
|
||
- Schema物理隔离
|
||
- 拆分独立系统（RVW）
|
||
- 引入API网关
|
||
|
||
### 阶段三：全面微服务（18个月+）
|
||
- 所有模块独立部署
|
||
- K8s编排
|
||
- 服务网格
|
||
|
||
---
|
||
|
||
## 📚 快速导航
|
||
|
||
### 当前实施中（Week 1）
|
||
1. [数据库连接配置](./02-数据库连接配置.md) - ✅ Schema隔离迁移配置
|
||
2. [迁移SQL脚本](./migration-scripts/) - ⏳ Week 1创建
|
||
|
||
### 未来实施
|
||
3. [Monorepo架构设计](./01-Monorepo架构设计/README.md) - ⏳ 待规划
|
||
4. [产品打包方案](./02-产品打包方案/README.md) - ⏳ 待规划
|
||
5. [微服务拆分](./03-微服务拆分/README.md) - ⏳ 待规划
|
||
|
||
---
|
||
|
||
## 🔗 相关文档
|
||
|
||
- [Monorepo架构评估](../00-系统总体设计/07-Monorepo架构评估.md)
|
||
- [模块独立部署方案](../00-系统总体设计/06-模块独立部署与单机版方案.md)
|
||
- [Schema隔离方案](../00-系统总体设计/05-Schema隔离方案与成本分析.md)
|
||
|
||
---
|
||
|
||
**最后更新：** 2025-11-06
|
||
**维护人：** 技术架构师
|
||
|
||
|
||
|
||
|
||
|