Would this work with Environment variables outside .env? about laravel-env-sync HOT 2 CLOSED

Hi,

The point of the package is just to check that your .env file is in sync with the .env.example and does not provide any kind of validation regarding the fact that a variable exists. It just operate a file content comparison (kinda).

I feel like it's out of scope of this package right now, but i'm glad to read more about it if you disagree!

from laravel-env-sync.

Thanks for the quick reply!

Having the ability to ensure that the ENV variable is present as a check for a deployment pipeline would be fantastic for verifying safe deployments.

But I understand not wanting to increase the package beyond its scope. Perhaps I'll just have to steal it for my own open source package!
I wouldn't want to add to the complexity of the package unnecessarily for a feature which needn't be here.

If it seems like it could benefit this package I'll swing back round and add a pull request here.
Thanks for this package though! Looking forward to including it in my development flow 👍

from laravel-env-sync.