PHPackages                             nexus633/processenv - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Parsing & Serialization](/categories/parsing)
4. /
5. nexus633/processenv

ActiveLibrary[Parsing & Serialization](/categories/parsing)

nexus633/processenv
===================

parse .env files to load variables to $\_ENV and/or $\_SERVER automatically

v1.0.1(2y ago)03GPL-3.0-or-laterPHPPHP ^8.0

Since Oct 23Pushed 2y ago1 watchersCompare

[ Source](https://github.com/Nexus633/Processenv)[ Packagist](https://packagist.org/packages/nexus633/processenv)[ RSS](/packages/nexus633-processenv/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (2)Dependencies (1)Versions (2)Used By (0)

Processenv
==========

[](#processenv)

### use .env files in your projects

[](#use-env-files-in-your-projects)

With **Processenv** you have the opportunity to use environment variables directly in your project.
You can parse **.env** files and add them to the super global variables ***$\_ENV*** and ***$\_SERVER***.
You can also specify default values with **Processenv**. These values are used if there is no environment variable.
This makes it easier to check for errors and use standard configurations.

You also have the option to define nested variables, arrays and objects in the environment file
You can use inline comments and masked hashtags (\\#)

Version 1.0.1
-------------

[](#version-101)

checkout the [Changelog](CHANGELOG.md)

---

Installation
------------

[](#installation)

```
$ composer require nexus633/processenv
```

---

usage
-----

[](#usage)

```