How dvelagui/gol360 works
Project Type and Purpose
• This is a full-stack Single Page Application built with Quasar (Vue.js) and hosted on Firebase.
• Frontend: Quasar/Vue app under src/, leveraging Vuex-style stores, Vue Router, and composables.
• Backend: Firebase Cloud Functions in functions/ for server-side logic and API wrappers (e.g., VEO integration).
• Database & Hosting: Firestore (NoSQL), Firebase Authentication, and Firebase Hosting for static assets.
File Structure Analysis
• Top-level:
• src/ – Quasar app (components/, pages/, layouts/, router/, stores/, services/)
• public/ & index.html – static assets & root HTML
• functions/ – Firebase Cloud Functions (TypeScript)
• firebase.json, .firebaserc – hosting & functions deployment config
• Architectural patterns:
• Modular services under src/services/ for API calls (accountService, tournamentService, etc.)
• Centralized state stores under src/stores/
• Boot files for initializing Firebase SDK and Axios
• Cloud Functions handle secure operations & wrap external VEO API
Key README Insights
• Uses Quasar CLI with Vite for dev & build.
• Deploy via quasar build + firebase deploy.
Detailed Capture of Architectural Elements
• Under Functions, show sub-modules: veo/api.ts, auth.ts, pkce.ts, and their connection to Firestore or VEO API.
• Deploy pipeline: Quasar build → Firebase Hosting & Functions deployment.