markwalet/dotenv-manager

A PHP package that helps you edit the .env file programmatically.

/mɑː(r)k wɔːˈlɛt/

dotenv-manager's Issues

Replace double quotes for single in readme

When double quotes are not necessary, we should not use them in our examples

Add Laravel 6 support

Because Laravel is using semver from now on, the usual composer.json should be updated to support Laravel 6 installations.

The CI configuration should also test if everything still works fine on illuminate version ~6.0.

[V2] Make a separate Laravel package

By removing the Laravel service provider from this package, we can make the package framework agnostic again.

This serviceprovider should be moved to a new repository: markwalet/laravel-dotenv-manager.

Removing support for Laravel is a breaking change. So this would be an update for version 2.0.

Add a Laravel Facade

A Facade will make it easier to mutate the .env file.

Add PHP 8.1 support

Support for Laravel 10

title

Support for Laravel Zero

I got a Laravel Zero application.
I tried to require markwalet/dotenv-manager, but composer dump-autoload reports several warnings like this:

Generating optimized autoload files
Warning: Ambiguous class resolution, "Illuminate\Foundation\Application" was found in both "/Users/...omitted.../vendor/laravel-zero/foundation/src/Illuminate/Foundation/Application.php" and "/Users/...omitted.../vendor/laravel/framework/src/Illuminate/Foundation/Application.php", the first will be used.

Thank you

Include `dragon-code/laravel-migration-actions` in readme

I just found out about the dragon-code/laravel-migration-actions package. I think this would work perfectly with the dotenv manager. We should add an example in the readme to show how to use the dotenv migration pattern in a migration action and recommend the package in our composer.json. Maybe @andrey-helldar could help with that?

Add Laravel 7 support

Refactor the Laravel service provider

We can improve 3 things on our service provider:

• The boot method is not being used. So we can remove it. (Already refactored)
• When we only use the register method on the service provider, we can make it a deferred provider.
• We should test if all injectables get registered correctly to the Laravel application container.