tajniak81andClaude Opus 5
143917f0bb
The Anker protocol maps are kept out of the tree as local copies of published artifacts; the Toyota API map is the same kind of file and joins the rule. The file itself stays on disk. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
23 lines
420 B
Plaintext
23 lines
420 B
Plaintext
# Design assets / source (not tracked)
|
|
Design/
|
|
|
|
# Dependencies (covers API Server/panel/node_modules, etc.)
|
|
node_modules/
|
|
|
|
# OS / editor cruft
|
|
.DS_Store
|
|
Thumbs.db
|
|
*.log
|
|
.vscode/*
|
|
!.vscode/extensions.json
|
|
.idea/
|
|
|
|
# Secrets
|
|
.env
|
|
*.env.local
|
|
|
|
# Local reference copies of the published protocol map artifacts
|
|
# (Anker: Modbus TCP, cloud MQTT, cloud REST API, OCPP; Toyota: cloud REST API)
|
|
anker-*-map.html
|
|
toyota-*-map.html
|