Download the PHP package piedweb/composer-symlink without Composer

On this page you can find all versions of the php package piedweb/composer-symlink. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of piedweb/composer-symlink

Informations about the package composer-symlink

Open Source Package

Composer Symlink

Latest Version Code Coverage Type Coverage Total Downloads

Disk efficient composer (fixer || symlinker) ➜ multiple projects relying on the same package version, why having multiple copies ?

This is a duplicate code killer to win some disk space.

Each vendor/{vendor}/{package} directory is moved to a shared {globalVendorDir}/{vendor}/{package}-{version} and replaced by a symlink. Projects locking the same version end up sharing a single copy; projects locking different versions keep their own.

Install

Via Packagist

Create a new project and install the dependency

Usage

Create cs.php

Then run it after each composer update:

You can also wire it in the post-update-cmd script of each project:

Arguments

Argument Description
$projectPathList Every project sharing the global vendor directory. Each one needs a vendor/ directory and a composer.lock.
$globalVendorDir Absolute path of the shared vendor directory. Created on demand. A relative path throws.
$pruneUnused true by default: shared packages no longer referenced are deleted.

The project list must be exhaustive

Pruning is what reclaims the disk space, and it decides what to delete from the global vendor directory alone — it has no way to discover a project you did not list. Leaving a project out deletes the packages it still symlinks, and its vendor/ is left with dangling links until the next composer install.

So either list every project sharing the directory, or pass pruneUnused: false and clean up by hand:

What is left alone

Contributing

Please see contributing

Credits

License

The MIT License (MIT). Please see License File for more information.

All versions of composer-symlink with dependencies

PHP Build Version
Package Version
Requires php Version >=8.4
symfony/filesystem Version ^7|^8
thecodingmachine/safe Version ^3
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package piedweb/composer-symlink contains the following files

Loading the files please wait ...