Download the PHP package devmcc/package-dev without Composer

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

Informations about the package package-dev

PackageDev

A simple tool for developing Composer packages.

PackageDev makes use of symlinks to make it seem as if the package you are developing is run in vendor. Thanks to this, you can make changes to your package and immediately check the results.

Installation

It is recommended to install PackageDev globally:

After you have installed PackageDev, go to the root directory of the project that needs to use your package and run:

Next, open up your project's composer.json file and add the following:

Linking packages

After running init, a new directory called packages was created, you need to add your packages to this directory.

If your package is called devmcc/testing, you need to add your package in the following folder structure:

Link your package with the following command:

Unlink your package with the following command:

Using a phar archive

PackageDev can be run through a phar archive. This can be very usefull for when you are using things like Docker containers.

You can create an archive with:

Next, make the following changes to your project's composer.json file:

NOTE: In order to be able to create phar archives, you need to add the following to your php.ini file:

Upgrading from version 1

For anyone who was using version 1, here is how you can upgrade to version 2: Unlink all your packages, do the upgrade and link them again

Testing

After you have cloned the repo and installed all dependencies you can do the following:

All versions of package-dev with dependencies

PHP Build Version
Package Version
Requires php Version ^7.1 || ^8.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 devmcc/package-dev contains the following files

Loading the files please wait ....