On this page
Creating Packagist and Repository Packages
This documentation needs work. See "Help improve this page" in the sidebar.
Packagist fields
Name - The label for the packagist. Used only in the UI (e.g. to reference when adding Repositories).
Base path - The filesystem location for packages definition files (i.e. packages.json
and other used to provide packages info). The path must be relative to the filesystem root, e.g. /home/packagistui/backend/packages
. The path should be writable by the backend user.
Base url - The url base relative to the domain name of the Packagist (as in https://example.com/[base-url]/packages.json
). Use slash (/
) for the domain root (as a common case).
Git repositories path - The filesystem location for git repositories. The path must be relative to the filesystem root, e.g. /home/packagistui/backend/repos
. The path should be writable by the backend user.
Archives path - The filesystem location for packages versions archives to be downloaded by Composer when package is added to a project. The path must be relative to the filesystem root, e.g. /home/packagistui/backend/archives
. The path should be writable by the backend user.
Archives base url - The full url that corresponds to the Archives path directory. Is used to prepare each package version archive download url to be included into package definition json.
Repository fields
Name - The label for the repository. Used only in the UI.
Packagist - The user Packagist that the repository belongs to. The Packagist entity should already exist.
Repository url - Git repository url, e.g. https://github.com/guzzle/guzzle.git .
The repository should be accessible by the backend user, i.e. non-public repository may need ssh keys for access.
Directory name - Directory name relative to the Packagist Git repositories path (see Packagist fields section above), e.g. guzzle
.
Vendor name - The vendor name for package.
Project name - The vendor name for package.
Help improve this page
You can:
- Log in, click Edit, and edit this page
- Log in, click Discuss, update the Page status value, and suggest an improvement
- Log in and create a Documentation issue with your suggestion