luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity
open-consul/ui
History
James Phillips 1955eadc12 Updates web assets to pull in RTT viz. 2016-06-07 09:32:44 -07:00
..
javascripts Implement a first-pass of tomography node hover 2016-05-18 10:05:16 -07:00
scripts Moves the static assets into a subfolder where index.html expects them. 2015-10-27 18:19:17 -07:00
static Updates web assets to pull in RTT viz. 2016-06-07 09:32:44 -07:00
styles Implement a first-pass of tomography node hover 2016-05-18 10:05:16 -07:00
tests ui: add nodeShow test 2014-06-10 16:36:06 -04:00
GNUmakefile Acknowledge that we're using GNU make's dialect and rename appropriate 2016-02-05 14:24:26 -08:00
Gemfile ui: update ember, dist steps 2014-05-01 11:21:55 -04:00
Gemfile.lock revert 8bf8871, fc2aad3, 503d338. 2015-08-07 16:40:49 -07:00
README.md Fixes the static asset generator for new pkg path, updates assets. 2016-01-15 10:21:42 -08:00
development_config.json revert 8bf8871, fc2aad3, 503d338. 2015-08-07 16:40:49 -07:00
index.html Implement a first-pass of tomography node hover 2016-05-18 10:05:16 -07:00
style-guide.html Use HTTPS + www. where appropriate 2016-01-13 17:44:01 -05:00

README.md

Consul Web UI

This directory contains the Consul Web UI. Consul contains a built-in HTTP server that serves this directory, but any common HTTP server is capable of serving it.

It uses JavaScript and Ember to communicate with the Consul API. The basic features it provides are:

  • Service view. A list of your registered services, their health and the nodes they run on.
  • Node view. A list of your registered nodes, the services running on each and the health of the node.
  • Key/value view and update

It's aware of multiple datacenters, so you can get a quick global overview before drilling into specific data-centers for detailed views.

The UI uses some internal undocumented HTTP APIs to optimize performance and usability.

Development

Improvements and bug fixes are welcome and encouraged for the Web UI.

You'll need sass to compile CSS stylesheets. Install that with bundler:

cd ui/
bundle

Reloading compilation for development:

make watch

Consul ships with an HTTP server for the API and UI. By default, when you run the agent, it is off. However, if you pass a -ui-dir flag with a path to this directory, you'll be able to access the UI via the Consul HTTP server address, which defaults to localhost:8500/ui.

An example of this command, from inside the ui/ directory, would be:

consul agent -bootstrap -server -data-dir /tmp/ -ui-dir .

Basic tests can be run by adding the ?test query parameter to the application.

When developing Consul, it's recommended that you use the included development configuration.

consul agent -config-file=development_config.json

Releasing

make dist

The ../pkg/web_ui folder will contain the files you should use for deployment.

###Acknowledgements cog icon by useiconic.com from the Noun Project

Compiling the UI into the Go binary

The UI is compiled and shipped with the Consul go binary. The generated bindata file lives in the command/agent/bindata_assetfs.go file and is checked into source control. This is useful so that not every Consul developer needs to set up bundler etc. To re-generate the file, first follow the compilation steps above to build the UI assets into the pkg/web_ui folder. With that done, from the root of the Consul repo, run:

$ make static-assets

The file will now be refreshed with the current UI data. You can now rebuild the Consul binary normally with make bin or make dev, and see the updated UI after re-launching Consul.