Download the PHP package gene/module-envphp-modules without Composer

On this page you can find all versions of the php package gene/module-envphp-modules. 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 gene/module-envphp-modules

Informations about the package module-envphp-modules

Gene_EnvphpModules

This module allows you to enable a module in app/etc/env.php rather than app/etc/config.php.

This is useful for require-dev dependencies which by default inject their module status into app/etc/config.php, but are never deployed as actual dependencies.

Benefits

This improves developer experience by preventing conflicts and changes on the app/etc/config.php, composer.json, and composer.lock files. All modules are committed in, but the module is only enabled on developer machines. This allows us to ensure dev teams are working with all the tools necessary to deliver high quality software.

This helps maintains zero downtime deployments by allowing module:config:status and setup:db:status to understand that these developer dependencies are purposefully not present, and not a cause for concern.

Installation

Usage

You may have a developer dependency like https://github.com/tddwizard/magento2-fixtures, the standard way to install is like so

This will

  1. Add the module in as a require-dev dependency within composer.json
  2. Set TddWizard_Fixtures => 1 within app/etc/config.php

This module should never end upstream but it is very useful for developers and CI pipelines to have for testing, so we can flag it as enabled in env.php like so.

This will

  1. Set TddWizard_Fixtures => 0 within app/etc/config.php, so this module is never active anywhere without an override in app/etc/env.php
  2. Store metadata about the module under gene_envphp_modules_configphp within app/etc/config.php
  3. Store TddWizard_Fixtures => 1 under gene_envphp_modules_envphp within app/etc/env.php

From here the module will appear enabled locally and within test executions.

Performance

This module is built to have a low footprint on the code. There are 2 main extension points

Performance - Setup Commands

The setup:upgrade, setup:db:status, module:config:status are all customised via the dependency injections in setup/config/autoload/gene-envphp-modules.global.php.

In Gene\EnvphpModules\Model\DeploymentConfigReader and Gene\EnvphpModules\Model\DeploymentConfigWriter we do a series of low impact array lookups and an is_file check per module. These changes only apply to the manually invoked setup commands.

Performance - Module List

We use app/etc/gene_envphp_modules/di.xml to inject the following custom deployment configuration model into the module list

On production/staging environments there will be no development modules defined in env.php, so the only additional overhead is an if condition and a lookup of the already available deployment configuration data.

All versions of module-envphp-modules with dependencies

PHP Build Version
Package Version
Requires php Version ^8.1
magento/framework Version *
magento/magento-composer-installer Version *
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 gene/module-envphp-modules contains the following files

Loading the files please wait ...