improve docker bits

.dockerignore

@@ -1,3 +1,6 @@
 node_modules
 config.json
+zampler
+zampler.files
+zampler.sqlite3
 .env

Dockerfile

@@ -22,4 +22,4 @@ FROM alpine:3.24
 COPY --from=go-build /build/zampler /usr/local/bin
 
 ENTRYPOINT ["zampler"]
-CMD ["/data"]
+CMD ["-s", "/db/zampler.sqlite3", "/data"]

README.md

@@ -48,7 +48,7 @@ Check out [go build](https://pkg.go.dev/cmd/go#hdr-Compile_packages_and_dependen
 
 ### Run Zampler
 
-Now that you have a `zampler` binary, you can start it by passing it the path(s) you want to scan:
+Now that you have a `zampler` binary, you can start it by passing it the path you want to serve files from:
 
 ```bash
 zampler /path/to/audio/files
@@ -56,10 +56,16 @@ zampler /path/to/audio/files
 
 When Zampler has started, it will tell you what URL to open in your browser to access the UI. This is normally <http://localhost:7777> but you can customise this. Run `zampler --help` for more usage information.
 
+#### SQLite database
+
+Zampler uses an SQLite database file to keep things organised and searchable. By default this is `zampler.sqlite3` in the current directory where you are running Zampler from. You can change this with the `--sqlite` flag; run `zampler --help` for more usage information.
+
 ### Docker
 
 The [Dockerfile](./Dockerfile) provides a basic recipe to build a lightweight Docker container that runs Zampler. This is not the recommended approach for most users, but it's available if Docker makes sense for your needs.
 
+By default, the SQLite database is written to `/db/zampler.sqlite3` and files are read from `/data` and both of these directories should be mounted according to your requirements.
+
 ## Development
 
 Follow the initial build instructions first, because the Go app still needs static assets in order to run.