OpenAthlete
AGPLv3 endurance training platform: EU-oriented hosting, transparent CTL/ATL/TSB logic in code, self-hosting, and full export. Built in Grenoble.
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證正在載入完整 README。 以下為已儲存的摘錄。
Angular single-page application for Berliz, a fitness and combat sports platform connecting trainers, gyms, and clients through profiles, bookings, and content.
See docs/TECH_STACK.md for a full breakdown of every library in use and why it's here, and docs/ARCHITECTURE.md for how the app is structured.
• Node.js 18+
• Angular CLI (npm install -g @angular/cli)檢視完整 README ↗Angular single-page application for Berliz, a fitness and combat sports platform connecting trainers, gyms, and clients through profiles, bookings, and content.
Live: berliz.fitness
Angular 16 · TypeScript · NgRx · Tailwind CSS · RxJS
See docs/TECH_STACK.md for a full breakdown of every library in use and why it's here, and docs/ARCHITECTURE.md for how the app is structured.
npm install -g @angular/cli)git clone https://github.com/blessedtasela/berliz.git
cd berliz
npm install
Configuration lives in src/environments/environment.ts (development) and environment.prod.ts (production, swapped in automatically by angular.json's fileReplacements on a production build) — not a .env file. Copy the shape of environment.ts if you need to point at a different backend locally.
ng serve
Opens at http://localhost:4200, proxying API calls to whatever environment.api points at (defaults to a local backend at http://localhost:8080).
ng build # development build
ng build --configuration=production # production build, used by Netlify
Output goes to dist/berliz/.
ng test
Netlify builds and deploys automatically on every push to master (see netlify.toml). Cloudflare sits in front of the custom domain for DNS and SSL. Full details in docs/DEPLOYMENT.md.
src/
app/
admin/ # Admin-only management screens (users, centers, trainers, content, etc.)
services/ # HTTP services, auth interceptor, shared business logic
state/ # NgRx: actions, reducers, effects, selectors
shared/ # Reusable components, pipes, directives
models/ # TypeScript interfaces for API data shapes
utils/ # Framework-agnostic helper functions
... # Feature areas (trainers/, centers/, categories/, etc.), each
# typically paired with an admin/<feature> counterpart
environments/ # environment.ts / environment.prod.ts — build-time config
legacy/ # Pre-NgRx state services, kept for reference during migration
angular.json # Angular CLI / build configuration
netlify.toml # Netlify build & deploy configuration
docs/ # Architecture, setup, deployment, roadmap, API, tech stack docs
docs/ARCHITECTURE.md — how the pieces fit togetherdocs/SETUP.md — detailed local setupdocs/DEPLOYMENT.md — how production deploys workdocs/API.md — backend API reference from the frontend's perspectivedocs/ROADMAP.md — what's built and what's planneddocs/TECH_STACK.md — every technology in use, and why