In this course we explore a few different ways to require a custom or private plugin with Composer. We'll start by using a public repository on Github and then switch to a private repository while still being able to require the plugin using Composer. To make things a bit easier, we'll switch to Packagist and then Private Packagist (for a private plugin). We'll wrap up using Repman, a free private package repository.
I am the creator of CraftQuest, a web developer, and former software team manager. I spend most of my time improving CraftQuest with code and courses. When I'm not in front of the computer, I spend my time with my family, and running on the roads and trails of Austin, TX.
Requiring Custom Plugins with Composer is made up of the following videos:
|1||Introduction to the Course||A short introduction to the course, as introductions should be.||03:00|
|2||Requiring a Plugin in a Public Git Repository||We start simple with a public Git repository hosted on Github.||04:49|
|3||Requiring a Plugin in a Private Git Repository||If our plugin cannot be public, we need to protect it with a private repository but still let Composer have access.||04:55|
|4||Requiring a Public Package using Packagist.org||If a plugin can be public and you don't want to deal with a VCS repository, you can use public Packagist.||09:58|
Andrew and Ryan meet up for one final livestream in 2020. We spin up a sample Docker Craft project and dockerize CraftQuest.
In this course we explore a few different ways to require a custom or private plugin with Composer.
Composer 2 was recently released. Here's a snapshot of what's changed and how to update to the new version.