How taipei-doit/taipei-city-dashboard works
Project type and purpose
• This is a comprehensive full-stack data visualization platform with three main domains:
• Taipei-City-Dashboard-FE (frontend SPA in Vue/Vite served via Nginx)
• Taipei-City-Dashboard-BE (Golang REST API with Redis cache, SQL database)
• Taipei-City-Dashboard-DE (Python-based Airflow-style DAGs deployed to Cloud Composer for ETL)
File structure
• Top-level folders:
• Taipei-City-Dashboard-FE → the Vue.js single-page frontend (src, public, assets, Dockerfile, Nginx)
• Taipei-City-Dashboard-BE → the Go backend (app/controllers, models, routes, middleware, cache, util), plus Dockerfiles, Cloud Build config, GitHub Actions
• Taipei-City-Dashboard-DE → data engineering pipelines (dags/proj_city_dashboard, utils, cicd, local_env for local Airflow testing)
• docker & local_env → Docker Compose configs for local orchestration (DB, init scripts, environment files)
• db-sample-data → sample SQL dumps
• CI/CD:
• .github/workflows/go.yml & node.js.yml for build/test/deploy
• Cloud Build YAML in BE and FE
• Configuration:
• .env templates, Dockerfiles, cloudbuild.yaml, composer DAG configs.
README for additional insights
• Confirms FE is Vue-based data visualization tool, BE is public REST API, DE pipelines run on Cloud Composer
• Project is open-source, encourages contributions and CI/CD integration.