hivepaas compose
Docker Compose files: their services as apps
hivepaas compose [command]
hivepaas compose up
Make a project of a Docker Compose file, its services as apps, or with -p add them to the project's environment -e (production by default, made when missing), as the dashboard's import does. The files it reads are sent from beside it; a variable with no value is asked, or given with --var. The plan is shown first - each service as the app it becomes, then the issues - and made once confirmed: asked at a terminal, --yes elsewhere. The apps are deployed and waited for unless --no-deploy or --no-wait.
hivepaas compose up [flags]
Examples:
hivepaas compose up
hivepaas compose up -f stack/compose.yaml -p shop -e staging --var DB_PASSWORD=$DB_PASSWORD --yes
Flags:
| Flag | Description |
|---|---|
--env-file string | the .env file; the one beside the compose file by default |
-f, --file string | the compose file; compose.yaml and the like here by default |
--name string | a new project's name; the compose file's by default |
--no-deploy | make the apps, and do not deploy them |
--no-wait | do not wait for the deployments |
--profile stringArray | a profile whose services are made too; repeat for more |
--timeout duration | how long to wait for the deployments (default: 30m0s) |
--var stringArray | a variable of the compose file, K=V; repeat for more |
-y, --yes | do not ask: for a script |
The global flags apply to every command.