liveBook · Manning

Deployment

As explained in Modern Angular

Deployment is the process of releasing software to an environment where it can be executed or accessed by users.

Deployment releases an Angular application into an environment where users can access it. For client-side rendering, the build produces bundled JavaScript, HTML, and CSS that a server delivers to browsers. section 9.4.4

A practical client-side deployment flow is:

  • Build the application, producing a dist folder containing the deployable application files. section 9.4.4
  • Copy the generated application folder to a location from which the hosting server can serve its files. section 9.4.4
  • Configure the server to return index.html for unknown routes, allowing Angular to handle direct navigation such as /products. section 9.4.4

HRMS application

An HRMS client-side-rendered application can be built into an hrms folder, copied to a hosting location, and served through index.html with a fallback for application routes. section 9.4.4

How Modern Angular covers it

How deep it goes
Explains build output, file delivery, and SPA fallback configuration, but defers platform-specific deployment procedures.
Examples
Uses the HRMS application, an Angular dist folder, and direct navigation to /products as concrete deployment examples.
What it assumes
Assumes an existing Angular application and basic ability to place files and configure a hosting server.
What you can do after
Apply via Angular CLI by building the application, publishing its output, and configuring route fallbacks.
How it connects
Connects client-side rendering with single-page applications, index.html delivery, and client-side routing.

Also explained in

Compare how 23 books explain deployment →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Modern Angular. The section links point to the parts of the book it draws on.