hoverctl expected behavior in regards to config and settings saved in .hoverfly/config.yaml

[John Taisto]

hoverfly@localhost ~> hoverctl version

+----------+----------+
| hoverctl |          |
| hoverfly | v0.15.1  |
+----------+----------+
hoverfly@localhost ~>


Is the following expected behavior or is it a bug?  I don't see it as an issue yet in github, so I'm hoping someone here can point me to this being a bug or this is designed behavior.  Thanks.

hoverfly@localhost ~> hoverctl status
Could not connect to Hoverfly at localhost:8888

hoverfly@localhost ~> cat .hoverfly/config.yaml
default: local
targets:
  local:
    name: local
    host: localhost
    admin.port: 8888
    proxy.port: 8500
    authenabled: false
    username: "test"
    password: "test123"

hoverfly@localhost ~> hoverctl config
/opt/QL/app/hoverfly/.hoverfly/config.yaml
default: local
targets:
  local:
    name: local
    host: localhost
    admin.port: 8888
    proxy.port: 8500
    authenabled: false
    username: "test"
    password: "test123"

hoverfly@localhost ~> hoverctl status
Could not connect to Hoverfly at localhost:8888

hoverfly@localhost ~> hoverctl config
/opt/QL/app/hoverfly/.hoverfly/config.yaml
default: local
targets:
  local:
    name: local
    host: localhost
    admin.port: 8888
    proxy.port: 8500
    authenabled: false
    username: ""
    password: ""

[Tommy Situ]

Hi John, 

What is the problem exactly? Is it about `hoverctl status` not be able to connect to hoverfly? If that's the case, is your hoverfly already running? You can check by going to `localhost:8888` in your browser, or run `ps -ef | grep hoverfly` in command line if you are using mac or linux.

Thanks, 
Tommy