- \n
- \n
For Composer, type
composer<\/code>. You will get the following result:<\/p>\n\n<\/p>
![\"The](\"https:\/\/blog.hostinger.io\/pt\/support\/wp-content\/uploads\/sites\/59\/2022\/07\/dbd8e7fc-1ef7-4496-8f6e-fde59a2294f2.jpg\")
<\/div>\n<\/p>\n<\/li>\n
- \n
Similarly, you can type
composer2<\/code> for the Composer 2 version:<\/p>\n<\/p>\n
![\"The](\"https:\/\/blog.hostinger.io\/pt\/support\/wp-content\/uploads\/sites\/59\/2022\/07\/d82a98fc-9692-4476-9db3-5c417876e786.jpg\")
<\/div>\n<\/li>\n<\/ul>\n<\/p>
In both cases, the command-line template will be shown below the Composer version, as well as a list of available options <\/b>and commands<\/b>.<\/p>
\n<\/p>
How to Install a Package Using Composer<\/h2>
- \n
- \n
Go to the Packagist<\/a> <\/b>repository and find the PHP package you want to install. Keep this page open for reference<\/p>\n<\/li>\n
- \n
Access your hosting environment using SSH<\/a><\/b><\/p>\n<\/li>\n
- \n
Use the
cd<\/code> command to navigate to the desired directory on your hosting. Consider that each package needs to be installed separately on every website<\/b> or project where you will need it<\/p>\n<\/li>\n- \n
Copy the command from Packagist and paste it onto the terminal<\/b>. This will either create the composer.json<\/b>, composer.lock<\/b> files and the vendor<\/b> directory or update them if they already exist<\/p>\n<\/li>\n
- \n
Proceed to test the installed package by creating or modifying your relevant PHP files<\/p>\n<\/li>\n<\/ol>
\nIf your hosting uses PHP version<\/a><\/b> 8.0 or higher<\/b>, use composer2<\/b> instead of composer<\/b>, like this:
composer2 [command]<\/code><\/p>\n<\/div>\n<\/p>
Example<\/h3>
Let’s use PHPMailer <\/b>as an example. Open the Packagist repository<\/a><\/b> to find the installation command:<\/p>
\n<\/p>
![\"The](\"https:\/\/blog.hostinger.io\/pt\/support\/wp-content\/uploads\/sites\/59\/2022\/07\/255bb82f-cd16-4b2d-acfa-f8716d7d72a5.jpg\")
<\/div>Now, on your SSH terminal, navigate to the website’s root folder. In this case, for domain.tld<\/b>, the
cd<\/code> command will be as follows:<\/p>\n<\/p>
cd domains\/domain.tld\/public_html\/<\/code><\/pre>\n<\/p>
Once you’ve reached the desired location, enter the composer command from Packagist. Since support for Composer 1 is deprecated, the composer2<\/b> command will be used instead:<\/p>
\n<\/p>
composer2 require phpmailer\/phpmailer<\/code><\/pre>\n<\/p>
The output will look similar to this:<\/p>
\n<\/p>
![\"A](\"https:\/\/blog.hostinger.io\/pt\/support\/wp-content\/uploads\/sites\/59\/2022\/07\/0e8f8f2e-5549-4193-a452-fcf1fe28a182.jpg\")
<\/div>That’s it – PHPMailer is successfully installed for domain.tld<\/b>. You can verify it because the vendor\/phpmailer<\/b> directory will be created.<\/p>
\n<\/p>
For installing it in another project, return to the domains<\/b> directory using the command
cd ..\/..<\/code> then navigate to the public_html<\/b> directory of the new domain, such as website.tld<\/b>:<\/p>\n<\/p>
cd website.tld\/public_html\/<\/code><\/pre>\n<\/p>
Repeat the installation process as before. In case you encounter any issues, check this article: Solving Common Composer Errors<\/a><\/b>.<\/p>
\n<\/p>
Additional Resources<\/b><\/p>
- \n
- \n