


5 Composer tips that PHPer needs to know, phpercomposer_PHP tutorial
5 Composer tips that PHPer needs to know, phpercomposer
Composer is a new generation of PHP dependency management tool. For its introduction and basic usage, you can read this article "Installation and Use of PHP Dependency Management Tool Composer". This article introduces five tips for using Composer, hoping to bring convenience to your PHP development.
1. Only update a single library
You only want to update a specific library and don’t want to update all its dependencies. It’s very simple:
composer update foo/bar
In addition, this trick can also be used to solve the "warning message problem". You must have seen warning messages like this:
Warning: The lock file is not up to date with the latest changes in composer.json, you may be getting outdated dependencies, run update to update them.
Damn, what went wrong? Don't panic! If you edit composer.json, you should see something like this. For example, if you add or update details such as a library description, author, more parameters, or even just a space, it will change the md5sum of the file. Composer will then warn you that the hash value is different from the one recorded in composer.lock.
So what should we do? The update command can update the lock file, but if it only adds some descriptions, it should not update any libraries. In this case, just update nothing:
$ composer update nothing Loading composer repositories with package information Updating dependencies Nothing to install or update Writing lock file Generating autoload files
This way, Composer will not update the library, but composer.lock will be updated. Note that nothing is not a keyword in the update command. There is just nothing this package causes. If you type foobar, the result is the same.
If the Composer version you are using is new enough, you can use the --lock option directly:
composer update --lock
2. Install the library without editing composer.json
You may find it too troublesome to modify composer.json every time you install a library, then you can use the require command directly.
composer require "foo/bar:1.0.0"
This method can also be used to quickly open a new project. The init command has the --require option, which can automatically write composer.json: (note that we use -n so that we don’t have to answer the question)
$ composer init --require=foo/bar:1.0.0 -n $ cat composer.json { "require": { "foo/bar": "1.0.0" } }
3. Derivation is easy
Have you tried the create-project command during initialization?
composer create-project doctrine/orm path 2.2.0
This will automatically clone the repository and check out the specified version. This command is very convenient to use when cloning a library, as there is no need to search for the original URI.
4. Consider caching, giving priority to dist packages
Composer from the past year will automatically archive the dist package you downloaded. By default, the dist package is used for tagged versions, such as "symfony/symfony": "v2.1.4", or wildcards or version ranges, "2.1.*" or ">=2.2,
The dist package can also be used for branches such as dev-master. Github allows you to download the compressed package of a certain git reference. To force the use of a tarball instead of cloning the source code, you can use the --prefer-dist option of install and update.
Here is an example (I used the --profile option to show execution time):
$ composer init --require="twig/twig:1.*" -n --profile Memory usage: 3.94MB (peak: 4.08MB), time: 0s $ composer install --profile Loading composer repositories with package information Installing dependencies - Installing twig/twig (v1.12.2) Downloading: 100% Writing lock file Generating autoload files Memory usage: 10.13MB (peak: 12.65MB), time: 4.71s $ rm -rf vendor $ composer install --profile Loading composer repositories with package information Installing dependencies from lock file - Installing twig/twig (v1.12.2) Loading from cache Generating autoload files Memory usage: 4.96MB (peak: 5.57MB), time: 0.45s
Here, the compressed package of twig/twig:1.12.2 is saved in ~/.composer/cache/files/twig/twig/1.12.2.0-v1.12.2.zip. Use it directly when reinstalling the package.
5. Consider modifications, source code first
When you need to modify the library, cloning the source code is more convenient than downloading the package. You can use --prefer-source to force selection of clone source code.
composer update symfony/yaml --prefer-source
Next you can modify the file:
composer status -v You have changes in the following dependencies: /path/to/app/vendor/symfony/yaml/Symfony/Component/Yaml: M Dumper.php
When you try to update a modified library, Composer will remind you and ask whether to abandon the modification:
$ composer update Loading composer repositories with package information Updating dependencies - Updating symfony/symfony v2.2.0 (v2.2.0- => v2.2.0) The package has modified files: M Dumper.php Discard changes [y,n,v,s,?]?
Prepare for production environment
Finally, when deploying code to the production environment, don’t forget to optimize automatic loading:
composer dump-autoload --optimize
You can also use --optimize-autoloader when installing packages. Without this option, you may see a 20% to 25% performance loss.
If you need help or want to know the details of a certain command, you can read the official documentation or check out this interactive cheat sheet made by JoliCode.
1: Replenish troops 2: Send various signals 3: Know the first choice target you should attack in a team battle, don’t let others rush you and throw away various skills 4: Remember various BUFFs and dragon refresh time 5: Know how to insert and buy wards 6: Be able to use the skills that come with various equipment and props 7: Know how to support teammates from other lanes 8: Know what you should do when Kill 1 enemy player. At this time, the enemy chooses to retreat, but our teammates don't know how to take the opportunity to ward and kill a dragon or something. Instead, they rush to the other person's tower and don't dare to jump over the tower. You Q me, I Q you, and wait until the opponent dies. There are too many situations where one person is resurrected and rushes to destroy our party. You need to know when to do something. In short, practice this a lot. I can’t explain it in two sentences

ThebestapproachforsendingemailsinPHPisusingthePHPMailerlibraryduetoitsreliability,featurerichness,andeaseofuse.PHPMailersupportsSMTP,providesdetailederrorhandling,allowssendingHTMLandplaintextemails,supportsattachments,andenhancessecurity.Foroptimalu

The reason for using Dependency Injection (DI) is that it promotes loose coupling, testability, and maintainability of the code. 1) Use constructor to inject dependencies, 2) Avoid using service locators, 3) Use dependency injection containers to manage dependencies, 4) Improve testability through injecting dependencies, 5) Avoid over-injection dependencies, 6) Consider the impact of DI on performance.

PHPperformancetuningiscrucialbecauseitenhancesspeedandefficiency,whicharevitalforwebapplications.1)CachingwithAPCureducesdatabaseloadandimprovesresponsetimes.2)Optimizingdatabasequeriesbyselectingnecessarycolumnsandusingindexingspeedsupdataretrieval.

ThebestpracticesforsendingemailssecurelyinPHPinclude:1)UsingsecureconfigurationswithSMTPandSTARTTLSencryption,2)Validatingandsanitizinginputstopreventinjectionattacks,3)EncryptingsensitivedatawithinemailsusingOpenSSL,4)Properlyhandlingemailheaderstoa

TooptimizePHPapplicationsforperformance,usecaching,databaseoptimization,opcodecaching,andserverconfiguration.1)ImplementcachingwithAPCutoreducedatafetchtimes.2)Optimizedatabasesbyindexing,balancingreadandwriteoperations.3)EnableOPcachetoavoidrecompil

DependencyinjectioninPHPisadesignpatternthatenhancesflexibility,testability,andmaintainabilitybyprovidingexternaldependenciestoclasses.Itallowsforloosecoupling,easiertestingthroughmocking,andmodulardesign,butrequirescarefulstructuringtoavoidover-inje

PHP performance optimization can be achieved through the following steps: 1) use require_once or include_once on the top of the script to reduce the number of file loads; 2) use preprocessing statements and batch processing to reduce the number of database queries; 3) configure OPcache for opcode cache; 4) enable and configure PHP-FPM optimization process management; 5) use CDN to distribute static resources; 6) use Xdebug or Blackfire for code performance analysis; 7) select efficient data structures such as arrays; 8) write modular code for optimization execution.

OpcodecachingsignificantlyimprovesPHPperformancebycachingcompiledcode,reducingserverloadandresponsetimes.1)ItstorescompiledPHPcodeinmemory,bypassingparsingandcompiling.2)UseOPcachebysettingparametersinphp.ini,likememoryconsumptionandscriptlimits.3)Ad


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment

WebStorm Mac version
Useful JavaScript development tools

SAP NetWeaver Server Adapter for Eclipse
Integrate Eclipse with SAP NetWeaver application server.

SublimeText3 English version
Recommended: Win version, supports code prompts!

MinGW - Minimalist GNU for Windows
This project is in the process of being migrated to osdn.net/projects/mingw, you can continue to follow us there. MinGW: A native Windows port of the GNU Compiler Collection (GCC), freely distributable import libraries and header files for building native Windows applications; includes extensions to the MSVC runtime to support C99 functionality. All MinGW software can run on 64-bit Windows platforms.
