Composer Repository

Troy Server provides a native Composer 2 repository. Every plugin and package you publish becomes available via composer require — alongside WordPress.org plugins from WP Packages or WPackagist.

Prerequisites

Add Your Repository

Add your Troy Server as a Composer repository in your project's composer.json under the repositories key:

{
  "repositories": [
    {
      "type": "composer",
      "url": "https://repo.example.org/composer/get"
    }
  ]
}

This repository entry sits alongside any other Composer repositories in your project.

Install Troy Server via Composer

composer config repositories.deploytroy composer https://repo.deploytroy.org/composer/get
composer require deploytroy-package/troy-server-installer

Composer fetches the metapackage and automatically pulls in Troy Client as a dependency.

Example With Multiple Repositories

A working example installing The SEO Framework via its Troy Server alongside Gentime via WP Packages:

{
  "repositories": [
    {
      "name": "wp-packages",
      "type": "composer",
      "url": "https://repo.wp-packages.org",
      "only": ["wp-plugin/*", "wp-theme/*"]
    },
    {
      "type": "composer",
      "url": "https://repo.theseoframework.com/composer/get"
    }
  ],
  "require": {
    "theseoframework-package/tsf-em-installer": "*",
    "wp-plugin/gentime": "^2.0"
  }
}

Plugins vs Packages

Troy Server provides these Composer package types, where {vendor} is your repository's vendor slug:

Bedrock Setup

Bedrock already manages WordPress plugins via Composer. Adding a Troy repository takes one entry.

{
  "repositories": [
    {
      "name": "wp-packages",
      "type": "composer",
      "url": "https://repo.wp-packages.org",
      "only": ["wp-plugin/*", "wp-theme/*"]
    },
    {
      "type": "composer",
      "url": "https://repo.example.org/composer/get"
    }
  ]
}

composer require deploytroy-package/troy-server-installer

Vendor Slug

Every Troy Server has a vendor slug — a short prefix that identifies your repository in Composer package names. It appears in:

• Plugin names: {vendor}-plugin/my-plugin.
• Package names: {vendor}-package/my-package.

Set the vendor slug in Settings → Troy Server → Composer. Troy pre-fills it from your site name at install time.

How Composer Resolution Works

When Composer encounters your Troy repository, it fetches packages.json at the repository URL. That response contains no package data — only instructions for fetching individual packages:

{
  "packages": {},
  "metadata-url": "/composer/get/%package%.json",
  "available-package-patterns": [
    "deploytroy-plugin/*",
    "deploytroy-package/*"
  ]
}

You can inspect live responses from Deploy Troy's repository:

• packages.json — the root response above.
• deploytroy-plugin/troy-server.json — individual plugin metadata.
• deploytroy-package/troy-server-installer.json — individual package metadata (metapackage).

Troubleshooting

Composer Reports "Package Not Found"

• Verify that the vendor slug in your composer require command matches the vendor slug configured in Troy Server.
• Verify that the plugin or package is published and has at least one released version.
• Verify that the repository URL in your composer.json is correct — no trailing slash, and the path ends with /composer/get.

HTTPS Errors

Troy Server requires HTTPS. If your server uses a self-signed certificate, Composer will reject it. Use a valid certificate (Let's Encrypt is free) or pass --no-verify-ssl during development only.

Stale Results After Publishing

Composer caches repository metadata. Run composer clear-cache and then composer update to force a fresh fetch.

Namespace Collisions

Troy's available-package-patterns tells Composer which namespaces your repository provides. Composer skips repositories that don't match the package it's resolving, so collisions are unlikely in practice.

If a misconfigured third-party repository still interferes, you can add an only filter to each repository entry in your composer.json to explicitly scope which packages it may resolve. See the Composer documentation on repository priorities for details.