PHPackages                             cranux/laravel-dotenv-editor - 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. [Utility &amp; Helpers](/categories/utility)
4. /
5. cranux/laravel-dotenv-editor

ActiveLibrary[Utility &amp; Helpers](/categories/utility)

cranux/laravel-dotenv-editor
============================

A package for editing the .env file in your Laravel root.

1.0.3(6y ago)34181MITPHPPHP &gt;=7.2.0

Since Jan 30Pushed 6y ago1 watchersCompare

[ Source](https://github.com/cranux/laravel-dotenv-editor)[ Packagist](https://packagist.org/packages/cranux/laravel-dotenv-editor)[ RSS](/packages/cranux-laravel-dotenv-editor/feed)WikiDiscussions master Synced 3w ago

READMEChangelogDependenciesVersions (5)Used By (1)

由于使用laravel6.x不兼容 所以此项目由 [Brotzka/laravel-dotenv-editor](https://github.com/Brotzka/laravel-dotenv-editor) 修改并完善功能,在此感谢原项目作者

Edit your Laravel .env file
===========================

[](#edit-your-laravel-env-file)

This package offers you the possibility to edit your .env dynamically through a controller or model.

The current version (2.x) ships with a graphical user interface based on VueJS to offer you a very simple implementation of all features.

List of available functions:

- check, if a given key exists
- get the value of a key
- get the complete content of your .env
- get the content as JSON
- change existing values
- add new key-value-pairs
- delete existing key-value-pairs
- create/restore/delete backups
- list all backups
- get the content of a backup
- enable auto-backups
- check, if auto-backups are enabled or not
- get and set a backup-path

Here are some images showing the gui which ships with the current version:

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

[](#installation)

### Via composer require

[](#via-composer-require)

Install the package via the composer require command:

```
composer require cranux/laravel-dotenv-editor

```

### Add the package manually

[](#add-the-package-manually)

Add the following line to your composer.json require section:

```
"require": {
    //other packages
    "cranux/laravel-dotenv-editor": "^1.0"
}

```

Then run the composer update command:

```
composer update

```

### After Installation

[](#after-installation)

Add the following line to your `config/app.php` providers:

```
Cranux\DotenvEditor\DotenvEditorServiceProvider::class,

```

Add the following line to your `config/app.php` aliases:

```
'DotenvEditor' => Cranux\DotenvEditor\DotenvEditorFacade::class,

```

Finally you have to publish the config file and view via:

```
php artisan vendor:publish --provider="Cranux\DotenvEditor\DotenvEditorServiceProvider"

```

After an Update, maybe you have to force publish:

```
php artisan vendor:publish --provider="Cranux\DotenvEditor\DotenvEditorServiceProvider" --force

```

Be careful, this will overwrite all your published files! It's always better to delete the `config/dotenveditor.php`file manually and then run the `php artisan vendor:publish` command than to run the force version.

Now you can edit the config file and put in your values.

Config
------

[](#config)

Open the config/dotenveditor.php and fill it up with your values.

**Note:** I had an issue where I had to switch the web-middleware between `middleware` and `middlewareGroups`. In Laravel 5.2, put the web-middleware in the `middleware` array. For Laravel 5.1 put it in the `middlewareGroups` array.

The path to your .env should not be changed.

Deactivate GUI
--------------

[](#deactivate-gui)

If you don't want to use the graphical interface, you could deactivate it in the config.

Additional middleware
---------------------

[](#additional-middleware)

If you want to add more middlewares to the used routes, you could put them in the arrays.

Examples
--------

[](#examples)

The following example shows an controller with a method, in which we change some values from the .env. Make sure, the entries you want to change, really exist in your .env.

```
namespace App\Http\Controllers;

use Cranux\DotenvEditor\DotenvEditor;
use Cranux\DotenvEditor\DotenvEditorFacade;

class EnvController extends Controller
{
    public function test(){
        $env = new DotenvEditor();

        $env->changeEnv([
            'TEST_ENTRY1'   => 'one_new_value',
            'TEST_ENTRY2'   => $anotherValue,
        ]);
        // 使用门面
        DotenvEditorFacade::changeEnv([
            'TEST_ENTRY1'   => 'one_new_value',
            'TEST_ENTRY2'   => $anotherValue,
        ]);
    }
}

```

For more exmaples visit the Wiki.

感谢 [Brotzka/laravel-dotenv-editor](https://github.com/Brotzka/laravel-dotenv-editor)

###  Health Score

28

—

LowBetter than 52% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity16

Limited adoption so far

Community9

Small or concentrated contributor base

Maturity55

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~0 days

Total

4

Last Release

2339d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/f317881aab201b808c1f70c0de2f75cd88ef8131470b3c5d08e6b2a5a2dfe1e1?d=identicon)[wangke568](/maintainers/wangke568)

---

Top Contributors

[![cranux](https://avatars.githubusercontent.com/u/37317831?v=4)](https://github.com/cranux "cranux (4 commits)")

---

Tags

laraveldotenvdotenv-editor

### Embed Badge

![Health badge](/badges/cranux-laravel-dotenv-editor/health.svg)

```
[![Health](https://phpackages.com/badges/cranux-laravel-dotenv-editor/health.svg)](https://phpackages.com/packages/cranux-laravel-dotenv-editor)
```

###  Alternatives

[jackiedo/dotenv-editor

The .env file editor tool for Laravel 5.8+

2031.2M32](/packages/jackiedo-dotenv-editor)[brotzka/laravel-dotenv-editor

A package for editing the .env file in your Laravel root.

370162.0k4](/packages/brotzka-laravel-dotenv-editor)[sixlive/dotenv-editor

A tool to edit phpdotenv files

741.6M12](/packages/sixlive-dotenv-editor)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
