Download the PHP package romanzipp/laravel-env-normalizer without Composer

On this page you can find all versions of the php package romanzipp/laravel-env-normalizer. 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 romanzipp/laravel-env-normalizer

Informations about the package laravel-env-normalizer

Laravel Env Normalizer

Latest Stable Version Total Downloads License GitHub Build Status

Format .env files according to your .env.example structure to keep track of used and unused variables.

Why?

I like to keep a clear overview of all available environment variables by adding some default values to my version controled .env.example file. This packages helps with structuring your example files.

Contents

Installation

Usage

List all available options

Specify reference and target file(s)

Reference and target options are optional. If not specified the command will only look for a .env.example (as reference) and .env file (as target).

Automatically format all other .env files

This option will discover any other .env.* files located in the base path and add them to the target list.

Create backup files

This will create a {name}.bak backup file for each modified target file.

Dry run

Log the expected output to the console instead of writing it to the file.

Example normalization

.env.example previous .env new .env 
BASE_URL=localhost 

# Database

DB_HOST=127.0.0.1
DB_PORT=${DEFAULT_PORT}
DB_USER=
DB_PASSWORD=

# Mail

MAIL_CONNECTION=







 
DB_HOST=10.0.0.10
BASE_URL=me.com
DB_USER=prod
DB_PASSWORD=123456
# Mail
MAIL_CONNECTION=foo
MAIL_USER=tim
#DEV_PW=123











 
BASE_URL=me.com 

# Database

DB_HOST=10.0.0.10
DB_USER=prod
DB_PASSWORD=123456

# Mail

MAIL_CONNECTION=foo

# Additional

MAIL_USER=tim

# Unset

#DEV_PW=123

Roadmap

Testing

All versions of laravel-env-normalizer with dependencies

PHP Build Version
Package Version
Requires php Version ^8.0
illuminate/database Version >=5.4
illuminate/support Version >=5.4
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 romanzipp/laravel-env-normalizer contains the following files

Loading the files please wait ....