Closed dvasdekis closed 4 years ago
Just to let you know, IBC 3.8.1 has fixed this issue, so you can fix this in your Docker image if you would like to! Since IBC >= 3.8.1, add the line "ReadOnlyApi=no" to IBController.ini. I can submit a pull request if you would like, but I wasn't sure how you wanted to handle this, whether with an env var or something?
An env var sounds like a great approach! Feel free to open a Pull Req. Thanks!
On Wed, Dec 16, 2020 at 7:08 AM Doug Swanson notifications@github.com wrote:
Just to let you know, IBC 3.8.1 has fixed this issue, so you can fix this in your Docker image if you would like to! Since IBC >= 3.8.1, add the line "ReadOnlyApi=no" to IBController.ini. I can submit a pull request if you would like, but I wasn't sure how you wanted to handle this, whether with an env var or something?
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/dvasdekis/ib-gateway-docker-gcp/issues/8#issuecomment-745568087, or unsubscribe https://github.com/notifications/unsubscribe-auth/AETC4JMOHHBHM44KLGYDY4DSU7F33ANCNFSM4O5TOKTA .
IBC has made a decision to not support disabling the read-only API. See here.
Therefore we need to allow users to write in their own ibg file