Replace config.toml?

Is your feature request related to a problem? Please describe.

I'm using docker compose. Why must I define a separate file and bind-mount that to configure some values that could easily be set using environment variables in the docker-compose file? It significantly complicates the set-up.

Describe the solution you'd like Either deprecate the config.toml or make it optional. If we're using environment variables it can be replaced by a .env file, the environment of the docker compose file, or a docker-compose.override.yml.

Tangentially, I'd like the chat model provider and embedding model provider to be either configurable before startup, or automatically use Ollama if there's nothing set-up for openAI.

My end goal is to have a single docker-compose file that delivers a completely working Vane when I run docker-compose up. Now I need to write a readme to document several extra steps that must be done, or I need to write an install script that handles that.

Considerations

If you really want to offer a docker compose file that needn't be changed by the end user, and keep end-user configuration in a separate file, these seem suitable options:

• .env file. Can be a named file like vane.env and listed in env_file: in the docker-compose.yml
• docker-compose.override.yml