Download the PHP package tormjens/workbench without Composer

On this page you can find all versions of the php package tormjens/workbench. 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?

Informations about the package workbench

Composer Workbench

A workbench for Composer that allows you to symlink your "offline" packages without writing them to the composer.lock file.

!!Please note!! This package has only been tested on macOS. It should work fine for Linux, but probably not for Windows.

Installation

Workbench is a plugin for Composer and installs like so:

composer global require tormjens/workbench

Usage

Once installed you'll notice a workbench.json file in your root composer directory (create it if you can't find it). On a mac that's usually /Users/username/.composer.

The file should look like this:

Inside the sources key, you'll place the absolute paths to where your local packages are located. It will search using a glob so if you have many packages you may specify the "top level".

For example if you have packages at

You would then only add the path /Users/username/packages and all of your packages would be found.

Inside the targets key, you'll place the absolute paths to where this plugin should be enabled. This will also search using a glob. A few examples:

So your workbench.json could look like:

Run Composer without Workbench

Some times, for various reasons, you may want to run composer install and other commands without triggering workbench. In that case you may prefix the command with WORKBENCH=0. This will deactivate Workbench for that run.

WORKBENCH=0 composer install

Caveats

While Workbench solves the issue of your custom local packages not being written to your project's .lock file, it will not be able to detect local changes to your composer.json during install. Hence you'll need to push and update for every of those changes.

All versions of workbench with dependencies

PHP Build Version
Package Version
Requires php Version >=7.0
composer-plugin-api Version ^1.0 || ^2.0
symfony/filesystem Version ^2.5 || ^3.0 || ^4.0
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 tormjens/workbench contains the following files

Loading the files please wait ....