defang compose
Work with local Compose files
Synopsis
Define and deploy multi-container applications with Defang. Most compose commands require a "compose.yaml" file. The simplest "compose.yaml" file with a single service is:
services: app: # the name of the service build: . # the folder with the Dockerfile and app sources (. means current folder) ports:
- 80 # the port the service listens on for HTTP requests
Aliases: stack
Options
-h, --help help for compose
--pulumi-backend string specify an alternate Pulumi backend URL or "pulumi-cloud"
Options inherited from parent commands
--color color-mode colorize output; one of [never auto always] (default auto)
-C, --cwd string change directory before running the command
--debug debug logging for troubleshooting the CLI
--dry-run dry run (don't actually change anything)
-f, --file stringArray compose file path(s)
-T, --non-interactive disable interactive prompts / no TTY (default true)
--org string override GitHub organization name (tenant)
-p, --project-name string project name
-P, --provider provider bring-your-own-cloud provider; one of [defang aws digitalocean gcp] (default auto)
-v, --verbose verbose logging
SEE ALSO
- defang - Defang CLI is used to take your app from Docker Compose to a secure and scalable deployment on your favorite cloud in minutes.
- defang compose config - Reads a Compose file and shows the generated config
- defang compose down - Reads a Compose file and deprovisions its services
- defang compose logs - Show logs from one or more services
- defang compose ps - Get list of services in the project
- defang compose up - Reads a Compose file and deploy a new project or update an existing project