上一版把 master 的轨道也改名成 master,会把历史构建号搬到新键上。 改为 master/main 继续用现有的 release 轨(build_map 原地保留), 只有 develop 等其它上架分支新建以分支名命名的轨道并复制一份构建号。 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BJaZ913U5GVdTkYHiRpvDU
1.9 KiB
1.9 KiB
iOS Build Server
FastAPI + Vue 3 iOS app auto-packaging service. Supports Ad_Hoc and App_Store builds with web UI, real-time logs, multi-user auth, and health monitoring.
Tech Stack
- Backend: Python 3.9+, FastAPI, SQLAlchemy (SQLite), JWT auth
- Frontend: Vue 3, Vite, Vue Router
- Tests: pytest (backend), vitest (frontend)
- Deploy: macOS launchd, deploy.sh management script
Key Commands
./start.sh # Dev mode (backend + frontend hot reload)
./deploy.sh build # Install deps + build frontend
./deploy.sh start/stop/restart/status
./deploy.sh test # Run all tests (backend + frontend)
Architecture
backend/routers/— API routes: auth, users, config, apps, tasksbackend/services/— build_service (packaging), build_queue (async queue), log_streamer (WebSocket)backend/deps.py— JWT auth dependency used by all protected routesbackend/config.py— loads .env, defines all config constantsfrontend/src/views/— BuildView, HistoryView, ConfigViewconfig.json— runtime config (apps, schemes, servers, upload, branches, versions) managed via web UI- Versions are per-track: each release branch has its own track (master/main keeps the historical
releasetrack, others are named after the branch, e.g.develop; build number auto-increments on App_Store), and all self-test branches share thefeaturetrack (never increments); each branch's track name lives inconfig["branch_track"], track records inconfig["versions"]["tracks"]carrykind(release/feature)
Conventions
- All backend routes require JWT auth except
/api/auth/loginand/api/health - Admin-only routes: user management (
/api/users/*) and all of/api/config/*except/api/config/apps* - Config stored in
config.json(apps/schemes/servers),.env(infra), SQLitebuild_configtable (build settings) - Chinese UI and documentation throughout