consul/ui
Andy Lo-A-Foe 85d0f4b9ef Propagate token in UI 2015-11-18 08:29:01 +01:00
..
dist ui: ignore compiled js, dist 2014-05-01 11:22:30 -04:00
javascripts Propagate token in UI 2015-11-18 08:29:01 +01:00
scripts Moves the static assets into a subfolder where index.html expects them. 2015-10-27 18:19:17 -07:00
static website: document precedence of Atlas endpoint inputs 2015-08-27 17:54:56 -07:00
styles revert 8bf8871, fc2aad3, 503d338. 2015-08-07 16:40:49 -07:00
tests ui: add nodeShow test 2014-06-10 16:36:06 -04: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
Makefile Use gox for building 2015-10-22 14:16:01 -04:00
README.md s/data center/datacenter/g 2015-02-19 17:45:47 -05:00
development_config.json revert 8bf8871, fc2aad3, 503d338. 2015-08-07 16:40:49 -07:00
index.html Show node status as failing if a service on the node is failing 2015-10-26 10:26:16 -05:00
style-guide.html ui: add delete key functionality 2014-04-30 23:44:29 -04: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 dist folder will contain the files you should use for deployment.