Problem
The authentication directory in index.js and the SQLite filename in messages/MessageDatabase.js are hard-coded to ./auth and chat_history.db. This makes it difficult to deploy multiple instances, place persistent data on a mounted volume, or keep runtime data outside the source checkout.
Expected behavior
The current defaults should continue to work, while deployments can override the storage locations through documented configuration.
Suggested direction
Introduce environment variables with clear names and fallback defaults, then use the same values everywhere the auth state and database are opened. Document them in .env.example and the setup guide.
Acceptance criteria
- Existing installations continue using the current default paths when no variables are set.
- The auth directory can be configured independently from the database path.
- The configured paths are used consistently for reads, writes, and cleanup.
- The new variables are documented without exposing secrets.
Problem
The authentication directory in
index.jsand the SQLite filename inmessages/MessageDatabase.jsare hard-coded to./authandchat_history.db. This makes it difficult to deploy multiple instances, place persistent data on a mounted volume, or keep runtime data outside the source checkout.Expected behavior
The current defaults should continue to work, while deployments can override the storage locations through documented configuration.
Suggested direction
Introduce environment variables with clear names and fallback defaults, then use the same values everywhere the auth state and database are opened. Document them in
.env.exampleand the setup guide.Acceptance criteria