By Jonni Lundy | March 29, 2017

3 Reasons Why You Should Use Environment Variables

There are some really big things coming down the pipe with our Beta release right around the corner, but we just couldn't wait to tell you about something we are really excited about: Environment Variables.

Environments have been around for a while, mainly hiding in the deep code forests, so we wanted to highlight them and share that we wrote some fresh documentation so you can start using them right away!

Adding environment variables

Here are a couple easy ways they can improve your app!

🚀 Change Hosting serve directory

By default, WeDeploy Hosting looks to your service's root directory to know what files to serve, but what if you are using a Gulp or Grunt build task to compile your files? No problem, just add the WEDEPLOY_WEB_PATH key and use the build path as your value.

See the full list at our Hosting Environment Variable Docs.

🔐 Integrate OAuth into your app

Want your users to log in with Facebook, Google, or Github accounts? Perfect, because that is super easy to do with WeDeploy Auth. Start by just adding a few environment variables for each provider.

See the full list at our Auth Environment Variable Docs.

📧 Change Email provider

WeDeploy Email supplies you with an email service straight out of the box, but what if you want to use your own SMTP server? With Environment Variables, you can change the email host, username, port, and much more.

See the full list at our Email Environment Variable Docs.

That's it! If you have any question, just shoot us an email or join the conversation on Slack.

Happy coding! 💻

We