Laravel 6 VS WordPress Packagist

Laravel Tinker allows you to interact through a command line with any project that uses the Laravel framework. It allows users to access all the events and objects. Tinker is an optional add on, so we should manually install with the Laravel versions after 5.4.

CMF is good, but I think these two things are not the same. What I do is just a lightweight thing that only requires your application to integrate Tinker/PsySH, and whatever your Laravel or PHP version is, so I just made something that you should write PHP code in the terminal and now can be written in the editor or GUI.

This incredible app was developed with the Laravel Developer in mind, to simplify the work that we all already do: Use the tinker tool. 🤔

If I have to use WordPress for something, I'll build it as a standard PHP project, requiring WordPress and any themes/plugins as a Composer dependencies from johnpbloch/wordpress and WordPress Packagist (more info here). If I need to do any significant templating, I like to use Timber.

Use it together with https://wpackagist.org/ and you can update all plugins/themes by latest or by version number.

Another option you can look at is Bedrock by Roots - that is sets WP as an app with composer already set up. It allows you to install WP plugins (from official WP repo) via composer (WP Packagist). The structure is set up to allow for git workflow. Also helpful if you want to make use of a bunch of composer packages on your site.

https://wpackagist.org/ in the example you see "repositories", now in that array you can put your plugins github-link and set the other settings. with composer install you install them and with composer update you update them

Side question: I know that the WordPress ecosystem has been moving toward better support for Composer – e.g., with WPackagist. But wouldn't plugins installed/updated via Composer run into the same issue?