How to use Docker Compose Profiles to manage the startup of optional services in the infrastructure?

Profiles in Docker Compose provide a convenient mechanism for conditionally starting containers depending on the developer's current tasks or environment. By default, all services without an explicit profile specification always start, but adding a special directive allows grouping services into logical groups.

To use this feature in the configuration file, a section with the profile name is added to each service that should only start on demand. These can be monitoring tools, databases for local testing, or auxiliary administration utilities that are not needed for the daily work of the main application.

Running a stack with specific profiles is done by passing the corresponding argument on the command line. You can activate either one specific profile or several simultaneously by listing them separated by spaces or using environment variables, which is especially convenient when configuring build automation scripts.

This approach greatly simplifies the organization of the workflow, as the developer no longer needs to create separate configuration files for each case or manually comment out unnecessary code blocks. The entire infrastructure is described in a single place, and its composition is flexibly adapted to specific needs with a single command.