You can add a comment in . env by starting a line with a hash (#) symbol. E.g. Lines started from # detected as comments.
env file. As you said, the only way to comment is at line level with the # character. A workaround would be looking for a shortcut in your IDE to employ multi-line editing (e.g. use Shift + Alt + Arrow Keys on Visual Studio Code in Linux).
You use hash commenting:
# Test Settings
ACCESS_KEY=qwsdr
ACCESS_TOKEN=Bgcvfsx
# Live Settings
ACCESS_KEY=985AsdefG
ACCCESS_TOKEN=LFP994kL
Documentation: https://github.com/vlucas/phpdotenv#comments
Please note that as of Laravel 5.8 comment parsing in values has changed.
In Laravel 5.7 an .env file containing ENV_VALUE=foo#bar
would evaluate to foo#bar
.
In Laravel 5.8 the same .env file would evaluate to foo
instead, with #bar
being seen as a comment.
To use the #
character in a value, double quote the entire value like so ENV_VALUE="foo#bar"
.
Laravel use the vlucas/phpdotenv
package to parse .env
file.
So according to the doc, you can comment like this:
# Test Settings
ACCESS_KEY=qwsdr
ACCESS_TOKEN=Bgcvfsx
# Live Settings
ACCESS_KEY=985AsdefG
ACCCESS_TOKEN=LFP994kL
Since Laravel 5.8, you can do something like this:
ENV_VALUE1=foo#bar
ENV_VALUE2="foo#bar"
will return:
env('ENV_VALUE1'); // foo
env('ENV_VALUE2'); // foo#bar
The phpdotenv package that is used to parse
.env
files has released a new major version, which may impact the results returned from theenv
helper. Specifically, the#
character in an unquoted value will now be considered a comment instead of part of the value:
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With