-
-
Notifications
You must be signed in to change notification settings - Fork 751
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1259 from StackStorm/0.8.3
0.8.3
- Loading branch information
Showing
25 changed files
with
277 additions
and
182 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,7 +8,6 @@ Contents: | |
|
||
overview | ||
install/index | ||
webui | ||
video | ||
start | ||
packs | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,80 @@ | ||
Web UI | ||
====== | ||
|
||
st2web is an Angular-based web application. It allows you to control the whole process of execution, from running an action to seeing the results of the execution. It also helps you to explore workflow executions up to the results of individual tasks. All in real time. | ||
|
||
Express installation | ||
-------------------- | ||
|
||
Production version of st2web is pre-installed on st2express and any other st2_deploy installation. You can access the UI by accessing ``/webui`` endpoint of st2api server. For vagrant deployment of st2express, it would be http://172.168.90.50:9101/webui. | ||
|
||
It can also be installed by extracting the latest tar-ball from :ops_latest:`webui` into ``/opt/stackstorm/static/webui``. | ||
|
||
This type of installation has no additional requirements. | ||
|
||
Production | ||
---------- | ||
|
||
st2web is a pure html5 application and consist only of js scripts, html templates, css styles and a number of static files including custom fonts and svg images. For application to work correctly, all this files should be served to the browser. In most cases, the particular web server doesn't matter. It might be apache or nginx, pecan or node.js, files could be served from local server or uploaded to S3, Heroku or even Github Pages. | ||
|
||
The application itself is running within the browser so API endpoint should be accessible to the user itself, not the static server. | ||
|
||
To generate the latest production version of st2web from the source code, run ``gulp production`` inside st2web directory. Then, copy ``build/`` directory to the server public folder or upload it to the cloud. For more information on working with gulp, please see :github_st2web:`README.md`. | ||
|
||
Development | ||
----------- | ||
|
||
With production version it is almost impossible to make any changes in code, besides configuration. In case any changes are needed, development version has to be installed. For information on how to install development version, please refer to :github_st2web:`README.md`. | ||
|
||
Configuration | ||
------------- | ||
|
||
For UI to work properly, both client and server side should be configured accordingly. | ||
|
||
On a UI side, there is a file ``config.js`` in a root of the project which contains the list of servers this UI can connect to. The file consists of an array of objects, each have a ``name``, ``url`` and ``auth`` properties. | ||
|
||
:: | ||
|
||
hosts: [{ | ||
name: 'Express Deployment', | ||
url: 'http://172.168.90.50:9101', | ||
auth: true | ||
},{ | ||
name: 'Development Environment', | ||
url: 'http://172.168.50.50:9101' | ||
}] | ||
|
||
|
||
Multiple servers could be configured for user to pick from. To disconnect from the current server and return to login screen, pick 'Disconnect' from the drop down at the top right corner of the UI. | ||
|
||
On an ST2 side, `CORS <https://en.wikipedia.org/wiki/Cross-origin_resource_sharing>`__ should also be properly configured. In st2.conf, ``allow_origin`` property of the [api] section should contain the Origin header browser sends with every request. For example, if you have deployed UI on its own server and accessing it using url `http://webui.example.com:8000`, your config should look like that: | ||
|
||
:: | ||
|
||
[api] | ||
# Host and port to bind the API server. | ||
host = 0.0.0.0 | ||
port = 9101 | ||
logging = st2api/conf/logging.conf | ||
# List of allowed origins for CORS, use when deploying st2web client | ||
# The URL must match the one the browser uses to access the st2web | ||
allow_origin = http://webui.example.com:8000 | ||
|
||
Origin consists of scheme, hostname and port (if it isn't 80). Path (including tailing slash) should be omitted. | ||
|
||
Please note that some of the origins is already included by default and do not require additional configuration: | ||
|
||
* http://localhost:3000 - development version of `gulp` running locally | ||
* http://localhost:9101,http://127.0.0.1:9101 - st2api pecan deployment (st2_deploy default) | ||
* `api_url` from [auth] section of st2.conf | ||
|
||
Also, please note that although this is not recommended and will undermine your security, you can allow every web UI deployment to connect to your server by setting ``allow_origin = *``. | ||
|
||
Authentication | ||
-------------- | ||
|
||
To configure st2web to support authentication, edit ``config.js`` and add ``auth:true`` to every server that supports authentication. To enable authentication on a server side, please refer to :doc:`/install/deploy`. | ||
|
||
For now, UI assumes st2auth is running on the same server with st2api on the port 9100. This is known issue and will be fixed in the next release. | ||
|
||
It is highly recommended to only use authentication alongside with SSL encryption (for st2web, st2api and st2auth) to mitigate possible MITM attacks and avoid sending passwords and auth tokens in plain text. |
Oops, something went wrong.