'How to use composer with WampServer?

I am trying to use composer with my WampServer.

My path for all the files is C:\wamp64\www, but when I run composer it will install the vendor file and other stuff somewhere else.

I don't even know where and I can't change the path of where is my project. I tried everything already and it still dose not seem to install the vendor file in my project folder.



Solution 1:[1]

Although it is an old post, it maybe useful as far as Wampserver exists, so the easiest fix is this:

  1. Go to the "bin/php" folder inside you wampserver, usually at C:\wampXX\bin\php, and look for the php version used in your wampserver. You can navigate to http://localhost to find that, or click in the Wampserver icon on Windows taskbar (If yours doesn't have the version number aside, click on PHP -> Version and you'll see the checked one):

enter image description here

  1. In the "bin/php" folder open the corresponding folder to your PHP version, in my case "7.0.33" and copy this path:

enter image description here

  1. Go to Windows Environment Variables, and in System Variables add that PHP's folder path you copied to Path variable (You can search on Google how to change a Path variable on your Windows version).

P.S.: In case you switch PHP version it won't work anymore, and you'll have to do that again. But now, changing for the correct PHP version folder.

  1. After doing that, go to composer site download the windows installer.

  2. CD into your projects root directory and run (which must contain a composer.json file):

    composer install

That's it. Maybe a lot of work, but at the end it's all quite simple.

Solution 2:[2]

I don't use this hack any more. I think there are better tools to solve this problem, such as Laragon, LocalWP (if you develop Wordpress plugins/themes) or Devilbox (you need to install Docker to use Devilbox).


I don't know if the poster will read and vote this answer. I had this problem and solved it, and I want to share my research with other people.

TL; DR

  • In Windows 10, you can have Composer without producing an error in Wampserver if you install it on the Windows Subsystem for Linux (WSL) environment.
  • Install PHP on WSL
  • Then install Composer on WSL

The problem

In Windows, Composer requires to set the system variable PATH to work properly during the installation; it doesn't matter if it is installed globally using the Windows Installer or locally, following this procedure

However, inserting the executable PHP file location in PATH causes an error in Wampserver, the ERROR C:/wamp64 or PHP in path. You can see the error message if you left-click on the Wampserver icon in the notifications area of the task bar.

Although Wampserver may work as usual, it could eventually fail according to the answer to this question on the official Wampserver forum:

Wampserver does not create paths in PATH system environment variable.

Wampserver does not use PATH system environment variable.

Some content - paths to PHP or mysql versions - of the PATH system environment variable can create Wampserver malfunctions because PHP configuration files (php.ini) or MySQL (my.ini) are searched first in the paths indicated by the contents of the PATH environment variables before being searched in the Apache, PHP or MySQL folders.

That is why, with version 3.1.3, the content of the PATH environment variable is checked and you are notified if there is a problem.

If your Wamperserver installation suffers already of this error, then

  • follow the advice from the Wampserver forum,

  • back up the content of your www folder,

  • uninstall Wampserver,

  • reinstall Wampserver.

If you have Windows 10 and followed the previous steps, then you are ready to implement the solution I propose.


The solution

The only solution I found in my research was explained in this tutorial by Jeff Geerling. My answer follows this tutorial in a somewhat loose way.

My starting point

These were the settings of my PC when I began this procedure:

Although Visual Studio with the WSL integrated terminal is not strictly necessary, I had it set because I intended to install and use Composer with it.

1 - Install PHP on WSL

To work correctly, Composer needs PHP but WSL does not come installed with it. So it is necessary to install PHP in this enviroment. According to this answer in AskUbuntu.com, the easiest way to install PHP on WSL is adding Ond?ej SurĂ½'s PPA. In the Visual Studio Code WSL integrated terminal, type:

sudo add-apt-repository ppa:ondrej/php
sudo apt-get update

Test that PHP was installed correctly typing php --version. If PHP was installed correctly, the terminal will return a message like:

PHP 7.2.10-0ubuntu0.18.04.1 (cli) (built: Sep 13 2018 13:45:02) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.2.10-0ubuntu0.18.04.1, Copyright (c) 1999-2018, by Zend Technologies

2 - Install Composer on WSL

There are two ways to do it:

The easier one: just type on the integrated terminal sudo apt-get install composer and that will be it.

The second one, and a better approach in my opinion: go to the Composer download page and get the installation code:

php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');"
php -r "if (hash_file('SHA384', 'composer-setup.php') === '544e09ee996cdf60ece3804abc52599c22b1f40f4323403c44d44fdfdd586475ca9813a858088ffbc1f233e9b180f061') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;"
php composer-setup.php
php -r "unlink('composer-setup.php');"

Warning: Do NOT copy/paste the code provided in this tutorial to install Composer. According to the Composer download page, the installation code

will change with every version of the installer.

The best practice here is to get the installation code directly from the download page.

I think this method is a better approach because, with the given code, it is possible to verify the SHA384 of the file and make sure it has not been tampered with.

If you installed Composer through the installation code from the developer website, in order to put that file into the global path on WSL, move the composer.phar file into the /user/bin/local folder with the bash command:

sudo mv composer.phar /user/bin/local/composer

If you installed Composer with the first command, this last step won't be necessary.

To check that the software was installed correctly, type composer on the integrated terminal. You should view a list of composer calling options and available commands.

Keep in mind that, to use Composer, you will need to type the commands in the WSL terminal.

Solution 3:[3]

Just run composer on your project folder.

Say your project path is on C:\wamp64\www\project0. So, just run composer install inside project0 folder. Composer will create vendor folder inside this project0 folder. This folder contain some folders of installed libraries.

Composer also generate a file composer.lock. This file contain information of installed libraries.

Then, when you want to use the libraries, please add this code inside your php file.

require_once "vendor/autoload.php";

This will call autoloader, so you don't need to use require_once anymore to load PHP Classess. Just call the Class using use keyword.

use Library0/Class0;
use Library1/Class1;
use Library2/Class2;

Solution 4:[4]

I used a different approach. I admit that it is dirty, and every time I switch PHP versions, I need to remember to update what I did, but well... it works :)

Go to C:\ProgramData\ComposerSetup\bin. There is a file there: composer.bat. This is executed every time you enter a composer install or a composer update command. Edit it with a notepad or any other text editor. You should see something like this:

@ECHO OFF
php "%~dp0composer.phar" %*

What we want to do is to give a direct path to php.exe, so let's comment out the current command and write our own:

@ECHO OFF
REM php "%~dp0composer.phar" %*
C:\wamp64\bin\php\php5.6.40\php.exe "%~dp0composer.phar" %*

Now everything works. But once you switch to another PHP version in Wampserver, you should update this file too.

By the way: a similar change can be done to make PHP sniffer or PHPUnit work too. Their bat files are in C:\Users\[your windows user]\AppData\Roaming\Composer\vendor\bin folder.

Solution 5:[5]

That answer is pretty bad. I have figured it out already on my own. I had to use cd commned in commend lines to get in this folder.

So after CMD i would type cd C:\wamp64\www\project0 thats proper answer to my problem.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1
Solution 2
Solution 3 Dolly Aswin
Solution 4 george007
Solution 5 Goriss