UnknownSec Bypass 403

: /var/www/html/lms_d5c35339adb3/vendor/vlucas/phpdotenv/ [ drwxr-xr-x ]
name : README.md PHP dotenv ========== Loads environment variables from `.env` to `getenv()`, `$_ENV` and `$_SERVER` automagically. This is a PHP version of the original [Ruby dotenv](https://github.com/bkeepers/dotenv). [](http://travis-ci.org/vlucas/phpdotenv) Why .env? --------- **You should never store sensitive credentials in your code**. Storing [configuration in the environment](http://www.12factor.net/config) is one of the tenets of a [twelve-factor app](http://www.12factor.net/). Anything that is likely to change between deployment environments – such as database credentials or credentials for 3rd party services – should be extracted from the code into environment variables. Basically, a `.env` file is an easy way to load custom configuration variables that your application needs without having to modify .htaccess files or Apache/nginx virtual hosts. This means you won't have to edit any files outside the project, and all the environment variables are always set no matter how you run your project - Apache, Nginx, CLI, and even PHP 5.4's built-in webserver. It's WAY easier than all the other ways you know of to set environment variables, and you're going to love it. * NO editing virtual hosts in Apache or Nginx * NO adding `php_value` flags to .htaccess files * EASY portability and sharing of required ENV values * COMPATIBLE with PHP's built-in web server and CLI runner Installation with Composer -------------------------- ```shell curl -s http://getcomposer.org/installer | php php composer.phar require vlucas/phpdotenv ``` Usage ----- The `.env` file is generally kept out of version control since it can contain sensitive API keys and passwords. A separate `.env.example` file is created with all the required environment variables defined except for the sensitive ones, which are either user-supplied for their own development environments or are communicated elsewhere to project collaborators. The project collaborators then independently copy the `.env.example` file to a local `.env` and ensure all the settings are correct for their local environment, filling in the secret keys or providing their own values when necessary. In this usage, the `.env` file should be added to the project's `.gitignore` file so that it will never be committed by collaborators. This usage ensures that no sensitive passwords or API keys will ever be in the version control history so there is less risk of a security breach, and production values will never have to be shared with all project collaborators. Add your application configuration to a `.env` file in the root of your project. **Make sure the `.env` file is added to your `.gitignore` so it is not checked-in the code** ```shell S3_BUCKET=dotenv SECRET_KEY=souper_seekret_key ``` Now create a file named `.env.example` and check this into the project. This should have the ENV variables you need to have set, but the values should either be blank or filled with dummy data. The idea is to let people know what variables are required, but not give them the sensitive production values. ```shell S3_BUCKET=devbucket SECRET_KEY=abc123 ``` You can then load `.env` in your application with a single line: ```php Dotenv::load(__DIR__); ``` All of the defined variables are now accessible with the `getenv` method, and are available in the `$_ENV` and `$_SERVER` super-globals. ```php $s3_bucket = getenv('S3_BUCKET'); $s3_bucket = $_ENV['S3_BUCKET']; $s3_bucket = $_SERVER['S3_BUCKET']; ``` You should also be able to access them using your framework's Request class (if you are using a framework). ```php $s3_bucket = $request->env('S3_BUCKET'); $s3_bucket = $request->getEnv('S3_BUCKET'); $s3_bucket = $request->server->get('S3_BUCKET'); ``` ### Nesting Variables It's possible to nest an environment variable within another, useful to cut down on repetition. This is done by wrapping an existing environment variable in `{$…}` e.g. ```shell BASE_DIR=/var/webroot/project-root CACHE_DIR={$BASE_DIR}/cache TMP_DIR={$BASE_DIR}/tmp ``` ### Immutability By default, Dotenv treats environment variables as immutable, that is… once set they cannot be changed. You can make Dotenv mutable using ```php Dotenv::makeMutable(); ``` … and you can make Dotenv immutable again using ```php Dotenv::makeImmutable(); ``` Requiring Variables to be Set ----------------------------- Using Dotenv, you can require specific ENV vars to be defined, and throw an Exception if they are not. This is particularly useful to let people know any explicit required variables that your app will not work without. You can use a single string: ```php Dotenv::required('DATABASE_DSN'); ``` Or an array of strings: ```php Dotenv::required(array('DB_HOST', 'DB_NAME', 'DB_USER', 'DB_PASS')); ``` If any ENV vars are missing, Dotenv will throw a `RuntimeException` like this: ``` Required environment variable missing or value not allowed: 'DB_USER', 'DB_PASS' ``` ### Allowed values As you may have noticed from the Exception message above, it's also possible to define a set of values that your environment variable should adhere to. ```php Dotenv::required('SESSION_STORE', array('Filesystem', 'Memcached')); ``` Again, if the environment variable wasn't in this list, you'd get a similar Exception: ``` Required environment variable missing or value not allowed: 'SESSION_STORE' ``` ### Comments You can comment your `.env` file using the `#` character. E.g. ```shell # this is a comment VAR="value" # comment VAR=value # comment ``` Usage Notes ----------- When a new developer clones your codebase, they will have an additional **one-time step** to manually copy the `.env.example` file to `.env` and fill-in their own values (or get any sensitive values from a project co-worker). phpdotenv is made for development environments, and generally should not be used in production. In production, the actual environment variables should be set so that there is no overhead of loading the `.env` file on each request. This can be achieved via an automated deployment process with tools like Vagrant, chef, or Puppet, or can be set manually with cloud hosts like Pagodabox and Heroku. Contributing ------------ 1. Fork it 2. Create your feature branch (`git checkout -b my-new-feature`) 3. Make your changes 4. Run the tests, adding new ones for your own code if necessary (`phpunit`) 5. Commit your changes (`git commit -am 'Added some feature'`) 6. Push to the branch (`git push origin my-new-feature`) 7. Create new Pull Request