Skip to content

Commit

Permalink
fixup! docs: reorg deployment guide with serve-from-disk info from CL…
Browse files Browse the repository at this point in the history
…I story
  • Loading branch information
jbogarthyde committed Jan 18, 2019
1 parent 13c3ef6 commit 4ed72c5
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions aio/content/guide/deployment.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,6 @@ During development, you typically use the `ng serve` command to build, watch, an
When you are ready to deploy, however, you must use the `ng build` command to build the app and deploy the build artifacts elsewhere.

Both `ng build` and `ng serve` clear the output folder before they build the project, but only the `ng build` command writes the generated build artifacts to the output folder.
Serving the contents of your output folder from a local web server can give you a better idea of how your application will behave when it is deployed to a remote server.

<div class="alert is-helpful">

Expand All @@ -25,7 +24,7 @@ To output to a different folder, change the `outputPath` in `angular.json`.

</div>

When you have deployed your app, however, you might still want to serve the app so that you can continue to see changes that you make in it.
Serving the contents of your output folder from a local web server can give you a better idea of how your application will behave when it is deployed to a remote server.
You will need two terminals to get the live-reload experience.

* On the first terminal, run the [`ng build` command](cli/build) in *watch* mode to compile the application to the `dist` folder.
Expand Down

0 comments on commit 4ed72c5

Please sign in to comment.