First of all, I would like to take this opportunity and wish composer a happy birthday and many more years to come. It’s been five years, and the world of PHP has changed so drastically that not many people remember how it used to be before.
I would have completely missed the birthday if it wasn’t for all the Google searching I did while working on a weird problem. But before I get to the problem, let me set the scene.
The big part of composer success is Packagist.org – the repository of almost 100,000 packages (93,572, according to statistics, as of this writing, to be precise), which help one to solve pretty much any problem that PHP can be used for.
As good as the Packagist is, there is often a need for a repository or a package elsewhere. Whether it’s a commercial library, or sensitive corporate code, having an ability to store it outside of public eye and handle with the same ease and the same tool as the rest of the dependencies is a very welcome feature.
Now we are getting closer to what actually happened. A while back, I’ve setup deployment and development process for WordPress-based projects. WordPress doesn’t support composer natively, but there are ways to make it work. Huge thanks here goes to Roots.
So. The composer.json file was filled with additional repositories and requirements which told composer where from to fetch things, and where to install them. Here’s an example:
This got especially useful, when we need to work with commercial plugins, which we couldn’t push to our public repositories, and which we didn’t want to re-distribute with every project.
So far so good. Fast-forward to a few month ago. We are setting up similar development and deployment process, but now for CakePHP-based projects. Things are much easier, since CakePHP 3 natively supports composer for the application itself and for its plugins.
But we still have the need for private repositories here and there, so we follow the same setup as we did for WordPress. This week, we had an unexpected roadblock, which wasn’t making much sense to me. When trying to pull a CakePHP plugin from a private repository, we’d get a nasty exception like this:
$ composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
- Installing qobo/cakephp-test-foo (1.0.1)
Loading from cache
Unable to get primary namespace for package qobo/cakephp-test-foo.
Ensure you have added proper 'autoload' section to your plugin's config as stated in README on https://github.com/cakephp/plugin-installer
This was confusing. First of all, I’ve never seen this error before. Secondly, I’ve read the README and had the autoloader section in the composer.json as instructed. Thirdly, very similar plugins were working fine.
Long story short, the issue wasn’t related to whether or not the GitHub/BitBucket repository was private or public. It was related to how the repository was configured in the composer.json. Reading and re-reading composer documentation about Repositories finally helped.
You can have a look at our test setup:
CakePHP plugin installer requires the autoload section in composer.json. But, when the repository is of type “package“, for some reason, the autoload section is ignored altogether. The RuntimeException “Unable to get primary namespace for package” is thrown by cakephp/plugin-installer (src/Installer/PluginInstaller.php line 274). The problem is not actually in the cakephp/plugin-installer, but somewhere in the composer. Maybe it’s intentional or maybe it’s not. I didn’t have the time to investigate and understand it further.
Switching the repository to type “vcs” fixes the problem. It also simplifies the composer.json file and removes the need for multiple version definitions, as now composer is using BitBucket/GitHub API to fetch available versions.