mmosarafO2
380e336369
The Postgres, MySQL, MariaDB, SQL Server, MongoDB and Redis cards gain Docker and Kubernetes setup modes beside Automatic (script) and Manual. Both run otel/opentelemetry-collector-contrib at the DBM collector version with the card's own metrics config, and the Database Monitoring config for the Metrics + Database Monitoring variant. - Docker: one paste writes config.yaml (and dbm-config.yaml) into ./o2-<db>-collector/ and starts the image with docker run, the password env vars the configs read, host.docker.internal via --add-host, and for Postgres/MySQL/MariaDB DBM the database log directory mounted read-only. - Kubernetes: one kubectl apply of a Namespace, a Secret with the password env vars, a ConfigMap carrying the configs and a one-replica Deployment labelled app=o2-<db>-collector, then a rollout restart. - Each mode has its own host field (host.docker.internal, a cluster DNS name) while port, database and log path stay shared across modes. - Uninstall follows the selected mode: docker rm -f in Docker, kubectl delete by label in Kubernetes, the script's uninstall in Automatic.
web
This template should help get you started developing with Vue 3 in Vite.
Recommended IDE Setup
VSCode + Volar (and disable Vetur) + TypeScript Vue Plugin (Volar).
Type Support for .vue Imports in TS
TypeScript cannot handle type information for .vue imports by default, so we replace the tsc CLI with vue-tsc for type checking. In editors, we need TypeScript Vue Plugin (Volar) to make the TypeScript language service aware of .vue types.
If the standalone TypeScript plugin doesn't feel fast enough to you, Volar has also implemented a Take Over Mode that is more performant. You can enable it by the following steps:
- Disable the built-in TypeScript Extension
- Run
Extensions: Show Built-in Extensionsfrom VSCode's command palette - Find
TypeScript and JavaScript Language Features, right click and selectDisable (Workspace)
- Run
- Reload the VSCode window by running
Developer: Reload Windowfrom the command palette.
Customize configuration
See Vite Configuration Reference.
Project Setup
npm install
Compile and Hot-Reload for Development
For stand-alone UI development environment, create .env file and which contains below environment variable
VITE_OPENOBSERVE_ENDPOINT=http://localhost:5080/
npm run dev
Type-Check, Compile and Minify for Production
npm run build
Run Unit Tests with Vitest
npm run test:unit
Run End-to-End Tests with Cypress
npm run test:e2e:dev
This runs the end-to-end tests against the Vite development server. It is much faster than the production build.
But it's still recommended to test the production build with test:e2e before deploying (e.g. in CI environments):
npm run build
npm run test:e2e
Lint with ESLint
npm run lint