From my analysis, the stats.db file cannot exist in a Docker container persistently. Since the file is created in the app’s root folder, it can only be extracted from a running environment and mapped, making a consistent Docker deployment not perfect.

A suggestion would be to create a separate folder (like ./data) and store app files in this folder, which could be created automatically by code and then mapped as a Docker volume, containing config.yaml and stats.db.

Taking a step further, and optionally (perhaps even a separate future issue), all configurations could be set by environment vars. This is merely hypothetical discussion as of now.