Allowing IBC to change Read-Only API mode
tbrown122387 opened this issue · 1 comments
Your README says
IBC has decided not to support switching off the Read-Only checkbox (on by default) on the API Settings page.
However, this was changed in in a recent commit: IbcAlpha/IBC@ecb6f3d#diff-c8d8d62a34800f1c969ec30de080d73cb3d46a102c697d8d4b942e973c615f6f
Editing IBCLinux-3.8.2/config.ini to say ReadOnlyApi=no takes no effect, though. A newly built container will start in the read only mode, regardless of how config.iniends up.
What must one change to have this config file read in?
I see supervisord.conf calls /opt/IBController/scripts/ibcstart.sh. Should it call something else? The first comment in this file suggests that it be called from something else, and that it not be edited:
Note that this command file is a 'service file' intended to be called from
higher level command files. There should be no reason for the end user to modify
it in any way. So PLEASE DON'T CHANGE IT UNLESS YOU KNOW WHAT YOU'RE DOING!
I fixed it by replacing
- ./ib/IBController.ini:/root/IBController/IBController.ini
with
./IBCLinux-3.8.2/config.ini:/root/IBController/config.ini
in docker-compose.yml, and replacing
ENV IBC_INI=/root/IBController/IBController.ini
with
ENV IBC_INI=/root/IBController/config.ini
in Dockerfile and by removing COPY ./ib/IBController.ini /root/IBController/IBController.ini in the same file