Php composer install directory

Install package into custom directory Composer

Hey I am trying to install a package into a custom ‘admin’ directory using composer. Here is my JSON:

Now when I run composer install it all installs but defaults to vendor/aheinze/cockpit I cannot for the life of me figure out why. Have done my research this should be the right code. any obvious errors? Cheers.

5 Answers 5

I have implemented this composer plugin to install packages into user (custom) defined folders you can just include it in your composer.json, follow the example and tell me if you have more questions 🙂

composer-custom-directory-installer

A composer plugin, to install differenty types of composer packages in custom directories outside the default composer default installation path which is in the vendor folder.

This is not another composer-installer library for supporting non-composer package types i.e. application .. etc. This is only to add the flexability of installing composer packages outside the vendor folder. This package only supports composer package types,

The type of the package. It defaults to library.

Package types are used for custom installation logic. If you have a package that needs some special logic, you can define a custom type. This could be a symfony-bundle, a wordpress-plugin or a typo3-module. These types will all be specific to certain projects, and they will need to provide an installer capable of installing packages of that type.

How to use

"require":< "php": ">=5.3", "mnsami/composer-custom-directory-installer": "1.1.*", "monolog/monolog": "*" > 

by adding the installer-paths part, you are telling composer to install the monolog package inside the monolog folder in your root directory.

• As an added new feature, we have added more flexibility in defining your download directory same like the composer/installers , in other words you can use variables like and in your installer-path section:

the above will manage to install the doctrine/orm package in the root folder of your project, under customlibs .

Note

Composer type: project is not supported in this installer, as packages with type project only make sense to be used with application shells like symfony/framework-standard-edition , to be required by another package.

Источник

Introduction#

Composer is a tool for dependency management in PHP. It allows you to declare the libraries your project depends on and it will manage (install/update) them for you.

Dependency management#

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-project basis, installing them in a directory (e.g. vendor ) inside your project. By default, it does not install anything globally. Thus, it is a dependency manager. It does however support a «global» project for convenience via the global command.

This idea is not new and Composer is strongly inspired by node’s npm and ruby’s bundler.

1. You have a project that depends on a number of libraries.
2. Some of those libraries depend on other libraries.

1. Enables you to declare the libraries you depend on.
2. Finds out which versions of which packages can and need to be installed, and installs them (meaning it downloads them into your project).
3. You can update all your dependencies in one command.

See the Basic usage chapter for more details on declaring dependencies.

System Requirements#

Composer in its latest version requires PHP 7.2.5 to run. A long-term-support version (2.2.x) still offers support for PHP 5.3.2+ in case you are stuck with a legacy PHP version. A few sensitive php settings and compile flags are also required, but when using the installer you will be warned about any incompatibilities.

Composer needs several supporting applications to work effectively, making the process of handling package dependencies more efficient. For decompressing files, Composer relies on tools like 7z (or 7zz ), gzip , tar , unrar , unzip and xz . As for version control systems, Composer integrates seamlessly with Fossil, Git, Mercurial, Perforce and Subversion, thereby ensuring the application’s smooth operation and management of library repositories. Before using Composer, ensure that these dependencies are correctly installed on your system.

Composer is multi-platform and we strive to make it run equally well on Windows, Linux and macOS.

Installation — Linux / Unix / macOS#

Downloading the Composer Executable#

Composer offers a convenient installer that you can execute directly from the command line. Feel free to download this file or review it on GitHub if you wish to know more about the inner workings of the installer. The source is plain PHP.

There are, in short, two ways to install Composer. Locally as part of your project, or globally as a system wide executable.

Locally#

To install Composer locally, run the installer in your project directory. See the Download page for instructions.

The installer will check a few PHP settings and then download composer.phar to 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 on the command line, amongst other things.

Now run php composer.phar in order to run Composer.

You can install Composer to a specific directory by using the —install-dir option and additionally (re)name it as well using the —filename option. When running the installer when following the Download page instructions add the following parameters:

php composer-setup.php --install-dir=bin --filename=composer

Now run php bin/composer in order to run Composer.

Globally#

You can place the Composer PHAR anywhere you wish. If you put it in a directory that is part of your PATH , you can access it globally. On Unix systems you can even make it executable and invoke it without directly using the php interpreter.

After running the installer following the Download page instructions you can run this to move composer.phar to a directory that is in your path:

mv composer.phar /usr/local/bin/composer

If you like to install it only for your user and avoid requiring root permissions, you can use ~/.local/bin instead which is available by default on some Linux distributions.

Note: If the above fails due to permissions, you may need to run it again with sudo .

Note: On some versions of macOS the /usr directory does not exist by default. If you receive the error «/usr/local/bin/composer: No such file or directory» then you must create the directory manually before proceeding: mkdir -p /usr/local/bin .

Note: For information on changing your PATH, please read the Wikipedia article and/or use your search engine of choice.

Now run composer in order to run Composer instead of php composer.phar .

Installation — Windows#

Using the Installer#

This is the easiest way to get Composer set up on your machine.

Download and run Composer-Setup.exe. It will install the latest Composer version and set up your PATH so that you can call composer from any directory in your command line.

Note: Close your current terminal. Test usage with a new terminal: This is important since the PATH only gets loaded when the terminal starts.

Manual Installation#

Change to a directory on your PATH and run the installer following the Download page instructions to download composer.phar .

Create a new composer.bat file alongside composer.phar :

C:\bin> echo @php "%~dp0composer.phar" %*>composer.bat

PS C:\bin> Set-Content composer.bat '@php "%~dp0composer.phar" %*'

Add the directory to your PATH environment variable if it isn’t already. For information on changing your PATH variable, please see this article and/or use your search engine of choice.

Close your current terminal. Test usage with a new terminal:

Composer version 2.4.0 2022-08-16 16:10:48

Docker Image#

Composer is published as Docker container in a few places, see the list in the composer/docker README.

docker pull composer/composer docker run --rm -it -v "$(pwd):/app" composer/composer install

To add Composer to an existing Dockerfile you can simply copy binary file from pre-built, low-size images:

# Latest release COPY --from=composer/composer:latest-bin /composer /usr/bin/composer # Specific release COPY --from=composer/composer:2-bin /composer /usr/bin/composer

Read the image description for further usage information.

Note: Docker specific issues should be filed on the composer/docker repository.

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.

Using Composer#

Now that you’ve installed Composer, you are ready to use it! Head on over to the next chapter for a short demonstration.

Found a typo? Something is wrong in this documentation? Fork and edit it!

Composer and all content on this site are released under the MIT license.

Источник

How to specify Composer install path?

I am using Symfony 1, and I’d like to install them on plugins/sfGuardPlugin/ . How do I specify this?

3 Answers 3

It seems that you can define the vendor dir to be something else ( plugins in your case):

Then, you might rename the package name to not have a level dir inside, like:

So, your composer.json should look like this:

Using this configuration, you will get the path (which is of course not good for symfony):

I found a workaround with this composer.json :

Nice, also can I somehow make it so that the extracted folder does not go as deep as it does now: plugins/sfGuardPlugin/sfGuardPlugin-4.0.2/ , instead I want plugins/sfGuardPlugin ?

is there a way to specify the vendor dir for some specific package only, and leave the others as default?

This is a great and researched answer, but don’t loose Adam’s V., because it seems more official, oh and easy 😉

You can also use composer/installers, a multi-framework composer library installer with the «symfony1-plugin» package type. This is what my composer.json file looks like, in order for it to install both Symfony 1.4 (in lib/vendor) and plugins in (/plugins):

< "config": < "vendor-dir": "lib/vendor" >, "repositories": < "symfony": < "type": "package", "package": < "name": "symfony/symfony1", "version": "1.4", "dist": < "url": "https://github.com/symfony/symfony1/zipball/1.4", "type": "zip" >> >, "sfResquePlugin" : < "type": "package", "package": < "name": "devpips/sfResquePlugin", "type": "symfony1-plugin", "version": "0.1", "dist": < "url": "https://github.com/devpips/sfResquePlugin/zipball/master", "type": "zip" >> > >, "require": < "composer/installers": "dev-master", "symfony/symfony1": "1.4", "devpips/sfResquePlugin":"0.1" >> 

@IsaacLubow, this will be done by composer-installers package, as symfony1 have a plugin there 🙂 Check Symfony1Installer.php

See COMPOSER_VENDOR_DIR environment variable.

By setting this var you can make Composer install the dependencies into a directory other than vendor.

Can be helpful in the case you want to override this in a particular environment such as vagrant or docker where you wouldn’t want this to be in a shared folder / volume.

And as J0k said, there’s vendor-dir in config section of composer.json

Defaults to vendor. You can install dependencies into a different directory if you want to. $HOME and ~ will be replaced by your home directory’s path in vendor-dir and all *-dir options below.

Источник