Where Is the devspace.yaml?
DevSpace reads devspace.yaml at the project root for deployments, file sync, and dev profiles.
Last updated
DevSpace configures from a YAML file at the project root. The devspace.yaml file names deployments, image builds, and sync paths with profiles per workflow. Hooks run commands around lifecycle events.
Schema versions with the binary, so match the version key to your install. Init scaffolds a starter from existing manifests. Keep the file with the code it deploys for reproducible environments.
Where DevSpace stores this, by platform
[ProjectDir]/devspace.yaml
Deployments, sync paths, and profiles live here. Match the version key to the binary. Hooks run around lifecycle events.
[ProjectDir]/devspace.yaml
Same root file on Mac. File sync keeps containers fresh during dev. Profiles switch clusters per flag.
[ProjectDir]\devspace.yaml
Same file on Windows. Sync performance follows the project root location. Exact schema keys vary by release.
Frequently asked questions
How do I use DevSpace profiles?
Define them in devspace.yaml with per environment overrides. Activate by name flag per command. Keep defaults safe for local development.
Why does DevSpace reject my config?
The version key predates the binary or a field moved. Migrate with the update hints in the error. Pin the binary version in CI.
Notice an outdated path? Let us know.