This has been a problem for a while, but I hadn't filed an issue. I expect per the README instructions that backend:watch will launch the server and monitor the filesystem for changes. What happens is that GOROOT=$HOME/local/google-cloud-sdk/platform/google_appengine/goroot APPENGINE_DEV_APPSERVER=$(which dev_appserver.py) gulp backend:watch terminates with exit code 0, and the server isn't launched.
This has been a problem for a while, but I hadn't filed an issue. I expect per the README instructions that
backend:watch
will launch the server and monitor the filesystem for changes. What happens is thatGOROOT=$HOME/local/google-cloud-sdk/platform/google_appengine/goroot APPENGINE_DEV_APPSERVER=$(which dev_appserver.py) gulp backend:watch
terminates with exit code 0, and the server isn't launched.Node v5.5.0, gulp 3.9.1, on my Goobuntu desktop.
gulp backend:serve
does launch the server at http://localhost:8080/ and monitors changes.