nginx - Xdebug with PHPStorm and a Docker container -

-

setup: windows 10; docker running boot2docker on hyper-v; phpstorm 9

webserver on vm nginx. i've configured xdebug.ini php5-fpm as:

zend_extension=xdebug.so xdebug.remote_enable=on xdebug.remote_port=9000 xdebug.remote_connect_back=on xdebug.remote_handler=dbgp xdebug.profiler_enable=0

if set breakpoint , reload page incoming connection xdebug in phpstorm:

incoming connection

i wonder there 1 file shown , not entire project bigger. if accept connection can debug first line not stopping on breakpoint , creates server entry looks like:

server what strange host empty. added server correct mapping got ignored.

so how xdebug stop on breakpoints?

what strange host empty.

phpstorm requires field filled uses recognize server entry (and therefore path mappings) use -- ide supports debugging same code base running on different domains / remote servers.

in particular case servername field / parameter of nginx configuration empty. can fix providing value in nginx config file.


Comments

Post a Comment

Popular posts from this blog

java - Date formats difference between yyyy-MM-dd'T'HH:mm:ss and yyyy-MM-dd'T'HH:mm:ssXXX -

-
i trying parse date 2014-12-03t10:05:59.5646+08:00 using these 2 formats: yyyy-mm-dd't'hh:mm:ss yyyy-mm-dd't'hh:mm:ssxxx when parse using yyyy-mm-dd't'hh:mm:ss works fine, when parse yyyy-mm-dd't'hh:mm:ssxxx parseexception thrown. which correct format parse date , difference between these 2 formats? note : cannot use joda :( those valid formats: yyyy-mm-dd't'hh:mm:ss.sssz >>> e.g.: 2001-07-04t12:08:56.235-0700 yyyy-mm-dd't'hh:mm:ss.sssxxx >>> e.g.: 2001-07-04t12:08:56.235-07:00 edit: btw, "x" refer (iso 8601 time zone)
Read more

c# - Get rid of xmlns attribute when adding node to existing xml -

-
i have xml-file: <ns2:root xmlns:ns2="namespace"> <ns2:a> <ns2:b>some content</b> <ns2:c>some content</c> <ns2:d>some content</d> </a> </root> i need add new node in specific place, code is: var doc = xdocument.load(file); xnamespace ns2 = "namespace"; doc.element(ns2 + "root").element(ns2 + "a").element(ns2 + "c").addafterself( new xelement(ns2+"new", new xelement("new1", new xelement("new2","some content"), new xelement("new3", "some content")))); the output is: <ns2:root xmlns:ns2="namespace"> <ns2:a> <ns2:b>some content</b> <ns2:c>some content</c> <ns2:new> <new1 xmlns=""> <new2>some content</new2> ...
Read more