Composer Install
Patrizia Leones
Composer is not a package manager in the same sense as Yum or Apt are. Yes,it deals with "packages" or libraries, but it manages them on a per-projectbasis, installing them in a directory (e.g. vendor) inside your project. Bydefault, it does not install anything globally. Thus, it is a dependencymanager. It does however support a "global" project for convenience via theglobal command.
Composer in its latest version requires PHP 7.2.5 to run. A long-term-supportversion (2.2.x) still offers support for PHP 5.3.2+ in case you are stuck witha legacy PHP version. A few sensitive php settings and compile flags are alsorequired, but when using the installer you will be warned about anyincompatibilities.
Composer needs several supporting applications to work effectively, making theprocess of handling package dependencies more efficient. For decompressingfiles, Composer relies on tools like 7z (or 7zz), gzip, tar, unrar,unzip and xz. As for version control systems, Composer integrates seamlesslywith Fossil, Git, Mercurial, Perforce and Subversion, thereby ensuring theapplication's smooth operation and management of library repositories. Beforeusing Composer, ensure that these dependencies are correctly installed on yoursystem.
Composer offers a convenient installer that you can execute directly from thecommand line. Feel free to download this fileor review it on GitHubif you wish to know more about the inner workings of the installer. The sourceis plain PHP.
The installer will check a few PHP settings and then download composer.pharto your working directory. This file is the Composer binary. It is a PHAR(PHP archive), which is an archive format for PHP which can be run onthe command line, amongst other things.
You can install Composer to a specific directory by using the --install-diroption and additionally (re)name it as well using the --filename option. Whenrunning the installer when followingthe Download page instructions add thefollowing parameters:
You can place the Composer PHAR anywhere you wish. If you put it in a directorythat is part of your PATH, you can access it globally. On Unix systems youcan even make it executable and invoke it without directly using the phpinterpreter.
Note: On some versions of macOS the /usr directory does not exist bydefault. If you receive the error "/usr/local/bin/composer: No such file ordirectory" then you must create the directory manually before proceeding:mkdir -p /usr/local/bin.
Note: You may also use composer instead of composer/composer as image name above. It is shorter and is a Docker official image but is not published directly by us and thus usually receives new releases with a delay of a few days. Important: short-aliased images don't have binary-only equivalents, so for COPY --from approach it's better to use composer/composer ones.
This installer script will simply check some php.ini settings, warn you if they are set incorrectly, and then download the latest composer.phar in the current directory. The 4 lines above will, in order:
By default the installer and composer self-update will download the latest stable version only. You may select a different download channel though.
If you would like to help test pre-release versions you can use the --preview flag on either the installer or self-update.
For snapshot builds, which are done from the latest Composer commit, you can use the --snapshot flag.
To programmatically install specific major versions you can use the --1 or --2 flag. To select the latest 2.2 LTS you can use --2.2.
I noticed that my plugins were not inside the mu-plugins and plugins directory. So i ran composer install and composer installed all dependencies. No errors. But then, the plugins directories were still empty.
I have small project made in symfony2 when I try to build it on my server it's always fails when unzipping symfony. Build was OK and suddenly composer won't unzip symfony and I didn't change anything. I tried to build with Jenkins and also manually from bash with same result. It's not permissions problem and also internet connection on my server is OK.
Composer itself impose a limit on how long it would allow for the remote git operation. A look at the Composer documentation confirms that the environment variable COMPOSER_PROCESS_TIMEOUT governs this. The variable is set to a default value of 300 (seconds) which is apparently not enough for a large clone operation using a slow internet connection.
After noticing Windows' "antimalware executable" taking up considerable CPU cycles when doing this composer install/update, I disabled "real-time protection" on the Windows 10 machine, and my composer update/install worked!!
It's an old thread but I found out the reason for time out was running a php debugger (PHPStorm was listening to xdebug connections) which caused the process timeout. When I closed the PHPStorm or disabled the xdebug extension, no time out occurred.
The problem: it was continuing to try download every 5 minutes. This was not noticeable at first because there are no timestamps, even when running composer -vvv install. After many increments of 5-15 minutes, I painfully realized I was in a programmer's hell - waiting long periods of time between each attempt to fix said problem. Additionally, I have no real "timeout" error messaging to help figure this out.
Supported by this article on composer's site, I discovered that I could edit the default_socket_timeout since it will choose which ever number is larger (default 300) or default_socket_timeout (default 60):
It means your network is probably so slow that a request took over 300seconds to complete. This is the minimum timeout Composer will use, but you can increase it by increasing the default_socket_timeout value in your php.ini to something higher.
I got it to download (had to set to more than 10 mins!) However, I got a new problem about zip archives - so I removed the compress: true from config, removed the vendor folder, and composer clearcache in hopes that it would solve the issue. It worked!
On Windows 11, and somewhat related to an above answer, adding a folder exclusion to real-time protection can stop the "antimalware executable" from scanning the folder and causing the timeout (and saves entirely disabling "real-time protection").
None of the solutions worked for me running on win10 wsl ubuntu (disabling firewall, removing debuggers, clearing cache, increasing timeout, deleting vendor).The only way that worked was deleting vendor and composer.lock from the main machine, copying composer.json to a fresh machine, install php and composer, run composer install (it should take less than 1 second to execute), then copying the vendor dir to the other machine, and run composer update.
Was this ever solved? I am running into the same issue and have tried the above on this thread. I can verify Composer is installed yet it will not load the install.php in I get the same error on this page.
Loading composer repositories with package information
Installing dependencies from lock file
Nothing to install or update
Package league/url is abandoned, you should avoid using it. Use league/uri instead.
Generating autoload files
To be clear, I have a working SuiteCRM instance in a separate folder ( ) where this is for a separate instance that I want to have as a test area for updates and other tweaking ( ). The test version is not working.
Hi
Eventually what did the trick for me was to download and install composer executable (here -Composer). Then download XMAP or AMPPS. When running the composer setup, it asks you to point it to a php.exe file, then point it to the PHP file in either XMAP or AMPPS.
. Up until Mautic 4, users could download Mautic as a ZIP file and install it on any PHP server. However, many users were running into installation and update errors, many of which caused considerable frustration and in some cases, significant...
After working perfectly the week before, Composer is now prompting to install its helper tool over and over again. When I first launch Composer, it shows as not responding in Activity Monitor, then it prompts to install the helper tool. If I go to /Library/PrivilegedHelperTools I do not see the Composer helper called "com.jamfsoftware.Composer.helper". I do see it at this file path on my personal MacBook Pro, so I know that is the correct location for the helper to be installed. I did try manually copying the helper from its location at /Applications/Jamf Pro/Composer.app/Contents/Library/LaunchServices/com.jamfsoftware.Composer.helper to /Library/PriveledgedHelperTools, but when I do this and then launch Composer again, I see it get deleted, and then I see the prompt again. Here are the things I've tried:
I'm at a loss and I need to use Composer ASAP. I will need to use it on my personal MacBook Pro if I can't get it working. I am running macOS Sonoma on both Macs. I will assume that Composer 10.50 is compatible with Sonoma since it was working before. Can anyone help?
This is not an uncommon problem. There are posts about this behavior on multiple sites, with multiple versions of Composer and on both macOS Ventura and Sonoma. Unfortunately I don't recall anyone ever finding a definitive answer as to what triggers it or a solution.
I think I have bigger issues. While working on this, I went into Privacy & Security to toggle full disk access off and on again for Composer. When I do this, I get prompted for my password, then the toggle goes to the off position. Right after that, it goes back to on. This same thing happens with every other app I try this with, even those that are not controlled by a configuration profile. The setting for Composer is not. My own MacBook Pro is excluded from a lot of the PPPC profiles that we have in our Jamf Pro server just to give me the easy ability to turn something off if I need to. I'm going to just wipe and reinstall this system completely. I noticed that it had some odd sluggish behavior too so hopefully all of my issues will be fixed by an erase and reinstall. All of my data is in cloud storage, so I don't have to spend a lot of time backing up. Thanks for your suggestions. You have always been helpful.
c80f0f1006