The Craft Cloud Config File

Craft Cloud looks for a craft-cloud.yaml file in the root of the connected repository.

This file has a specific syntax (YAML) and schema that determines a few things about how your project is built, deployed, and served. If there are problems with your config file, the deployment will fail with an error describing the issue.

When you run php craft setup/cloud to install the Cloud extension, it will offer to generate a config file for you, then walk you through setting PHP and Node versions based on your project’s state.

Config Schema #

Your craft-cloud.yaml must contain at least a php-version key:

# Versions must include major + minor, but no patch.
php-version: "8.1"

composer.json’s config.platform is only used to determine the default value that the setup wizard presents.

Advanced Options #

These settings are optional, and should only be used when your project is incompatible with the platform defaults.

# Choose a major version of Node to use in your build step. Minor versions are not allowed.
node-version: "18"

# Directory NPM commands will be run in.
node-path: buildchain

# Key/name of the `script` in package.json run at build time.
npm-script: build

# The directory uploaded to our CDN at the end of the build step.
artifact-path: cms/web

# The directory where your PHP application lives.
app-path: cms

# Public directory, containing `index.php`.
webroot: web

Expanding on the above:

  • node-version — When declared, determines the Node version used in your build step. (Default: None—if you wish to run a Node build step, you must specify a version!)
  • node-path — This directory must contain package.json and package-lock.json. Your NPM script will be run here. (Default: '')
  • npm-script — A single script name. Arbitrary Bash (including other npx commands) is not allowed. (Default: build)
  • artifact-path — Anything emitted from your build step must be in this directory, or it will not be uploaded to the CDN or available to your running app, in any way. (Default: Inherits the value of webroot)
  • app-pathcomposer.json and composer.lock must be located here. Cloud will run composer install in this directory. (Default: '')
  • webroot — If your project uses a different directory for the public web root, you should specify it here. This is relative to app-path. (Default: web)

For the latest information on supported PHP and Node versions, see our Cloud Services and Compatibility article.

Directory Structure #

Multiple settings influence how Cloud locates key files in your project. The defaults agree with our official starter project.

If you have moved your composer.json or package.json into subdirectories, you will need to specify an app-path or node-path, respectively. Similarly, changing your web root will require setting a webroot value, unless it remains below app-path, in a directory named web.

Changing Settings #

You can update craft-cloud.yaml any time. The settings will be validated and used during the next deployment. If you want to test a setting, commit the changes to a branch, and deploy it to another environment!

If you encounter an error at build time, check out our Troubleshooting guide.

Headless and Decoupled Front-Ends #

If your front-end runs elsewhere (and Craft is deployed solely as a back-end or API), you may not need to run any build process on Cloud. Instead of blocking your deploys running the default build script, consider adding a noop script to your package.json

  // ...
  "scripts": {
    "build": "webpack --production",
    "noop": "exit 0"

…and updating craft-cloud.yaml, appropriately:

# ...
npm-script: 'noop'

Applies to Craft Cloud.