awx/awx/ui

Ansible Tower UI

Requirements

Node / NPM

Tower currently requires the 6.x LTS version of Node and NPM.

macOS installer: https://nodejs.org/dist/latest-v6.x/node-v6.9.4.pkg

RHEL / CentOS / Fedora:

$ curl --silent --location https://rpm.nodesource.com/setup_6.x | bash -
$ yum install nodejs

Other Dependencies

On macOS, install the Command Line Tools:

$ xcode-select --install

RHEL / CentOS / Fedora:

$ yum install bzip2 gcc-c++ git make

Usage

Starting the UI

First, the Tower API will need to be running. See CONTRIBUTING.md.

When using Docker for Mac or native Docker on Linux:

$ make ui-docker

When using Docker Machine:

$ DOCKER_MACHINE_NAME=default make ui-docker-machine

Running Tests

Run unit tests locally, poll for changes to both source and test files, launch tests in supported browser engines:

$ make ui-test

Run unit tests in a CI environment (Jenkins)

$ make ui-test-ci

Adding new dependencies

Add / update a bundled vendor dependency

1. npm install --prefix awx/ui --save some-frontend-package@1.2.3
2. Add 'some-package' to var vendorFiles in ./grunt-tasks/webpack.js
3. npm --prefix awx/ui shrinkwrap to freeze current dependency resolution

Add / update a dependecy in the build/test pipeline

1. npm install --prefix awx/ui --save-dev some-toolchain-package@1.2.3
2. npm --prefix awx/ui shrinkwrap to freeze current dependency resolution

Polyfills, shims, patches

The Webpack pipeline will prefer module patterns in this order: CommonJS, AMD, UMD. For a comparison of supported patterns, refer to [https://webpack.github.io/docs/comparison.html](Webpack's docs).

Some javascript libraries do not export their contents as a module, or depend on other third-party components. If the library maintainer does not wrap their lib in a factory that provides a CommonJS or AMD module, you will need to provide dependencies with a shim.

1. Shim implicit dependencies using Webpack's ProvidePlugin. Example:

// Tower source code depends on the lodash library being available as _
_.uniq([1,2,3,1]) // will throw error undefined

// webpack.config.js
plugins: [
  new webpack.ProvidePlugin({
      '_': 'lodash',
  })
]

// the following requirement is inserted by webpack at build time
var _ = require('lodash');
_.uniq([1,2,3,1])

2. Use imports-loader to inject requirements into the namespace of vendor code at import time. Use exports-loader to conventionally export vendor code lacking a conventional export pattern.
3. Apply a functional patch. A webpack plugin is the correct choice for a functional patch if your patch needs to access events in a build's lifecycle. A webpack loader is preferable if you need to compile and export a custom pattern of library modules.
4. Submit patches to libraries without modular exports - the internet will thank you

Some javascript libraries might only get one module pattern right.

Environment configuration - used in development / test builds

Build tasks are parameterized with environment variables.

package.json contains default environment configuration. When npm run myScriptName is executed, these variables will be exported to your environment with the prefix npm_package_config_. For example, my_variable will be exported to npm_package_config_my_variable.

Environment variables can accessed in a Javascript via PROCESS.env.

  "config": {
    "django_port": "8013",
    "websocket_port": "8080",
    "django_host": "0.0.0.0"
  }

Example usage in npm run build-docker-machine:

$ docker-machine ssh $DOCKER_MACHINE_NAME -f -N -L ${npm_package_config_websocket_port}:localhost:${npm_package_config_websocket_port}; ip=$(docker-machine ip $DOCKER_MACHINE_NAME); echo npm set ansible-tower:django_host ${ip}; $ grunt dev

Example usage in an npm test script target:

npm_package_config_websocket_port=mock_websocket_port npm_package_config_django_port=mock_api_port npm_package_config_django_host=mock_api_host npm run test:someMockIntegration

You'll usually want to pipe and set vars prior to running a script target:

$ npm set ansible-tower:websocket_host ${mock_host}; npm run script-name

NPM Scripts

Examples:

  {
    "scripts": {
      "pretest": "echo I run immediately before 'npm test' executes",
      "posttest": "echo I run immediately after 'npm test' exits",
      "test": "karma start karma.conf.js"
    }
  }

npm test is an alias for npm run test. Refer to script field docs for a list of other runtime events.