The core way to adjust Composer behavior is through the config part of composer.json, which allows users to control installation paths, warehouse settings and platform constraints. 1. The config block is located in composer.json and is used to change the default configuration, such as vendor-dir, bin-dir, and cache-dir. 2. The platform option can simulate different PHP versions or extensions to ensure that dependency resolution is consistent with the target environment. 3. Repositories and cache-files-ttl settings support custom private repositories and cache policies, and use-include-path can be used for non-standard automatic loading. 4. Secure-http and git-version are used to force HTTPS and specify Git versions to ensure security and compatibility. All available configuration items can be viewed through the composer config --list command.

When you need to adjust Composer's behavior, the config section in composer.json is where most of those tweaks happen. It's a flexible way to control things like package installation paths, repository settings, and even platform-specific constraints.

1. Understanding the basic structure

The config block sits directly under your main composer.json file. You don't need to include every possible option — only the ones you want to change from their defaults.

A simple example looks like this:

 {
    "config": {
        "vendor-dir": "custom_vendor_path"
    }
}

This changes where Composer installs dependencies. By default, it uses vendor/ , but here we've changed it to custom_vendor_path/ .

Some common config options:

• vendor-dir : Changes where packages are installed.
• bin-dir : Sets the directory for binaries.
• cache-dir : Specifies where Composer caches files.

These can help if you're working with custom project structures or limited filesystem access.

2. Setting platform compatibility

Sometimes you need to simulate different PHP versions or extensions, especially when deploying to environments that different from your development setup.

You can do this using platform inside config :

 {
    "config": {
        "platform": {
            "php": "8.1.0",
            "ext-something": "1.0"
        }
    }
}

Composer will then resolve dependencies as if you were running on PHP 8.1.0, even if your local version is higher. This helps avoid accidental dependency mismatches later on.

This is useful when:

• You're developing on a newer PHP version than your production server.
• You want to test how your app behaves on an older version without switching locally.

3. Customizing repositories and caching

If you use private packages or mirrors, you can set them up in the repositories section. But did you know you can also influence how Composer caches these?

For example:

 {
    "repositories": [
        {
            "type": "composer",
            "url": "https://your-private-repo.example.com"
        }
    ],
    "config": {
        "cache-files-ttl": 86400,
        "use-include-path": true
    }
}

Here, cache-files-ttl controls how long Composer considers cached package data valid (in seconds). The default is two weeks, but you might lower that during active development or raise it on stable projects.

Also, use-include-path lets you autoload from non-standard locations — handy if you're dealing with legacy systems or unusual settings.

4. Handling git versions and secure HTTP

Composer works well with Git-based repositories, but sometimes you need to lock down specific behaviors. For example, if you're pulling from VCS repos and want to enforce HTTPS-only connections:

 {
    "config": {
        "secure-http": true,
        "git-version": "2.9.0"
    }
}

• secure-http : Stops Composer from using insecure HTTP for downloading packages.
• git-version : Forces Composer to use a specific Git version (helpful in shared hosting environments).

If you're ever unsure about what config options exist, run composer config --list --global and composer config --list to see global and local settings respectively.

Basically that's it.

The above is the detailed content of How do I configure Composer settings using the config section?. For more information, please follow other related articles on the PHP Chinese website!