How sullaspqr/dobok works
This is a small Express application for managing a drum catalog through CRUD HTTP endpoints. Requests reach the API, which reads and mutates a seeded in-memory array; changes are not shown being persisted to a database. The app also serves static files and exposes generated Swagger documentation. The README describes starting the server, but does not document a separate client workflow. The map reflects the single sampled runtime file; the PDF’s role is unclear.
Main entry points: server.js Drum CRUD API · public Static Files
Components 6
Drum API
- Drum CRUD API
server.js - Express App
server.js
Catalog State
- In-Memory Drums
server.js
Serving and Docs
- Swagger UI
server.js - Static Files
public
Other components
- HTTP Client
Connections 6
- HTTP Client → Drum CRUD API: sends requests
server.js - Drum CRUD API → In-Memory Drums: reads and mutates
server.js - Drum CRUD API → HTTP Client: returns JSON
server.js - Express App → Drum CRUD API: routes requests
server.js - Express App → Swagger UI: mounts at /swagger
server.js - Express App → Static Files: serves static files
server.js