lsabi opened a new issue, #2543: URL: https://github.com/apache/iggy/issues/2543
### Description of the problem and how to reproduce it Testing `Iggy` on servers running `podman`, it didn't work, while it worked locally without a problem. After some days I found out that the docs [https://iggy.apache.org/docs/server/configuration](https://iggy.apache.org/docs/server/configuration) are not clear if this is the default configuration that will be used or not from the server in case parameters are mising. ``` In case no configuration file is found, the server will use the default configuration. Let's take a look at the configuration file, and discuss the available options. ``` It led me into thinking that those parameters were the default ones if none are specified. Furthermore, on the next page for `docker` deploy, it only proposes to tweak some parameters for `docker-compose`, but also provides a run string that works locally and does not provide parameters, aside from the container/oci ones (see page [https://iggy.apache.org/docs/server/docker](https://iggy.apache.org/docs/server/docker)) Also, on the `README.md` file in the repo, there's just mention about overriding the default parameters ``` You can also use environment variables to override any configuration setting: Override TCP address IGGY_TCP_ADDRESS=0.0.0.0:8090 cargo run --bin iggy-server Set custom data path IGGY_SYSTEM_PATH=/data/iggy cargo run --bin iggy-server Enable HTTP transport IGGY_HTTP_ENABLED=true cargo run --bin iggy-server ``` but doesn't mention that 127.0.0.1:8090 is the default (and I thought 0.0.0.0:8090 was just as an example on the structure to be used) ``` docker run --cap-add=SYS_NICE --security-opt seccomp=unconfined --ulimit memlock=-1:-1 apache/iggy:edge ``` ### Solution Update the docs, mentioning that for server/public deploy, the default parameters work only locally (127.0.0.1) and instead it is needed to set the server's listening urls to `0.0.0.0:[port]` (where port is the port for the chosen protocol) Will there be a new section with best practices, tip and tricks for running in production? Or should it just be mentioned in the configuration parameters explanation? Let me know, so I can update the docs (where are they? In a separate repo?) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
