How aziontech/azion-console-kit works
Project type and purpose
• This is a front-end single-page application (“Azion Console Kit”) built with Vue 3 + Vite, styled with PrimeVue & Tailwind, that provides a customizable UI for managing Azion edge-platform resources (accounts, billing, edge apps, DNS, WAF, real-time events, metrics, etc.).
High-level file-structure analysis
• Top level: config files (Vite, Tailwind, Cypress), CI/CD workflows, scripts, Docker aliases.
• src/
• assets, layouts, templates, views & components → presentation layer
• router/ → vue-router configuration
• stores/ → Pinia/Vuex-style state management
• composables/ & helpers/ → reusable logic (domain/business helpers)
• services/ & services/axios/ → HTTP client adapters + API-specific service modules
• plugins/ → Vue plugins (analytics, factories)
• modules/ → feature-scoped sub-systems (AI-chat, real-time events, metrics)
• cypress/ → end-to-end tests
• .github/workflows/ → lint, test, deploy pipelines
Additional insights from README
• Targets two environments (stage/production) via VITE_ENVIRONMENT
• Supports local Docker alias for yarn
• Deploys statically (via Azion CLI) onto Azion’s edge/CDN
• Integrates Stripe for payments, plus many external APIs (GraphQL, WebPageTest, GitHub, Google Storage, StatusPage)
Main components & interactions (
A. Presentation Layer (in-browser SPA)
• Views/Templates/Components/Layouts
• Routing (vue-router)
• State (stores)
B. Domain Logic
• Composables & Helpers
• Feature Modules (azion-ai-chat, real-time-events, real-time-metrics)
C. Data Layer (API Services)
• AxiosHttpClientAdapter + SignalDecorator
• Service modules per domain (account-services, billing-services, edge-application-services, etc.)
• GraphQL client (makeGraphQl)
D. Plugins
• AnalyticsTrackerAdapterPlugin → tracks events to different trackers (ProductTracker, RealTimeMetricsTracker, etc.)
• Factories (analytics-tracking-factory, segment-token-factory)
E. External Services
• Azion Public API (REST & GraphQL)
• Stripe (payment processing)
• GitHub API, WebPageTest API, Google Storage, StatusPage API, third-party data-stream targets (Kafka, Splunk, BigQuery)
F. Deployment Pipeline
• GitHub Actions → CI (eslint, vitest, cypress) → npm build
• Azion CLI → deploy to edge/CDN for “stage” / “production”
Architectural patterns & design principles
• Layered separation: Presentation / Domain / Data
• Modular feature organization under src/modules
• Reusable building blocks: templates/, composables/, helpers/
• Centralized API client configuration via services/axios
• Immutable, centralized state (stores/)
• Declarative routing (router/routes/ per feature)