Composer VS fig-standards

Delving into PHP frameworks like Laravel or Symfony is like building a skyscraper, with Composer acting as your "construction foreman," guiding you step by step to ensure your code is robust and awe-inspiring. This stage involves getting familiar with popular PHP frameworks such as Laravel, Symfony, CodeIgniter, etc., and utilizing the functionalities provided by these frameworks to rapidly develop efficient, maintainable web applications. Tools to consider: Laravel, Composer.

In our example application we will manage dependencies via Composer.

Our project template is equipped with Composer and an autoload class pre-installed. This inclusion in the repository streamlines the setup process, particularly for this access-token course. Composer, a dependency manager for PHP, simplifies the integration of external libraries and ensures efficient autoloading of classes. It plays a pivotal role in managing project dependencies, enabling developers to focus more on implementation rather than manual library management. If you're unfamiliar with Composer or need guidance on its installation, refer to the following link for detailed instructions: [https://getcomposer.org/] and this article for more details on the setup of the packages in this project.

On you Jenkins server, install PHP, its dependencies and Composer tool (Feel free to do this manually at first, then update your Ansible accordingly later)

Composer

Composer for installing the PHP package: https://getcomposer.org/

Visit https://getcomposer.org/ and click on the DOWNLOAD button.

Composer bisect command #11119

Composer is a PHP package manager and it will allow us to use many out-of-the-box packages and features such as HTTP requests, logging, and templates and database management. I use it to develop large, complex applications.

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.