---env option is not working
See original GitHub issueI can succcessfully set the environment by using the -e
option, but the ---env
option is not working:
example:
$ db-migrate up ---env="myEnv"
[ERROR] Error: Environment(s) 'dev, development' not found.
Issue Analytics
- State:
- Created 9 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
[FIX] System Could not Find Environment Option that was ...
Method 1: Add a New Environment Variable in Safe Mode · Restart your system and press F4 when you see the start-up logo...
Read more >Problems with Environment Variables
To check which environment variables are set, do the following (works for all versions of Windows): Open a DOS box (or a Command...
Read more >pm2 --update-env option seems not working - node.js
So, I just tried pm2 delete 0 , pm2 start ecosystem.config.js then It's working well. Why does --update-env options not working? What do...
Read more >Variable interpolation in options:env: not working #98 - GitHub
Hi, I'm trying to specify environment variables for the whole build instead of for each build step, like so: steps: - id: 'echo_env_vars' ......
Read more >The System Could Not Find The Environment Option That Was ...
Fixed -The System Could Not Find The Environment Option That Was Entered.This is a very irritating issue that arises when the Environment ......
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 FreeTop 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
Top GitHub Comments
Doh!. If you look closer at the error i posted, I had used 3 dashes instead of two. User error.
I’ll get some more specifics on this and get back to you.