Level 51
use .env.production and .env.local to have 2 different env set of variables.
https://laravel.com/docs/9.x/configuration#additional-environment-files
Aug 19, 2022
13
Level 10
Custom .env variable for npm run production
Hi All, I am currently switching my images from hosting them on my project server to digital ocean spaces. I have everything working great using flysystem-aws-s3-v3 but I am now looking into the best way to have a testing and a production image server. When I switched to spaces I had to update my Vue project to use a custom url instead of my public folder. I did this using the .env mix. in my .env file:
MIX_IMAGE_URL=https://DEV.sfo3.digitaloceanspaces.com/public/
The issue is vue compiles locally so while laravel will use the production .env, vue will be using my local .env. Is there a way that I can say when running npm run prod it uses a different location? Like in my .env file
if('production')
{
MIX_IMAGE_URL=https://DEV.sfo3.digitaloceanspaces.com/public/
} else {
MIX_IMAGE_URL=https://PROD.sfo3.digitaloceanspaces.com/public/
}
Level 10
@mohamedtammam Thanks for this. I understand the idea but I am struggling to understand how to implement it.
Level 51
@chrisgrim In your project use two .env files. one named .env.local and other named .env.production When you compile use assets using MIX. if you run npm run dev MIX is going to use the variables in your .env.local. When you build for production and run npm run prod MIX will use the variables in your .env.production.
Level 10
@MohamedTammam I thought that is how it would work but if I just have an .env.local and an .env.production when I go to my site I get the error
No application encryption key has been specified. {"exception":"[object] (Illuminate\Encryption\MissingAppKeyException(code: 0): No application encryption key has been specified. at /
In order to get my app to run I have to rename .env.local back to just .env.
Level 10
I should also note if I have a .env and a .env.local and .env.production when I run npm run dev or npm run prod it still uses my .env instead of the other two.
Level 51
In your production you need you to have only one .env
Level 10
@MohamedTammam I get that but I am generating my production js file locally.
Level 51
@chrisgrim Your production js files doesn't related to .env in production. .env should be used for back-end only in that case.
Level 10
@MohamedTammam in my .env file I use
MIX_IMAGE_URL=https://DEV.sfo3.digitaloceanspaces.com/public/
which is cool because when I run npm dev it grabs that url and puts it into my js. However I need to have it so when I am running npm run prod it uses a different url
MIX_IMAGE_URL=https://PROD.sfo3.digitaloceanspaces.com/public/
since I have two servers holding images, my DEV and my PROD.
Level 51
@chrisgrim In your .env.local add
MIX_IMAGE_URL=https://DEV.sfo3.digitaloceanspaces.com/public/
In your .env.prod add
MIX_IMAGE_URL=https://PROD.sfo3.digitaloceanspaces.com/public/
Level 10
I have done that. So I only have a .env.local and a .env.production in my local project folder. However when I try to access the app it errors out because laravel needs a .env file.
So I added the .env back so now I have a .env, .env.local and .env.production in my project folder. However if I run npm run production it uses my .env file instead of my .env.production file
Level 51
@chrisgrim Before you run npm run prod change APP_ENV in your .env to be production
Level 10
@MohamedTammam I tried doing that just now and still using the .env mix file. :(
Please or to participate in this conversation.