Appearance
Composer
Recipe for managing packages from custom Composer repositories with authentication.
Configuration
Repository URL
- Label: Repository URL
- Required: Yes
- Type: URL
- Placeholder:
https://example.com/packages.json - Helper Text: The URL of the Composer repository. It should be a URL that returns a valid composer.json file.
Package
- Label: Package
- Required: Yes
- Type: Select (searchable)
- Note: Dynamically populated based on the repository URL. Shows all available packages from the repository.
Basic Auth Username
- Required: Yes
- Type: Secret
- Note: Used for HTTP Basic Authentication when accessing the repository.
Basic Auth Password
- Required: Yes
- Type: Secret
- Note: Used for HTTP Basic Authentication when accessing the repository.
Features
- Automatically fetches available packages from the repository
- Supports HTTP Basic Authentication for private repositories
- Compatible with standard Composer repository format
How to Obtain License Information
You'll need:
- The URL to your Composer repository's
packages.jsonfile - HTTP Basic Authentication credentials (username and password) if your repository is private
- The package name you want to manage
Common use cases:
- Private Satis repositories
- Commercial plugin repositories that use Composer
- Custom package repositories
Notes
- The repository URL will automatically append
/packages.jsonif not present - Uses standard Composer package format
- Caches repository responses to improve performance
- Downloads packages using the
dist.urlfrom the package metadata - User agent:
Composer/2.8.0