When you're using an editor/CLI development approach (for example, Visual Studio Code plus Docker CLI on macOS or Windows), you need to know every step, generally in more detail than if you're using Visual Studio. In this section, this whole process is detailed and every major step is explained by focusing on a Visual Studio environment. Step-by-step workflow for developing Docker containerized apps
The development process for Docker apps: 1 - Code your App, 2 - Write Dockerfile/s, 3 - Create images defined at Dockerfile/s, 4 - (optional) Compose services in the docker-compose.yml file, 5 - Run container or docker-compose app, 6 - Test your app or microservices, 7 - Push to repo and repeat.įigure 5-1. The following are the basic steps you usually take when building a Docker application, as illustrated in Figure 5-1. The initial steps to set up the environment aren't included, since those steps are done only once.Īn application is composed of your own services plus additional libraries (dependencies). The inner-loop workflow means it's not considering the broader DevOps workflow, which can include up to production deployment, and just focuses on the development work done on the developer's computer. This section describes the inner-loop development workflow for Docker container-based applications. Workflow for developing Docker container-based applications With this workflow, no matter which language, framework, and platform you choose, you're always developing and testing Docker containers, but doing so locally.Įach container (an instance of a Docker image) includes the following components:Īn operating system selection, for example, a Linux distribution, Windows Nano Server, or Windows Server Core.įiles added during development, for example, source code and application binaries.Ĭonfiguration information, such as environment settings and dependencies. The application development life cycle starts at your computer, as a developer, where you code the application using your preferred language and test it locally.
0 kommentar(er)
