1088a5c170
add ability to specify response headers on the HTTP API |
||
|---|---|---|
| .. | ||
| dist | ||
| javascripts | ||
| scripts | ||
| static | ||
| styles | ||
| tests | ||
| Gemfile | ||
| Gemfile.lock | ||
| Makefile | ||
| README.md | ||
| development_config.json | ||
| index.html | ||
| 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 .
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.