Files
weave-scope/client
Simon Howe 1b78427fb9 Keep scroll position if we scroll away from the bottom of the term
aka, scroll locking. Allows you to scroll back through logs without new
log data dragging the scroll back down to the next entries as they come
in.
2016-11-01 11:44:29 +01:00
..
2016-04-20 12:33:22 +02:00
2016-09-15 11:55:25 +02:00
2015-11-11 18:42:48 +01:00
2015-05-20 10:45:35 +00:00
2016-04-05 15:45:13 +02:00
2016-04-27 17:21:46 +02:00
2015-05-19 10:02:02 +00:00
2016-04-20 12:33:22 +02:00
2016-09-28 13:04:55 -07:00
2016-09-15 11:55:25 +02:00

Scope UI

Getting Started (using local node)

  • You need nodejs 4.2.2 and a running weavescope container
  • Setup: npm install
  • Develop: BACKEND_HOST=<dockerhost-ip> npm start and then open http://localhost:4042/

This will start a webpack-dev-server that serves the UI and proxies API requests to the container.

Getting Started (using node in a container)

  • You need a running weavescope container
  • Develop: make WEBPACK_SERVER_HOST=<dockerhost-ip> client-start and then open http://<dockerhost-ip>:4042/

This will start a webpack-dev-server that serves the UI from the UI build container and proxies API requests to the weavescope container.

Test Production Bundles Locally

  • Build: npm run build, output will be in build/
  • Serve files from build/: BACKEND_HOST=<dockerhost-ip> npm run start-production and then open http://localhost:4042/

Coding

This directory has a .eslintrc, make sure your editor supports linter hints. To run a linter, you also run npm run lint.

Logging

To enable logging in the console, activate it via localStorage in the dev tools console:

localStorage["debug"] = "scope:*"

The Scope UI uses debug for logging, e.g.,:

const debug = require('debug')('scope:app-store');
debug('Store log message');

Gotchas

Got a blank screen when loading http://localhost:4042?

Make sure you are accessing the right machine: If you're running npm start on a virtual machine with IP 10.0.0.8, you need to point your browser to http://10.0.0.8:4042. Also, you may need to manually configure the virtual machine to expose ports 4041 (webpack-dev-server) and 4042 (express proxy).