How chargepi/chargepi-go works
Project type and purpose
• ChargePi-go is a full-stack, modular EV charging point framework:
• Backend in Go (monolithic service with CLI, gRPC & HTTP APIs, hardware drivers, scheduler, smart-charging logic, persistence)
• Frontend UI in SvelteKit
• Docker‐based deployment and configuration management
• Hardware‐abstraction plugins (charge-point controllers, meters, displays, RFID readers)
• Purpose: unify disparate hardware into an OCPP 1.6/2.0.1-compliant charge point with API & UI for management, extensibility, and simulation.
File structure
• Top-level:
• cmd/ – CLI entry points: import, export, run, version
• internal/ – core application packages (api, auth, chargepoint, evse, diagnostics, sessions, smart‐charging, users)
• pkg/ – hardware drivers & utilities (display, indicator, power-meter, reader, observability)
• proto & gen/proto – protobuf definitions and generated gRPC code
• ui/ – frontend SvelteKit app
• deployments/docker – docker-compose for full stack
• scripts – environment setup, certificate generation
• main.go – application bootstrap
• build/Dockerfile – container image build
• Notice clean-architecture flavors:
• Adapters: internal/api/grpc, internal/api/http
• Domain & service layers: internal/chargepoint, sessions, smart-charging, users
• Infrastructure: internal/pkg/database (Badger), internal/pkg/settings, hardware plugins in pkg/
README insights
• Confirms modular, hardware-agnostic design
• Highlights OCPP protocol support (via internal/chargepoint and protobuf)
• Describes API, UI, simulator & demo modes
• Notes “framework” pattern – plugin‐style hardware drivers
a. Main components
• Frontend UI (SvelteKit)
• Backend service
– CLI layer (cmd/)
– API layer:
· HTTP server (internal/api/http, UI hosting, REST/JSON endpoints)
· gRPC server (internal/api/grpc)
– Domain services:
· Charge-point controller (internal/chargepoint)
· EVSE manager & device abstractions (internal/evse)
· Smart-charging scheduler (internal/smart-charging, internal/pkg/scheduler)
· Auth & session management (internal/auth, internal/sessions)
· User management (internal/users)
· Diagnostics (internal/diagnostics)
– Persistence:
· Settings & configuration manager (internal/pkg/settings)
· Database layer (internal/pkg/database, sessions & user Badger stores)
– Hardware plugins (pkg/display, pkg/reader, pkg/power-meter, pkg/indicator, pkg/evcc)
– Observability (pkg/observability)
• External systems
– OCPP Central System (over WebSocket/JSON via chargepoint module)
– Optional MQTT or other external integrations via API
b. Relationships & interactions
• UI ↔ HTTP API
• CLI ↔ domain services for import/export/configuration
• HTTP/gRPC API ↔ domain services
• Domain services ↔ hardware drivers via adapter interfaces
• Domain services ↔ persistence layer
• Charge-point ↔ external OCPP CS over network
c. Architectural patterns
• Clean/hexagonal architecture: clear separation of adapters (API, CLI), application logic (services), and infrastructure (database, drivers)
• Plugin architecture for hardware: loadable drivers under pkg/ and docs/contribution
• Event/scheduler pattern for smart-charging
d. Key technologies & frameworks
• Go modules, Go-Generate for protobuf (buf, protoc)
• gRPC + protobuf (proto/, gen/proto/)
• HTTP server (built-in net/http, SvelteKit for UI)
• Badger embedded KV store for sessions and users
• Docker & docker-compose for deployment
• SvelteKit, TailwindCSS for UI
Elements
• Labels
– UI, HTTP API, gRPC API, CLI, Domain Services, Persistence, Hardware Drivers, External OCPP CS
– UI → HTTP API → Domain Services → Drivers
– Domain Services ↔ DB
– Charge-point module → External OCPP CS