Blocky commands do not run without local ./config.yml file

[schlamar]

I would expect that blocky commands like "blocky query" or "blocky blocking status" are using the HTTP API and require only the argument apiPort to work (and apiHost if it isn't running on localhost).

However, running a blocky command without a local ./config.yml file fails:

$ blocky --apiPort=4000 blocking status
FATA[0000] Can't read config file: open ./config.yml: no such file or directory

Additionally, I would suggest that you introduce a default API port so that blocky commands can run without any configuration argument for default installs.

I have installed blocky by FHS rules (/usr/local/bin/blocky, /etc/blocky/config.yml, /var/log/blocky/*.log) and using blocky in the shell is really cumbersome in this case.

[0xERR0R]

Yes, It makes sense. I changed the logic: config file is only for "server mode" mandatory. Other CLI commands will use port from config file only if the config file exist, otherwise only parameters from command line. Default host is localhost, default port is 4000 now.
If you use port 4000, you can just call blocky blocking status without other parameters