liveBook · Manning

Deployment

As explained in Enterprise RAG

Deployment is the process of releasing a software system or change into an environment where it can operate for users.

Deployment releases a software system from a local experiment into a reachable, repeatable production service. A chatbot that once ran as one process with local storage must withstand bursts, replacement instances, secrets management, and real users. section 5.0

A production-ready deployment keeps service instances stateless, moves configuration into environment variables, packages the application in a Docker image, and runs it on a managed container host. The image should boot consistently on a developer laptop, Azure App Service, or another supported host. section 5.0

A repeatable deployment workflow typically includes:

  • Package the application and its dependencies into a self-contained Docker image. section 5.0
  • Store the image in a registry so the host pulls an immutable artifact rather than a developer's local state. section 5.2
  • Keep credentials in Azure configuration and GitHub encrypted secrets instead of embedding them in the image or source tree. section 5.2 section 5.2.4
  • Use GitHub Actions to build, test, and deploy after commits, blocking releases when tests fail. section 5.2.4 section 5.3
  • Validate the public endpoint, inspect live logs, and load-test with Locust before scaling resources or replicas. section 5.0 section 5.3

Verifying a deployed WebSocket service

Copy the Azure App Service domain into a browser harness, change the connection to wss://, submit a prompt, and inspect Log stream for “Listening on port 8000.” A streamed response confirms that external traffic reaches the packaged Python process. section 5.3

Figure 5.1 This flowchart shows the key stages of this chapter. We will start by packaging our app as a container, then deploy it to Azure’s app service, then test it remotely. Finally, we will perform load testing using logging and simulated users with Locust.

Use the deployment flow to navigate from container packaging through Azure hosting, remote testing, logging, and Locust-based load testing. section 5.0

How Enterprise RAG covers it

How deep it goes
Explains packaging, secrets, CI testing, endpoint validation, logging, and load testing, stopping short of detailed scaling implementation.
Examples
Uses Docker images, Azure Web App domains, GitHub workflow tests, WebSocket smoke tests, Log stream output, and Locust traffic.
What it assumes
Assumes a working chatbot, Docker image, Azure Web App, GitHub repository, container registry, and configured service credentials.
What you can do after
Operate/configure an Azure-hosted container deployment with automated releases, endpoint checks, logs, and synthetic load tests.
How it connects
Connects containers, statelessness, environment variables, GitHub Actions, Azure App Service, registries, WebSockets, logging, and load testing.

Also explained in

Compare how 29 books explain deployment →

Related concepts

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