- How do I install mrgswift/laravel-encryptenv in a Laravel app?
- Install the package with Composer using the mrgswift/laravel-encryptenv package name, then follow the repository README for any service provider or configuration publishing steps. For version 1.1.0, confirm your app is on Laravel 11 and PHP 8.2+ before adopting it. Run your application tests after installation to catch integration issues early.
- Does mrgswift/laravel-encryptenv support Laravel 11?
- Yes, the 1.1.0 release updates composer.json constraints to support Laravel 11. The release note describes a dependency and compatibility update rather than new product capabilities or API changes. Verify the package in a disposable Laravel 11 app and confirm its CI matrix covers the Laravel 11 minor versions you use.
- Which Laravel versions can I use with this package?
- Version 1.1.0 is specifically described as adding Laravel 11 compatibility. The provided release information does not confirm whether Laravel 10 or earlier remains supported in the same release or whether 1.1.0 is a hard upgrade boundary. Check the package composer.json and README before upgrading or downgrading.
- How does encrypting .env values work in Laravel with this package?
- The package encrypts and decrypts values in your .env file or a custom config file, helping keep API keys, passwords, and other secrets out of plain text. It is designed to preserve a familiar environment configuration workflow rather than replacing it with a separate secrets system. Review the README for the exact commands, key management, and decryption workflow.
- Can I encrypt a custom config file instead of .env?
- Yes, the package overview says it can encrypt your .env file or a custom config file in Laravel. Confirm the supported file paths and configuration options in the README before relying on this for production secrets. Test encryption and decryption in a non-production environment first.
- What should I check before using version 1.1.0 in production?
- Treat 1.1.0 as a Composer-level compatibility release for Laravel 11 and validate it in a branch before production. Confirm PHP 8.2+ and Composer constraints, refresh the lockfile, run application tests, and check any package-specific config, migrations, routes, and scheduled jobs. Deploy to staging first and keep a rollback plan.
- Does version 1.1.0 require PHP 8.2 and Composer 2?
- Laravel 11 requires PHP 8.2+, so a Laravel 11 application using this package must run on PHP 8.2 or newer. The release note only mentions composer.json constraint updates, so verify the exact PHP and Composer requirements in the package composer.json. Do not assume older PHP runtimes are supported.
- Is mrgswift/laravel-encryptenv tested against Laravel 11 in CI?
- The provided evaluation does not confirm whether the package CI matrix covers Laravel 11 or which Laravel 11 minor versions are tested. The 1.1.0 release note describes dependency and compatibility updates but does not mention test matrix changes. Check the repository CI configuration and run the package tests in a disposable Laravel 11 app.
- What alternatives exist for encrypting Laravel .env secrets?
- Alternatives include Laravel's built-in env encryption commands, cloud secret managers such as AWS Secrets Manager or HashiCorp Vault, and CI/CD secret injection. This package's differentiator is keeping an .env-style workflow while encrypting values. Compare operational complexity, key management, and deployment workflow before choosing.
- Is mrgswift/laravel-encryptenv actively maintained?
- The 1.1.0 Laravel 11 compatibility release is a positive maintenance signal because it tracks a current framework version. One dependency release does not establish a predictable release cadence or long-term support commitment. Review release history, open issues, security advisories, and the maintainer support policy before standardizing on it.