zepgram / magento-dotenv
zepgram/magento-dotenv
Simple autoloader to integrate the Symfony Dotenv component into Magento2
Magento Dotenv
Simple autoloader to integrate Symfony Dotenv component to Magento2.
The implementation can be found under path app/dotenv.php and can be configured safely for your needs.
Compatibility
| Magento Dotenv | v1.* | v2.* |
|---|---|---|
| Symfony Dotenv | ^5.0 | ^5.4 / ^6.0 |
| PHP version | ^7.0 | ^8.0 |
Installation
composer require zepgram/magento-dotenv
How to
You can use it similar way as a Symfony project:
- If .env exists, it is loaded first. In case there's no .env file but a .env.dist, this one will be loaded instead.
- If one of the previously mentioned files contains the APP_ENV variable, the variable is populated and used to load environment-specific files hereafter. If APP_ENV is not defined in either of the previously mentioned files, dev is assumed for APP_ENV and populated by default.
- If there's a .env.local representing general local environment variables it's loaded now.
- If there's a .env.$env.local file, this one is loaded. Otherwise, it falls back to .env.$env.
You can freely edit app/dotenv.php: this file will be not updated.
For more information you can follow the documentation:
https://symfony.com/doc/current/components/dotenv.html
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 2.0.3 | stable | Fail | Magento 2.4.7 Details | 2024-02-12 12:23:58 |
| 2.0.2 | stable | Not tested | Not yet tested Details | 2023-06-12 13:20:58 |
| 2.0.1 | stable | Not tested | Not yet tested Details | 2023-06-12 11:06:37 |
| 2.0.0 | stable | Not tested | Not yet tested Details | 2022-04-01 18:27:49 |
| 1.0.1 | stable | Not tested | Not yet tested Details | 2020-09-02 07:26:42 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2020-08-26 08:45:06 |
| 0.0.1 | stable | Not tested | Not yet tested Details | 2020-02-27 21:28:27 |
Requires 2
| Package | Constraint |
|---|---|
| php | >=8.0.2 |
| symfony/dotenv | ^5.4|^6.0 |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge — a phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
PHPStan
Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases. Cell → details modal.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
More from zepgram
View vendorTechnical module to industrialize API REST call with dependency injection pattern using Guzzle library
Magento2 module to disable search engine and fulltext indexing for category search
This module is a powerful tool for developers who want to process large data sets in a short amount of time
Turn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.