Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add support for .env.dist files
See original GitHub issueAlso support .env.dist for ENV variables. eg see https://github.com/symfony/flex/blob/master/src/Flex.php#L177
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
node.js - How to put .env and other filed in dist folder while ...
To resolve this issue, I need to copy my all the configuration/static files (here, . env file) into ./dist folder at the time...
Read more >Support for a build / distribution .env file (eg. env.build) #39524
Would it be an good idea to add support to the dotenv for and extra env file that can be packed within the...
Read more >How to customize Node.js .env files for different environment ...
Custom env is a library built to make development easier by allowing multiple .env configuration for different environments. This is done by ...
Read more >We need to talk about the .env | Platform.sh
An application that supports .env files will, on boot, run through each line in that file and read key=value pairs. For each, it...
Read more >How To Use Environment Files with env-cmd | DigitalOcean
Learn how to add handle environment variables with the env-cmd package.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
As I see all these kind of files usually copied to .env (Laravel has .env.example file). And usually both of this file with similar content are in project. This makes Go to declaration feature unconvenient - user should every time choose between .env and .env.dist file declaration. I’ll try to avoid these issues in future… maybe. But currently I’ll support only .env files.
~It seems that having both stops the wildcard working.~
Apologies, I had at some point added the others to
textfiles, individually, without the wildcard