History

Michael Lange f747cc79e4 Revert "UI Placement failures"" This reverts commits 141ecd8d9170f56c8302b5c776532e6d287a40e3 d2d838c2de08aac716a9431d9720b5c12bb19ba1 8099db433641429816e8479c6d23116269f744c0 86262b3ceff607627a9c9e0e25eb81b9b5ee739c eb4104ec528982e0ee6ae9a05fb0460e53139f3f 0e0e23e238017815bdb6dcfbc056275b3deaacca 6d45658d77fb4c40760a63cced71b74757356e48 b52a8176e85b9c6f13ec012f7fce2ec3df1c8751		2017-11-29 20:03:39 -08:00
..
app	Revert "UI Placement failures""	2017-11-29 20:03:39 -08:00
config
lib/bulma
mirage	Revert "UI Placement failures""	2017-11-29 20:03:39 -08:00
public	New icons for pausing and playing	2017-11-21 11:22:42 -08:00
tests	Revert "UI Placement failures""	2017-11-29 20:03:39 -08:00
vendor
.editorconfig
.ember-cli
.eslintignore
.eslintrc.js	New eslint rule for ember-concurrency infinite loop pattern	2017-11-21 11:22:42 -08:00
.travis.yml
.watchmanconfig
ember-cli-build.js	Add new icon helper and the first icon: warning	2017-10-03 10:54:22 -07:00
package.json	Add ember-concurrency dependency	2017-11-21 11:22:41 -08:00
README.md
testem.js
yarn.lock	Add ember-concurrency dependency	2017-11-21 11:22:41 -08:00

README.md

Nomad UI

The official Nomad UI.

Prerequisites

This is an ember.js project, and you will need the following tools installed on your computer.

Node.js
Yarn
Ember CLI
PhantomJS (for running tests)

Installation

The Nomad UI gets cloned along with the rest of Nomad. To install dependencies, do the following from the root of the Nomad project:

$ cd ui
$ yarn

Running / Development

First, make sure nomad is running. The UI, in development mode, runs independently from Nomad, so this could be an official release or a dev branch. Likewise, Nomad can be running in server mode or dev mode. As long as the API is accessible, the UI will work as expected.

ember serve
Visit your app at http://localhost:4200.

Running / Development with Vagrant

All necessary tools for UI development are installed as part of the Vagrantfile. This is primarily to make it easy to build the UI from source while working on Nomad. Due to the filesystem requirements of Broccoli (which powers Ember CLI), it is strongly discouraged to use Vagrant for developing changes to the UI.

That said, development with Vagrant is still possible, but the ember serve command requires two modifications:

--watch polling: This allows the vm to notice file changes made in the host environment.
--port 4201: The default port 4200 is not forwarded, since local development is recommended.

This makes the full command for running the UI in development mode in Vagrant:

$ ember serve --watch polling --port 4201

Running Tests

Nomad UI tests can be run independently of Nomad golang tests.

ember test (single run, headless browser)
ember test --server (watches for changes, runs in a full browser)

Building

Typically make release or make dev-ui will be the desired build workflow, but in the event that build artifacts need to be inspected, ember build will output compiled files in ui/dist.

ember build (development)
ember build --environment production (production)

Releasing

Nomad UI releases are in lockstep with Nomad releases and are integrated into the make release toolchain.

Troubleshooting

The UI is running, but none of the API requests are working

By default (according to the .embercli file) a proxy address of http://localhost:4646 is used. If you are running Nomad at a different address, you will need to override this setting when running ember serve: ember serve --proxy http://newlocation:1111.

Nomad is running in Vagrant, but I can't access the API from my host machine

Nomad binds to 127.0.0.1:4646 by default, which is the loopback address. Try running nomad bound to 0.0.0.0: bin/nomad -bind 0.0.0.0.

Ports also need to be forwarded in the Vagrantfile. 4646 is already forwarded, but if a port other than the default is being used, that port needs to be added to the Vagrantfile and vagrant reload needs to be run.