@tririga/tri-proxy/README.md

A development HTTP proxy for IBM TRIRIGA UX views.

# tri-proxy

A simple development HTTP proxy for IBM TRIRIGA UX views.

`tri-proxy` is a node.js application that serves one or more TRIRIGA UX views from the local file system and proxies all other views files and ajax calls to a TRIRIGA server.

After the tri-proxy is started, it automatically opens the browser.
The tri-proxy watch your view files as you work. Changes you make will cause the browser to do a full-page refresh.

### Installation

    $ npm install @tririga/tri-proxy -g

### Synopsis

	$ tri-proxy -t <tririga_url>

### Options

  * `-t, --target url` The URL of the TRIRIGA server that the proxy can delegate requests to. It must include the context path. 
  * `-p, --port port` The local TCP port to be used by the proxy server. Defaults to 8001.
  * `-v, --views view ...` The name of the view(s) to be served from the local file system. Defaults to the current directory name.   
  * `-d, --dirs directory_path` The directory path(s) that contains the files for the view(s) specified by the -v option. Defaults to the current directory path. For Windows, replace the backslashes with forward slashes.
  * `-b, --browser browser` The browser to open when starting the tri-proxy. Currently available: Chrome, ChromeCanary, Firefox, Opera, Safari , PhantomJS, IE.
  * `--version` print tri-proxy version.
  * `--help` print this message.

### Usage

To proxy a view called my-app, run the following command:

    $ cd my-app/
    $ tri-proxy -t <tririga_url>

To proxy multiple views at the same time, run the following command:

	$ tri-proxy -t <tririga_url> -v <name_of_view_1> <name_of_view_2> -d <diretory_for_view_1> <diretory_for_view_2>

To proxy using a custom port, run the following command:

	$ tri-proxy -t <tririga_url> -p <local_port>