Deploy

Rodan Client uses Gulp to manage deployment, both for development and production. How Rodan Client can be deployed is defined in gulpfile.js. Just like jspm, Gulp was installed as a development dependency, so its binary is located in `node_modules/.bin’.

The gulpfile.js defines three entry points to deploy Rodan Client. Choose the one best suited for your needs.

Development

user@computer:~/rodan-client$ ./node_modules/.bin/gulp

or

user@computer:~/rodan-client$ ./node_modules/.bin/gulp develop

The develop task is the default task in gulpfile.js. This type of deployment is meant for debugging and development. It will: * link JavaScript source files, resources, styles, and configuration to rodan-client/web * run JSHint on the JavaScript source * start a small web server that hosts the application on your machine’s IP at port 9001.

Production

user@computer:~/rodan-client$ ./node_modules/.bin/gulp dist

The dist task will create a single JavaScript bundle file for the application and copy only those files required for deployment. This type of deployment is meant for production. All files required are stored in rodan-client/dist. You will have to setup a web server to statically serve the contents of this directory.

If you wish to test the bundle, you can run:

user@computer:~/rodan-client$ ./node_modules/.bin/gulp dist:server

This does the same as the simple dist task, but also runs a small development server just as the develop task does on port 9001.