Home  >  Article  >  Development Tools  >  Pitfalls of running composer in wamp environment

Pitfalls of running composer in wamp environment

藏色散人
藏色散人forward
2019-09-09 13:40:572456browse

The following column composer usage tutorial will introduce you to the solutions to the pitfalls of running composer in a wamp environment. I hope it will be helpful to friends in need.

Pitfalls of running composer in wamp environment

I got an error when installing laravel with composer today

The openssl extension is required for SSL/TLS protection but is not availab le. If you can not enable the openssl extension, you can disable this error , at your own risk, by setting the 'disable-tls' option to true.

It is said online that OpenSSL is not turned on. Open php.ini, enable the plug-in and set the corresponding certificate and then restart Apache.

Theoretically speaking, there should be no problem at this step. There is also an OpenSSL extension in phpinfo();, but the error remains.

After research, we found that the basis for composer to judge OpenSSL is: the php.ini file in the php directory under the current environment variable, but the php.ini file under wamp actually corresponds to phpForApache.ini in the php directory. Instead of php.ini, so copy all the contents in phpForApache.ini to php.ini, and run composer install again and no error will be reported.

The above is the detailed content of Pitfalls of running composer in wamp environment. For more information, please follow other related articles on the PHP Chinese website!

Statement:
This article is reproduced at:segmentfault.com. If there is any infringement, please contact admin@php.cn delete
Previous article:Share composer tipsNext article:Share composer tips