Packagist VS fig-standards

What will we do next time? Actually, the whole package is ready, and all that's left is to publish it on Packagist.

publishing our work on https://packagist.org/

The latter one is based on nix OS using Symfony flex recipes and PHP packagist composer. The flex devenv should work cross-platform on Linux, Windows, and Mac. "The main difference to other tools like Docker or a VM is that it neither uses containerization nor virtualization techniques. Instead, the services run natively on your machine."

Composer is (still) the defacto standard package manager, with the Packagist repo being the standard place to find and install libraries.

Sorta—it looks like they were most enforced by convention until May 2015, when they finally become enforced [0]. Still, that's a good one that I hadn't thought of, and they at least had the convention in place.

[0] https://github.com/composer/packagist/issues/163#issuecommen...

Scanning your image for vulnerabilities is a critical step before you deploy it to production. You can use Snyk to scan your PHP Docker image and identify and resolve vulnerabilities. The Snyk Vulnerability Database includes records for all popular operating systems and dependencies, including PHP packages published to Packagist.

No. The only linked commercial thing I know - is Nova admin panel interface lib. But you don't have to use it. (Filament or Encore are free and suitable). Modules are free ( packagist.org and gthub.com ) and you should handle them with standard composer package tool. But you need to code. It is not WordPress like CMS

Once you understand the underlying principles of a concept, you're free to find a library via packagist.org to use.

For strings I use Stringy (https://github.com/danielstjules/Stringy) for arrays I built my own Collection library, but pretty sure there are plenty in packagist (https://packagist.org/)

I guess I tried downloading a old version. and have to download a newer version of apiclient I found on https://packagist.org/packages/google/apiclient with monolog/monolog: ^2.9||^3.0. I'll try that in a second, I am away from computer now.

The namespaces and class names must follow this example.

I would familiarize yourself with the following PHP standards: https://www.php-fig.org

The PHP Standard Recommendation, or PSR for short, from the aforementioned PHP-FIG.

That's what happens if you use a PSR-4 autoloader and not utilise PSR-4 in your project structure 👀 So either use PSR-0 or properly use PSR-4.

PHP really "got it's act together" in my view when packagist and composer (which are PHP's equivalent of npm) became mainstream and with the release of the PSR community standards. We were admittedly a little behind the curve with regards to package managers but with standardised formats and not having to copy and paste zip file libraries anymore, PHP received a new lease of life.