- feat: internal/api/openapi/openapi.yaml describes every operation (OpenAPI
3.0.3), written by hand and embedded in the binary; GET /api/v1/openapi.yaml
serves it
- feat: GET /api/docs/ serves Swagger UI from assets embedded in the binary
(github.com/swaggest/swgui, v5emb), so opening it never contacts another
server; both are public because they contain no data
- feat: response objects in the spec are closed (additionalProperties: false)
- test: the spec is valid OpenAPI; the router and the spec describe the same
operations in both directions; every operation has an id, a summary, a tag,
a documented 401 when it needs a token and a 403 when it is admin only
- test: a contract test drives every operation through the real services,
including a real scan and real streaming, and validates each response
(status, headers, JSON body) against the spec with kin-openapi; it fails if
an operation was never exercised. Checked by breaking the code and the spec
on purpose
- test: the docs page loads without any external address and every asset it
references is served
- docs: README section on the interactive documentation and on keeping the
spec in step with the code
Closes#15
- feat: the scan summary has an unsupported counter for audio files in formats
Sonda cannot read yet (m4a, ogg, opus, wav, wma, ...); they are counted and
never opened, instead of disappearing without a trace. Video containers such
as .mpg are not counted
- feat: folders named .@__thumb, @Recycle, #recycle, @eaDir, $RECYCLE.BIN and
System Volume Information are skipped, matched by exact name ignoring case,
so a NAS recycle bin does not end up in the library; a library whose own
folder carries one of these names is still scanned, and files indexed before
from such a folder are flagged missing like any vanished file
- docs: the README lists the new counter and the skipped folders
- test: system folders at any depth, near-miss names, a library inside a
system-named folder, entries flagged missing, unsupported counting
Closes#14
- what Sonda is, what works today and what does not
- build, configure (keys and environment variables) and use PostgreSQL
- a demo from an empty database to streaming a track with curl: first user,
library, scan, browse and search, Range streaming, listen events, token
refresh and logout, a second user
- the API at a glance, security notes, backups, tests (including the
PostgreSQL run) and the project layout
Closes#13