open-consul

History

Jack Pearkes 962421288b ui: kv layout improvements		2014-06-04 16:57:37 -04:00
..
dist	ui: ignore compiled js, dist	2014-05-01 11:22:30 -04:00
javascripts	ui: remove nodes debugging	2014-06-04 16:20:32 -04:00
scripts	ui: upgrade handlebars and use query params	2014-06-04 16:04:45 -04:00
static	ui: loading	2014-05-01 12:17:06 -04:00
styles	ui: kv layout improvements	2014-06-04 16:57:37 -04:00
tests
Gemfile
Gemfile.lock
index.html	ui: kv layout improvements	2014-06-04 16:57:37 -04:00
Makefile	ui: delete backup files	2014-05-01 12:45:15 -07:00
README.md	Minor Typo	2014-05-29 15:15:13 -04:00
style-guide.html

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 data centers, 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 .

Releasing

make dist

The dist folder will contain the files you should use for deployment.