How mengjp810418/dbdiagram works
Project type and purpose
• This is a static single-page web application (SPA) that provides an open-source alternative to dbdiagram.io.
• There is no traditional “backend” server in the repo—persistence is handled by localStorage in the browser and by direct calls to an S3 bucket or equivalent object store.
File structure
• Top-level
– .github/workflows: CI/CD pipeline for building/deploying (GitHub Pages or static hosting).
– api/.gitkeep: placeholder for potential serverless API code.
• web/
– Quasar config & Dockerfile for containerized local dev or Nginx hosting.
– src/
· boot/: initialization scripts (Ace integration, i18n, Pinia store, numeric library).
· components/: Vue components for editor, graph, dialogs, export/import UI.
· i18n/: localization files.
· layouts/, pages/, router/: standard SPA structure.
· store/: Pinia stores (chart data, editor state, file repo).
· utils/: helper modules (storage, math).
– quasar.conf.js, babel.config.js, eslint, postcss, ts shims: build tool configuration.
README for additional insights
• Mentions Docker image, GitHub Pages live demo, JointJS and DBML parser dependencies.