COMPOSER-CLI(1)

πŸ’… COMPOSER-CLI(1) β€” the composer-cli manual, but make it cute

okay bestie, sit down, hydrate, because we're diving into composer-cli-compose and honestly? it's giving management. πŸ‘‘


✨ NAME ✨

composer-cli-compose β€” manage composes πŸŽ€


🌸 SYNOPSIS 🌸

composer-cli compose ... [flags]

πŸ¦‹ DESCRIPTION πŸ¦‹

So like, this is the vibe: you're managing composes on the server. That's the whole thing. That's the job. πŸ’–

And here's the lil spicy detail β€” the start and start-ostree commands can optionally upload the results for you. no cap. And if you wanna see the full upload profile reference, it lives right here:

https://osbuild.org/docs/user-guide/uploading-cloud-images/

go look at it, it's iconic, iykyk. 🫢


πŸ‘‘ OPTIONS πŸ‘‘

  • -h, --help[=false] β€” help for compose. the classic. the goat. literally just tells you about compose. πŸ’…

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

these bad boys come down from the parent command, so they're not even yours, you're just borrowing them and honestly? they ate.

  • -a, --api=1 β€” which WELDR Server API Version to use. defaults to 1. ⭐
  • --cloudsocket="/run/cloudapi/api.socket" β€” the path to the cloudapi server's socket file. that's the default path, fr fr. πŸ”Œ
  • -j, --json[=false] β€” output the raw JSON response instead of the normal output. for the girlies who like their data unprocessed. πŸ’€
  • --log="" β€” path to an optional logfile. optional! so chill. default is empty. πŸ“
  • -s, --socket="/run/weldr/api.socket" β€” path to the WELDR API server's socket file. also has a default. 🧚
  • --test=0 β€” pass test mode to compose. 1=Mock compose with fail. 2=Mock compose with finished. yes those are the exact values, don't @ me. πŸ™ˆ
  • --timeout=240 β€” timeout to use for server communication. set it to 0 for no timeout (main character energy tbh). ⏳
  • --weldr-only[=false] β€” only use the WELDR API; skip using the newer Cloud API. old school, but valid. πŸ’œ

πŸ“ EXAMPLE πŸ“

here's where it gets fun, bestie β€” TOML profiles. three of them. all for uploading, all gorgeous.

🌸 TOML profile for uploading to AWS

provider = "aws"

[settings]
accessKeyID = "AWS_ACCESS_KEY_ID"
secretAccessKey = "AWS_SECRET_ACCESS_KEY"
bucket = "AWS_BUCKET"
region = "AWS_REGION"
key = "OBJECT_KEY"

🌸 TOML profile for uploading to GCP

provider = "gcp"

[settings]
bucket = "GCP_BUCKET"
region = "GCP_STORAGE_REGION"
object = "OBJECT_KEY"
credentials = "GCP_CREDENTIALS"

🌸 TOML profile for uploading to Azure

provider = "azure"

[settings]
storageAccount = "your storage account name"
storageAccessKey = "storage access key you copied in the Azure portal"
container = "your storage container name"
ngl the Azure one really said "copy it from the portal yourself" and i respect the honesty. πŸ’…

πŸ”₯ SEE ALSO πŸ”₯

the whole friend group, periodt:


πŸ’œ HISTORY πŸ’œ

  • 28-Apr-2026 β€” auto generated by spf13/cobra. the robots did this one, not me. πŸ€–βœ¨

and that's the whole page bestie!! this one's from the composer-cli manual, dated Apr 2026 β€” go forth and manage your composes, you absolute icon. πŸ’–πŸŽ€πŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from