{"id":36985838,"url":"https://github.com/mrgswift/laravel-encryptenv","last_synced_at":"2026-01-13T23:03:44.373Z","repository":{"id":38855031,"uuid":"223476375","full_name":"mrgswift/laravel-encryptenv","owner":"mrgswift","description":"Encrypt your .env (or custom config file) in Laravel","archived":false,"fork":false,"pushed_at":"2024-11-23T20:11:08.000Z","size":53,"stargazers_count":43,"open_issues_count":1,"forks_count":27,"subscribers_count":1,"default_branch":"master","last_synced_at":"2025-08-20T20:03:43.191Z","etag":null,"topics":["configuration","configuration-files","encrypt-files","encryption","environment-variables","laravel","security"],"latest_commit_sha":null,"homepage":null,"language":"PHP","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/mrgswift.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null}},"created_at":"2019-11-22T19:54:35.000Z","updated_at":"2025-08-06T05:22:15.000Z","dependencies_parsed_at":"2022-07-12T17:39:32.172Z","dependency_job_id":null,"html_url":"https://github.com/mrgswift/laravel-encryptenv","commit_stats":{"total_commits":26,"total_committers":6,"mean_commits":4.333333333333333,"dds":0.3076923076923077,"last_synced_commit":"372a8332a09a3a196a187a584925059d6373fe9f"},"previous_names":[],"tags_count":10,"template":false,"template_full_name":null,"purl":"pkg:github/mrgswift/laravel-encryptenv","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mrgswift%2Flaravel-encryptenv","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mrgswift%2Flaravel-encryptenv/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mrgswift%2Flaravel-encryptenv/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mrgswift%2Flaravel-encryptenv/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/mrgswift","download_url":"https://codeload.github.com/mrgswift/laravel-encryptenv/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/mrgswift%2Flaravel-encryptenv/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28403763,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-13T21:51:37.118Z","status":"ssl_error","status_checked_at":"2026-01-13T21:45:14.585Z","response_time":56,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.5:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["configuration","configuration-files","encrypt-files","encryption","environment-variables","laravel","security"],"created_at":"2026-01-13T23:03:43.707Z","updated_at":"2026-01-13T23:03:44.366Z","avatar_url":"https://github.com/mrgswift.png","language":"PHP","funding_links":[],"categories":[],"sub_categories":[],"readme":"# laravel-encryptenv\n\n[![GitHub license](https://img.shields.io/badge/License-MIT-green.svg)](https://github.com/mrgswift/laravel-encryptenv/blob/master/LICENSE)\n\nThis package allows you to encrypt your environment variables in your .env file OR in a custom config file.\n\nThis is accomplished through the added helper function `secEnv()` to replace `env()` when using\nan encrypted value in your configuration file. \n\nAlso included is a console command to encrypt \nthe values of all flagged .env or config file variables/keys, and a console command to run other console commands (scheduled tasks, artisan commands, etc) that require the decrypted environment variables to run.\n\nSome setup/configuration is required to get everything working correctly.\n\n## Table of Contents\n\n- [Install](#install)\n- [Documentation](#documentation)\n\n## Install\n\n###### Since some components in this package are needed early on in composer's autoload execution, installation steps must be done in this order (below).  If you don't follow this order, composer may throw an error and things will break.\n\n#### Use composer to install the package\n```console\n$ composer require mrgswift/laravel-encryptenv\n```\n#\n#### Add package provider EncryptEnvServiceProvider to providers in `config/app.php` (`bootstrap/providers.php` in Laravel 11)\n```php\n'providers' =\u003e [\n    ...\n    mrgswift\\EncryptEnv\\Provider\\EncryptEnvServiceProvider::class\n],\n```\n#\n#### Publish necessary package assets (e.g. config file, console command, helper file)\n\n```console\n$ php artisan vendor:publish --provider=\"mrgswift\\EncryptEnv\\Provider\\EncryptEnvServiceProvider\"\n```\nThis publishes the following files:\n```\napp/Helpers/secEnv.php\nconfig/encryptenv.php\napp/Console/Commands/EncryptEnvValues.php\napp/Console/Commands/SecEnvConsoleCommand.php\n```\n\n#\n#### Add the new Helper file `app/Helpers/secEnv.php` to the files property in the autoload block of your `composer.json` file\n```\n    \"autoload\": {\n        ...\n        \"files\": [\"app/Helpers/secEnv.php\"]\n    },\n```\nClear out and re-generate your autoload files, otherwise the new files entry you added to `composer.json` will not be seen by composer\n```console\n$ composer dump-autoload\n```\n#\n#### Add the new console commands to the commands array in `app/Console/Kernel.php` (Not necessary in Laravel 11)\n```php\n\n    /**\n     * The Artisan commands provided by your application.\n     *\n     * @var array\n     */\n    protected $commands = [\n        ...\n        'App\\Console\\Commands\\EncryptEnvValues',\n        'App\\Console\\Commands\\SecEnvConsoleCommand'\n    ];\n```\n#\n#### Update `config/encryptenv.php` with desired settings\n\nRequired Settings in `config/encryptenv.php`\n\n****cipher (default: AES-128-CBC)****\n```php\n    /*\n    |--------------------------------------------------------------------------\n    | Encryption Cipher\n    |--------------------------------------------------------------------------\n    |\n    | This package uses Laravel's built-in Encryption API\n    | Laravel Encrypter supports either AES-128-CBC or AES-256-CBC as a cipher.\n    |\n    | If you are concerned about the performance and scalability of your\n    | application, AES-128-CBC should be more then sufficient to protect your\n    | environment variables.  If you are more paranoid, you can use AES-256-CBC\n    |\n    | More on this here:\n    | https://blog.1password.com/guess-why-were-moving-to-256-bit-aes-keys/\n    |\n    | Change 'cipher' below to AES-128-CBC OR AES-256-CBC to encrypt your environment\n    | variables in your .env or custom config file (set custom config below)\n    |\n    */\n\n    'cipher' =\u003e 'AES-128-CBC',\n```\n\n****encrypt_flag (default: !ENC:)**** \n```php\n    /*\n    |--------------------------------------------------------------------------\n    | Encrypt Value Flag\n    |--------------------------------------------------------------------------\n    |\n    | This will tell the EncryptEnv console command what flag to look for at the\n    | beginning of each environment variable value, to trigger encrypting the value.\n    |\n    | For best results, use a string that has little probability of being inside of\n    | an actual variable value. Though this package does only check the beginning of\n    | each variable value, it is still possible to mistakenly choose an encrypt_flag\n    | that is contained at the beginning of an actual variable value. If you make\n    | this mistake, this package will partially encrypt the variable value causing\n    | unexpected results and most likely making the variable unreadable\n    |\n    | The default included encrypt_flag should suffice for most setups\n    |\n    | NOTE:  This cannot be 'ENC:' but you can put anything else here\n    |\n    */\n\n    'encrypt_flag' =\u003e '!ENC:',\n```\n#\nOther Settings in `config/encryptenv.php` \n\n****custom_config_file**** \n```php\n    /*\n    |--------------------------------------------------------------------------\n    | Custom Config File\n    |--------------------------------------------------------------------------\n    |\n    | Set this if you would rather use your own config file and not docroot/.env\n    | Otherwise leave this blank.  Any custom config file must be located in\n    | the laravel's default config path, which is docroot/config for most Laravel\n    | environments. Laravel has the helper function config_path() to return this\n    | path if you are unsure what this path is.\n    |\n    | NOTE: If you set this, your .env file will be completely ignored by this\n    | package\n    }\n    */\n\n    'custom_config_file' =\u003e '',\n```\n****custom_config_output (default: env)**** \n```php\n    /*\n    |--------------------------------------------------------------------------\n    | Custom Config File Output Format\n    |--------------------------------------------------------------------------\n    |\n    | This is only applied if custom_config_file (above) is set to a non-blank\n    | value/filename. Valid output formats are 'env' OR 'array'.  Setting to\n    | 'env' outputs variables in valid .env file syntax, while 'array' outputs\n    | an array usable by Laravel's Config helper class\n    |\n    */\n\n    'custom_config_output' =\u003e 'env'\n```\n#\n#### Configure your web service (apache/nginx) to pass your CONFIGKEY (encryption key) to PHP\n\nThis package requires that the environment variable CONFIGKEY be passed by your web service to your \nLaravel application.  Your CONFIGKEY is either 16 characters (for AES-128-CBC cipher) or 32 characters long \n(for AES-256-CBC cipher)\n\nFor best security practices, this should be set up as a conditional pass based on what script is making the request. \nIdeally this should only be `public/index.php`.  By limiting the passing of CONFIGKEY to only index.php, it limits the \nability of non-privileged users to retrieve the CONFIGKEY and your encrypted config values. This otherwise could be \naccomplished by simply creating a new console command or php script that can be accessed remotely.  You should also make \nindex.php read-only to non-privileged users.  These measures are obviously not full-proof, but it most likely will buy \nyou more time to mitigate a disaster in the event your server is hacked or a malicious user attempts to retrieve the \nCONFIGKEY or one of your config file values.\n\nYour web service configuration files (nginx.conf, /etc/nginx/sites-available/*, httpd.conf, etc) should only be readable \nby the root user, otherwise your CONFIGKEY can be retrieved by a non-privileged shell user by simply opening the config file. Most apache and nginx setups run their parent process as root, so there should not be an issue of \nthe configuration files being readable by apache/nginx.\n\nAn example configuration for nginx and apache are below.  Configuration of nginx and apache are beyond the scope \nof this README.  For help with nginx or apache, or for more information refer to:\n\n[Apache Documentation Website](http://httpd.apache.org/docs/)\n\n[Nginx Documentation Website](https://docs.nginx.com/nginx/admin-guide/)\n\n****Apache Configuration Example****\n\nVirtualHost block example with example CONFIGKEY\n```\n\u003cVirtualHost *:80\u003e\n    DocumentRoot \"/path/to/laravel/docroot\"\n    ServerName yourlaravelapp.tld\n    \u003cIf \"%{SCRIPT_FILENAME} == '/path/to/laravel/docroot/public/index.php'\"\u003e\n       SetEnv CONFIGKEY \"51TMszQEvpAlVxbe\"\n    \u003c/If\u003e\n    ...\n\u003c/VirtualHost\u003e\n```\n\n****Nginx Configuration Example (using php-fpm)****\n\nPHP location block example with example CONFIGKEY\n\n```\n    location ~ \\.php$ {\n        set $script_filename $document_root$fastcgi_script_name;\n        set $configkey \"\";\n        if ($script_filename = \"/path/to/laravel/docroot/public/index.php\") {\n          set $configkey \"51TMszQEvpAlVxbe\";\n        }\n        try_files $uri /index.php =404;\n        fastcgi_split_path_info ^(.+\\.php)(/.+)$;\n        ...\n        fastcgi_param SCRIPT_FILENAME $script_filename;\n        fastcgi_param CONFIGKEY $configkey;\n        include fastcgi_params;\n    }\n\n```\n\nThe two examples above will pass CONFIGKEY into PHP's $_SERVER array as $_SERVER['CONFIGKEY'].\n\n****What about IIS?****\n\nRegarding IIS setups.  I have no idea how to do this in IIS, though I suspect it is possible.  If anyone\nknows how to accomplish the same thing with the same level of security in an IIS server environment, feel free to do a pull \nrequest. Thanks!\n\n***The reason for all of this***\n\nDuring execution of this script's decryption sequence, the value of $_SERVER['CONFIGKEY'] is retrieved.  \nIf $_SERVER['CONFIGKEY'] is not empty, the decryption sequence proceeds to decrypt any encrpyted environment\nvariables (or custom config file values).\n\n## Documentation\n\n1. [Preparing for Encryption](#preparing-for-encryption)\n2. [Using the Encryption flag](#using-the-encryption-flag)\n3. [Running the Console Commands](#running-the-console-commands)\n4. [File Permissions](#file-permissions)\n\n\n### Preparing for Encryption\n\n#### 1. Backup your existing environment variables file (.env or otherwise) \n\nTo prepare for encryption you should first backup your existing .env (or custom config) file, as this process will overwrite your file with the\nencrypted values.  By design and for security reasons, it is not convenient to decrypt these values after the fact, as \nthere is no console command to do so, and ideally the CONFIGKEY (encryption key) is not even available for decryption\n\n#### 2. Ready your configuration files by using the secEnv helper function for config values you plan to encrypt\n\nUpdate your Laravel and package-specific config files and change the values of each variable or property that you\nwant to be encrypted to use the secEnv helper function (works exactly like the env() helper function)\n\nUsage: secEnv('name','fallback_value')\n\nExample mail.php config file:\n```php\nreturn [\n    'driver' =\u003e env('MAIL_DRIVER', 'smtp'),\n    'host' =\u003e secEnv('MAIL_HOST', 'smtp.somehost.com'),\n    'port' =\u003e env('MAIL_PORT', 587),\n    'username' =\u003e secEnv('MAIL_USERNAME'),\n    'password' =\u003e secEnv('MAIL_PASSWORD'),\n    ...\n];\n```\nIn the above example, the the use of the secEnv helper function in the host, username, and password values indicates that\nthe secEnv function should be used to retrieve the values of each of these keys, checking if the value in your .env or \ncustom config file should be decrypted.  In the case of 'host', the value of MAIL_HOST in your environment file \nwill be checked for an encrypted value.  If it is encrypted, the value will be decrypted to be readable by Laravel's \nConfig class.  If it cannot find an encrypted value, it will assign the fallback value (smtp.somehost.com in the example).  \nJust like the env() helper function, the fallback value for secEnv is optional.\n\n\n\n#### 3. Be sure the correct custom config file (if any) is defined in `config/encryptenv.php`\n\nBy default this package overwrites your .env file if `custom_config_file` is not defined/blank.  If you don't want\nto use .env to store your environment variables, define a filename for `custom_config_file`. This file must reside in your \nLaravel config path, and the file must contain an array with the keys and values of your configuration (like all other\nLaravel config files).\n\n_**Comments at the top of your custom configuration file**_\n\nIf you use a custom configuration file and wish to preserve a comment block at the top of the file, you must use the\nopening doc block convention /\\** instead of a normal opening comment /*.  \nThis tells the encryption sequence to preserve your comment block at the top of the file.\n\nExample:\n```\n/**\n|--------------------------------------------------------------------------\n| Encrypted Environment Variables\n|--------------------------------------------------------------------------\n|\n| Keep encrypted env variables here.\n| These Environment Variables will be replaced and assigned to readable\n| env values given the correct Config encryption key is provided to\n| the application\n|\n*/\n```\n\n\n### Using the Encryption Flag\n\nEdit the environment variables file you are using and add the encryption flag defined in \n`config/encryptenv.php` as a prefix to each value you want to encrypt\n\nExample .env File with default Encrypt Flag !ENC:\n```\nAPP_ENV=production\nAPP_DEBUG=false\nAPP_KEY=!ENC:65UMszZRvpAPVxba\n\nMYSQL_HOST=db.somehost.net\nMYSQL_USER=!ENC:webapp_mysql\nMYSQL_PASS=!ENC:Secure.P4ssW0rd!\n\nSERVICE_API_KEY=!ENC:qZXFuZWh0NFE9PSIsInZhbHVlIjoidmNpRUV5em\n\n```\n\nIt works the same in a php configuration file that you define for `custom_config_file` in `config/encryptenv.php`\n\n```php\n\u003c?php\nreturn [\n    'APP_ENV' =\u003e 'production',\n    'APP_DEBUG' =\u003e false,\n    'APP_KEY' =\u003e '!ENC:65UMszZRvpAPVxba',\n    'MYSQL_HOST' =\u003e 'db.somehost.net',\n    'MYSQL_USER' =\u003e '!ENC:webapp_mysql',\n    'MYSQL_PASS' =\u003e '!ENC:Secure.P4ssW0rd!',\n    'SERVICE_API_KEY' =\u003e '!ENC:qZXFuZWh0NFE9PSIsInZhbHVlIjoidmNpRUV5em'\n];\n\n```\nIn both examples (above) the values for APP_KEY, MYSQL_USER, MYSQL_PASS, and SERVICE_API_KEY are flagged for encryption\nand will be replaced with the encrypted string when running the console command (below).\n\n### Running the Console Commands\n\n#### Encrypting your environment variables\n\n`php artisan encryptenv:encrypt`\n\nThis command will run the encryption sequence in your environment variables file, execute the artisan console command included with this package\n\nThere is one optional argument `configkey`.  Having the config key as an optional\nargument allows you to add this console command to your own scripts for things like automation in your deployment process.\nIf you do use the configkey argument, it is recommended that you include safeguards to prevent this console command from \nbeing recorded in your shell's history (to protect your Config Key).\n\nMore on protecting your config key here:\nhttps://stackoverflow.com/questions/6475524/how-do-i-prevent-commands-from-showing-up-in-bash-history\n\n##### Generating a new CONFIGKEY (encryption key)\n\nYou will need to generate a new CONFIGKEY if you don't already have one.\n\nIf you put `generate-key` in the optional configkey argument, the encryptenv:encrypt artisan command will automatically\ngenerate a new CONFIGKEY and encrypt the flagged values in your environment variables file.  \n\nUpon completion of the encryption, it will display your new CONFIGKEY (See example below)\n\n```console\n$ php artisan encryptenv:encrypt generate-key\nDone!\n\nYour new generated CONFIGKEY is: UQvq72E7ZFXE2sUvW2QsaXGCEgXav2jK\n\nDO NOT lose this key if you want to use the encrypted config values you just encrypted.\nYou will need to update your web service configuration file with this new CONFIGKEY\nRefer to the Install [Configure your web service] section in the README for more info\n```\n\n##### Running This Command With An Existing CONFIGKEY\n\nIf you already have a CONFIGKEY set up and configured for your web service, simply run the encryptenv:encrypt artisan\ncommand as follows:\n\n_Without the optional configkey argument_\n```console\n$ php artisan encryptenv:encrypt\n```\n\n_With the optional configkey argument_\n```console\n$ php artisan encryptenv:encrypt UQvq72E7ZFXE2sUvW2QsaXGCEgXav2jK\n```\n\nIf you do not provide the configkey argument, you will be prompted for your Config Key,\neither 16 characters or 32 characters long depending on which cipher you defined in `config/encryptenv.php`  \n\nEnter your Config Key into the prompt and press Enter when you are ready to start the encryption sequence\n\nExample with Config Key prompt:\n```console\n Config Key (16 char key):\n \u003e 95UMleZOvpAPVyba\n\nDone!\n```\n\nWhen the command has completed the encryption sequence it will display \"Done!\"\n\nCheck your environment variables file to make sure the values you want encrypted are as you expect.  \n\nYour .env file (or custom config) will look similar to this:\n```php\nAPP_ENV=production\nAPP_DEBUG=false\nAPP_KEY=ENC:eyJpdiI6ImpBMlE0Q1VNK2J3MEdlWU9peSs0TFE9PSIsInZhbHVlIjoiNUpsbDNzVUw2RWpWUE1rXC9xQTliNjltT3hLZWNZS1JqTVNRWGZ6cjBNaUFQc3FrUVJObENWNW1SaTlOaTVKdVUiLCJtYWMaUFQc3FrUVJObENWNWDJhNjZhMmE3NmUyYmJkYjQ3ODMxZmFiNmQ0ZTgxZTkxZDA5N2RhMjk2MGZmYzM5NTY4ZjcyIn0=\n\nMAILCHIMP_API_KEY=ENC:eyJpdiI6IkUzK0c2QmdIMlkwQW56MEtYd3o5ZGc9PSIsInZhbHVlIjoiTWRhZ1gxenZzUENaTFZCcVFJWmZIeTJ6NnpjZitzODVYMjROd2xyR295UTFXNhMWU3Y2xyR295UTFXbWkxZ3YrRnExNyIsIm1hYyI6IjM4N2MxZjM5MjIyMjRlZjAxZjc4xMnZ4TmRIODVYMjROd2xyR295UTFXNhMWU3YzZiZmNmY2JiYTQwNDQ1NmRjOTI4OTEifQ==\n\nMAIL_USERNAME=ENC:eyJpdiMjkzMDkxOTY4MzY5OTUxMmFlMmYSIsInZhbHVlIjoieEo5ZjBzckRORnBQRlFTMDlQRkxlUXpXWjg0ME8zUFZvRHBCekhBXC9rXC9NPSIsIm1hYyI6IjFkZmJlMjQ5OWUxNGI0NWVkMTg4Yzk1ODE2OWU0YTJhZjQzMjkzMDkxOTY4MzY5OTUxMmFlMmY0MmMyZmIzNzMifQ==\nMAIL_PASSWORD=ENC:eyJpdiI6IlU4a2lhMEFqa3hlcWZyQTlyOXd1c2c9PSIsInZhbHVlIjoiVENPRFwvUldBNDRMUzZGeHNvT1lsSlQzcU41bWsyZ25HcW8zdTJYKytkTVU9IiwibWFjIjoiYWY5MGIwMGJjMDk5MTJiNTcxYzQzODIyODZiMjEyOXd1c2c9PSIsInZhbHVlIjoiVENPRFwvU0OTMyMjUyZGVjOWUyNyJ9\n```\n\nIf you set everything up correctly, Laravel should now be working with your encrypted config values.\n\nNote: You should run `php artisan config:clear` to clear your config cache just to be sure everything is truly working.\n\n### Running console commands that require decrypted environment variables\n`php artisan encryptenv:console`\n\nThis command exists to allow you to run console commands that require your environment variables to be decrypted during execution.\n\nFor example `php artisan encryptenv:console 'php artisan migrate'`\n\nThe first required argument `console_command`, must be wrapped in single quotes or regular quotes\n\nThe second optional argument is `configkey`.  This allows you to add console commands that require the CONFIGKEY to deployment scripts or cron jobs.\n\nIf you do not provide the configkey argument, you will be prompted for your Config Key,\neither 16 characters or 32 characters long depending on which cipher you defined in `config/encryptenv.php`  \n\nEnter your Config Key into the prompt and press Enter when you are ready to execute your console command\n\nExample with Config Key prompt:\n```console\n Config Key (16 char key):\n \u003e 95UMleZOvpAPVyba\n```\n\nOnce the Config key is set, the console command you entered into the console_command argument will be executed with decrypted access to your environment variables until execution is completed.\n\nAs noted above, you should do your due diligence to protect your config key from being saved in your shell's history.\n\n\n### File Permissions\n\nYou should make `public/index.php` read-only to non-privileged users. This prevents a malicious user from adding code to\nindex.php in order to retrieve decrypted config values or the decryption key itself (assuming conditional CONFIGKEY pass \nexplained in Install [Configure Your Web Service] section was followed).\n\nYour web service configuration files should only be readable by the root user, otherwise a non-privileged user can read\nthe CONFIGKEY (encryption key) by opening the configuration file in an editor like vim, emacs, nano, or simply using the\ncat command in a shell. \n\nMost apache and nginx setups run their parent process as root, so there should not be an issue of the configuration files\nbeing readable by apache/nginx.\n\n\n## License\n\n[MIT][1]\n\n[1]: https://github.com/mrgswift/laravel-encryptenv/blob/master/LICENSE\n\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmrgswift%2Flaravel-encryptenv","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fmrgswift%2Flaravel-encryptenv","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmrgswift%2Flaravel-encryptenv/lists"}