From 3d23542979af2445f617925f00f50842e746f6d6 Mon Sep 17 00:00:00 2001
From: Victor Login <batazor111@gmail.com>
Date: Mon, 18 May 2020 17:29:23 +0300
Subject: [PATCH] Update README.md

Close #8
---
 README.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/README.md b/README.md
index 51282a1..6e5d1fb 100644
--- a/README.md
+++ b/README.md
@@ -40,6 +40,16 @@ export AWS_ACCESS_ID=YOURACCESSIDGOESHERE
 export AWS_SECRET_ACCESS_ID=YOURSECRETKEYGOESHERE
 ```
 
+Local path support for `.env` files:
+
+```ruby
+Vagrant.configure("2") do |config|
+  config.env.enable # enable the plugin
+  config.env.load 'my/path/.env' # custom path
+  config.vm.box = ENV['BOX_NAME']
+end
+```
+
 ### Should I commit my .env file?
 
 It is recommended that you store development-only settings in your .env file, and commit it to your repository. Make sure that all your credentials for your development environment are different from your other deployments. This makes it easy for other developers to get started on your project, without compromising your credentials for other environments.