[Question] – How to specify a custom path to config.toml

[ChrisRichner]

Hi team,

Thanks for the great project!
When I run hubproxy with Docker‑Compose or Docker‑Swarm I hit a problem:

The container always looks for the configuration file at /root/config.toml.

In many setups (CI pipelines, different host folders, several instances with separate configs) it would be useful to choose our own path for the file.

Suggestion:
Add an environment variable (for example HUBPROXY_CONFIG or CONFIG_PATH) or a command‑line flag (--config ) that lets us tell the program where the config.toml file lives.

Thanks for your time!

[Rirmach]

Config path that the program would use is currently hardcoded ($WorkspaceDirectory/config.yaml):

hubproxy/src/config/config.go

Line 201 in 31f62fd

if data, err := os.ReadFile("config.toml"); err == nil {

For you, there are 3 options:

1. Deploy by docker (use docker compose):
   

   hubproxy/docker-compose.yml

   Line 9 in 31f62fd

   - ./src/config.toml:/root/config.toml

    volumes:
      - /path/to/config.toml:/root/config.toml # Change /path/to/config.toml to elsewhere you want

Do not concert about the config path inside the container

2. Deploy by systemd:
   

   hubproxy/hubproxy.service

   Line 10 in 31f62fd

   WorkingDirectory=/opt/hubproxy

   
   Change WorkingDirectory to elsewhere you want and put config.toml inside it

3. Modify source code
   

   hubproxy/src/config/config.go

   Line 201 in 31f62fd

   if data, err := os.ReadFile("config.toml"); err == nil {

   
   Modify config field inject chains (via environment variable and/or config file), consult LLM if needed
   Then, manual or via CI to build as your wish

PS. This project is far from stable, but it's quite simple to modify and build. So it's highly recommend to fork/PR or build your own hubproxy base on this project