laranail/env-kit is not published to Packagist, so there is no registry-version badge to show: see Install.
A view-less Laravel engine for reading and safely editing
.envfiles — one transactional, atomic, guarded, audited commit path behind a programmatic API, a CLI, and an interactive TUI.
PHP ^8.4.1 on Laravel ^13. It is the engine of the EnvKit family; the env-kit-webui companion drives it for the web.
composer require laranail/env-kituse Simtabi\Laranail\EnvKit\Headless\Facades\EnvKit;
EnvKit::set('MAIL_HOST', 'smtp.acme.test'); // atomic · backed-up · audited
$debug = EnvKit::getBool('APP_DEBUG', false); // typed readThe service provider and facade register themselves through package discovery, and EnvKit edits
your application's .env out of the box. Optionally:
- Publish the config to change the defaults (writes
config/laranail/env-kit.php):php artisan vendor:publish --tag=laranail::env-kit-config. - Point it at another file with the
ENV_KIT_PATHvariable. - Verify against the current
.env:php artisan laranail::env-kit.doctor.
use Simtabi\Laranail\EnvKit\Headless\Facades\EnvKit;
EnvKit::set('MAIL_HOST', 'smtp.acme.test'); // atomic, backed up, audited
EnvKit::get('MAIL_HOST'); // "smtp.acme.test"
EnvKit::getBool('APP_DEBUG', false); // true / 1 / yes / on → trueTarget another file per call:
EnvKit::file(base_path('.env.staging'))->set('APP_ENV', 'staging');
EnvKit::on('testing')->get('DB_DATABASE'); // → .env.testing alongside the base fileThe full walkthrough is in Programmatic API; everything else is in the documentation index.
Full documentation is at opensource.simtabi.com/documentation/laranail/env-kit — format-preserving atomic writes, secret redaction + encryption-at-rest, schema validation, the guard/protection policy, the CLI, the interactive TUI, and configuration.
Issues and PRs are welcome — see CONTRIBUTING.md. Report vulnerabilities per SECURITY.md (opensource@simtabi.com); participation follows the Code of Conduct.
MIT © Simtabi LLC. See LICENSE.