Brad Parbs

Any <code>WPENV_</code> prefixed variables in the <code>.env</code> will be used to override the WordPress options. For example, if you’d like to set a specific environment to “Discourage search engines from indexing this site”, you can add <code>WPENV_BLOG_PUBLIC=0</code> to your <code>.env</code> file.
<ul>
<li>
Any option in the <code>wp_options</code> table or retrieved by <code>get_option()</code> can be set this way.
</li>
<li>
You can define keys either as <code>WPENV_BLOGDESCRIPTION</code> or as <code>WPENV_blogdescription</code>, both will work.
</li>
<li>
If you’d like to define the location of your <code>.env</code> file, rather than the plugin looking for it, you can filter <code>dotenv_location</code> to be a directory path.
</li>
<li>
You can also change the <code>WPENV_</code> prefix by filtering <code>dotev_key_prefix</code> to be a different prefix.
</li>
</ul>

dotenv

A WordPress plugin to set WordPress options from a .env file.

Developer Debug Tools vs dotenv