ExternalVendorCode/openmct
1
0
Fork 0
mirror of https://github.com/nasa/openmct.git synced 2025-06-16 14:18:16 +00:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity

Updated tutorial to reference app.js built in web server instead of http-server

Browse Source
This commit is contained in:
Henry
2015-10-15 15:51:54 -07:00
parent 688718cad0
commit 9d17768327
1 changed files with 12 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
docs/src/tutorials/index.md
View File

@ -171,21 +171,23 @@ __bundles.json__
### Run a Web Server ### Run a Web Server
The next step is to run a web server so that you can view the Open MCT Web The next step is to run a web server so that you can view the Open MCT Web
client (including the plugins you add to it) in browser. The HTTP server option client (including the plugins you add to it) in browser. Any web server can
that is recommended here, for simplicity, is http-server, be used for hosting OpenMCTWeb, and a trivial web server is provided in this
[https://www.npmjs.com/package/http-server](). package for the purposes of running the tutorials. The provided web server
should not be used in a production environment
To run the tutorial web server
To run: node app.js
npm install http-server -g
http-server <path to Open MCT Web repository>
### Viewing in Browser ### Viewing in Browser
Once running, you should be able to view Open MCT Web from your browser at Once running, you should be able to view Open MCT Web from your browser at
[http://localhost:8080/](). [Google Chrome](https://www.google.com/chrome/) is [http://localhost:8080/]() (assuming the web server is running on port 8080,
recommended for these tutorials, as Chrome is Open MCT Web’s “test-to” browser. and OpenMCTWeb is installed at the server's root path).
The browser cache can sometimes interfere with development (masking changes by [Google Chrome](https://www.google.com/chrome/) is recommended for these
tutorials, as Chrome is Open MCT Web’s “test-to” browser. The browser cache
can sometimes interfere with development (masking changes by
using older versions of sources); to avoid this, it is easiest to run Chrome using older versions of sources); to avoid this, it is easiest to run Chrome
with Developer Tools expanded, and “Disable cache” selected from the Network with Developer Tools expanded, and “Disable cache” selected from the Network
tab, as shown below. tab, as shown below.