Help with accessing app through browser, container id questions, inter alia about cheesy-poofs HOT 9 CLOSED

The README has the link to pull up the app in the browser:

https://github.com/zehnergroup/cheesy-poofs#access-app

Basically, go to: http://docker.local:8004

from cheesy-poofs.

Also, the container that matters is the one named cp-frontend. So it's the container ID for that container that you should use when running other docker commands, like docker exec

from cheesy-poofs.

@duro Well that was quick!

I guess I missed that and instead tried to access http://docker.local:8383/debug?ws=docker.local:8384&port=5354 - is this supposed to work out of the box or should there be more configuration?

from cheesy-poofs.

That is the URL for the debugger, which should work out of the box.

The app is basically a boilerplate, it gives you a starter, and then you extend from there.

from cheesy-poofs.

Can I debug why the debugger isn't working? I'm getting a connection refused.

EDIT:
http://docker.local:8384/debug?ws=docker.local:8384&port=5354 works

http://docker.local:8383/debug?ws=docker.local:8384&port=5354 doesn't

Maybe need to update README.txt?

from cheesy-poofs.

Updating README

from cheesy-poofs.

Thanks so much for the help!

from cheesy-poofs.

Fixed. Also, I updated node-debugger to the lastest version. If you do a fresh pull, then vagrant reload you should get the update.

from cheesy-poofs.

@duro Awesome, looks like server-side breaks are working now in the debugger (though it may have just been negligence on my part).

from cheesy-poofs.