Open JulienHe opened 5 years ago
.env
contain API credentials and should not be commited to Git or in CI. You should use environment variables in TravisCI to set the values of .env. You can create a bash script in TravisCI that chooses which environment variable to use based on the branch.
Problem
Having the possibility to deploy to multiple environment based on the branch. I want to deploy to a specific Slate theme when I use a different branch, automatically.
Replication steps
Create a skeleton slate theme with 2 .env - production and staging and make the build verified by travis.
Travis will come with this error :
Error: ENOENT: no such file or directory, open '/home/travis/build/ultrasupernew/Gugusleep-shop/shop/.env.staging'
More Information
If you have any hint that will be awesome!