Fix incorrect development server port in documentation
This commit is contained in:
parent
11319080a8
commit
94e826e1e2
|
@ -45,7 +45,7 @@ npm install
|
||||||
npm start
|
npm start
|
||||||
```
|
```
|
||||||
|
|
||||||
Then, browse to http://localhost:8080
|
Then, browse to http://localhost:1337
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
@ -100,7 +100,7 @@ see also [docs/deployment.md](docs/deployment.md)
|
||||||
|
|
||||||
## Android
|
## Android
|
||||||
|
|
||||||
The android implementation is contained in the `android` directory, and can be viewed locally for easy testing and editing by running `ANDROID=1 npm start` and then visiting <http://localhost:8080>. CSS and image files are located in the `android/app/src/main/assets` directory.
|
The android implementation is contained in the `android` directory, and can be viewed locally for easy testing and editing by running `ANDROID=1 npm start` and then visiting <http://localhost:1337>. CSS and image files are located in the `android/app/src/main/assets` directory.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
|
@ -2,7 +2,7 @@ Send has two build configurations, development and production. Both can be run v
|
||||||
|
|
||||||
# Development
|
# Development
|
||||||
|
|
||||||
`npm start` launches a `webpack-dev-server` on port 8080 that compiles the assets and watches files for changes. It also serves the backend API and frontend unit tests via the `server/bin/dev.js` entrypoint. The frontend tests can be run in the browser by navigating to http://localhost:8080/test and will rerun automatically as the watched files are saved with changes.
|
`npm start` launches a `webpack-dev-server` on port 1337 that compiles the assets and watches files for changes. It also serves the backend API and frontend unit tests via the `server/bin/dev.js` entrypoint. The frontend tests can be run in the browser by navigating to http://localhost:8080/test and will rerun automatically as the watched files are saved with changes.
|
||||||
|
|
||||||
# Production
|
# Production
|
||||||
|
|
||||||
|
|
|
@ -24,7 +24,7 @@ module.exports = function(app, devServer) {
|
||||||
.toString()
|
.toString()
|
||||||
.replace(
|
.replace(
|
||||||
'<base href="file:///android_asset/" />',
|
'<base href="file:///android_asset/" />',
|
||||||
'<base href="http://localhost:8080/" />'
|
'<base href="http://localhost:1337/" />'
|
||||||
);
|
);
|
||||||
res.set('Content-Type', 'text/html');
|
res.set('Content-Type', 'text/html');
|
||||||
res.send(index);
|
res.send(index);
|
||||||
|
|
|
@ -6,7 +6,7 @@ To run all the tests use `npm test`. This will run the tests and produce a code
|
||||||
|
|
||||||
Unit tests reside in `test/frontend/tests`.
|
Unit tests reside in `test/frontend/tests`.
|
||||||
|
|
||||||
Frontend tests can be ran in the browser by running `npm start` and then browsing to http://localhost:8080/test. Doing it this way will watch for changes and rerun the suite automatically.
|
Frontend tests can be ran in the browser by running `npm start` and then browsing to http://localhost:1337/test. Doing it this way will watch for changes and rerun the suite automatically.
|
||||||
|
|
||||||
You can also run them in headless Chrome by using `npm run test:frontend`. The results will be printed to the console.
|
You can also run them in headless Chrome by using `npm run test:frontend`. The results will be printed to the console.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue