Keep .env when importing from GitHub?


#1

Hi! I’ve been playing with passing code back and forth between my HyperDev project (coffee-wave) and a GitHub repo (https://github.com/ddemaree/node-blog), and everything works well except that my .env file is completely overwritten on import. I understand why this is (import just replaces everything), but it’d be easier to keep the two code bases in sync if ignored/env specific files like .env could be preserved?


#2

Thanks for reporting the issue ddemaree, you’re totally right that it would be better to keep the .env file on GitHub imports. I’ve just released a fix to address this so that .env files will be kept, let me know if it works for you!