etc, etc, and just tagged my commits with the new version number.
Now I use Toran Proxy because you can set it up with a cron and it will mirror all your git repos and also packagist too if you want at whatever rate you decide to set the cron job for. So you really only need to push new versions to your private repos and Toran automatically stays in sync.
What I find irritating is that the composer landscape changes, frequently. I go to back to an old client site and run composer update, and it barfs cryptically about composer/installers not being up to date, which they clearly are.
Quite surprised to find no mention of SatisPress in this discussion.
It’s a little rough around the edges but on the whole, a very functional solution to this tricky problem.
It runs on top of WordPress, allowing you to install premium / 3rd party plugins and setup their licenses / update mechanisms etc
The only issues we’ve found with using it so far is that the admin gets slow very quickly with that many plugins active, as many of the plugins rely on being active to check for updates etc so we’ve started splitting our plugins across multiple satispress instances (ie 1 repo for gravity forms and all add-ons, one for woo and all our premium extensions, one for general plugins like ACF).
We even use the github updater plugin to pull a bunch of our homemade plugins from git/bitbucket repos into a satispress instance, that way we don’t need a heap of different VCS repositories in our composer.json
We’ve set cron to run updates automatically, but some plugins hook in weird places that depend on having the actual wp-admin loaded, so we still try to log in and manually update the sites as needed or at least once a week
Hope this helps, it’s been the best solution my company has found so far
Hi,
I’m trying to get my trellis setup working with some premium plugins for wordpress. That’s really tricky. I tried to add them to the must-use-plugins (and unignored them manually in the bedrock repo). The plugin are listed in the wp backend with an appended * (what ever that means), but they aren’t really active… wp plugin list doesn’t show them.
You should be able to add them to the regular plugins directory; they don’t need to be “mu-plugins”. Try this first and then activate them in WordPress once they’re deployed.