Download the PHP package empaphy/docker-composer without Composer

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

Informations about the package docker-composer

docker-composer

Composer plugin that ensures scripts are always executed within a Docker Compose service.

Installation

Composer 2.2 and newer require plugins to be allowed explicitly. Composer 1 ignores allow-plugins.

Configuration

Configure the target service in the root package's composer.json:

Configure service for the default redirection target, and configure service-mapping for scripts that should run in a different service. If neither resolves the current script, the plugin warns once per Composer run and lets host scripts run normally.

Supported keys:

Unknown keys warn and are ignored. Invalid known values fail before Docker is run.

Behavior

When Composer dispatches a top-level script on the host, the plugin runs the same script inside the configured service and prevents the host-side script from continuing.

If service-mapping contains the current script name under a service, that service is used instead of the default service.

In exec mode, the plugin checks whether the service is already running:

If the service is not listed, it starts it:

In run mode, it runs:

The plugin passes DOCKER_COMPOSER_INSIDE=1 into the container. Composer scripts then run normally because the plugin detects that Composer is already inside a container. It also treats /.dockerenv, /run/.containerenv, and common cgroup markers as container signals.

Set DOCKER_COMPOSER_DISABLE=1 to bypass Docker redirection temporarily.

Scope

This plugin redirects Composer scripts, including lifecycle scripts such as post-install-cmd and custom scripts run through composer run-script.

It also redirects dependency commands before host execution so platform requirements are resolved from inside the configured service:

All versions of docker-composer with dependencies

PHP Build Version
Package Version
Requires php Version >=8.1
composer-plugin-api Version >=1.1
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 empaphy/docker-composer contains the following files

Loading the files please wait ...