Monday Monday Monday open wide dev fans get ready to stuff your face with javascript CSS node module barbecue tips get work flows break dancing soft skills web development the hastiest the

Carrazius the tastiest web development treats coming in hot. Here is West

Barracuda boss and Scott L. Toro Lungo to Linsky

Welcome to syntax in this Monday hasty treat. We're going to be talking all about our environment variables. These are the variables that you use that are often kept as secrets or maybe they're just some

that variable information that sticks along with the different aspects of how your application is running different environments. So to say my name is

Scott Linsky. I'm a full stack developer from Denver Colorado and with me as always West boss. The variable master they call me in high school variable master variable master

disaster getting it faster. Blaster. Okay. Oh, that's good. Yeah. Oh, yeah. Okay. This episode is sponsored by two of our favorite sponsors over here at

syntax and that is Sanity and century. Do you want to dig in a little deep on Sanity and I'll take century West. Yes, Sanity.io is the

structured content CMS. They always check change of tagline. I love it on their homepage. You can tell they're constantly tweaking the marketing as

well as the actual product. See the magic. Yeah, the magic is build beyond your expectation. Sanity is the ultimate content platform that helps

teams dream big and deliver quickly. They've got Nike and fig figma is running on Sanity. That's pretty cool.

November, Condé Nass cloud flare. Basically what it is. It's a CMS. You configure it in your code. So what your CMS is can be kept in

Git. And then you deploy this thing and you can either host yourself or you Sanity to host it. The backend. This thing is called Sanity Studio.

And it's entire backend written in React. And if you want to you can make your own inputs and make your own customization. So it's kind of the best of both worlds because it's a hosted service. It comes with all this amazing stuff out of the box where you can have

custom workflows and custom inputs and everything you could imagine. But then if you if you really want to you can make your own inputs and make your own workflows and and whatnot. So like there's really is the best of both worlds. So check it out. Sanity.io.

Slash syntax. It's going to get you double the free usage tier and tweet us what you're making with Sanity. We've had a couple of people do that lately. And it's kind of cool to see what people have built on it.

Sick. This episode is also sponsored by sentry and that's at sentry.io. Now sentry is the perfect place to track all of your errors and exceptions. We love sentry over here at level up tutorials and syntax. That's what I use it on my platform level up tutorials. And I absolutely could not exist without sentry.

Sentry is the tool that allows me to push with confidence when I know that if there is a major issue going on in the site. I'm going to notice it very quickly because all of my errors and exceptions are logged cataloged organized and even displayed in terms of the frequency and when they last hits. And if it was a regression and get hub issue attached to it and all sorts of amazing stuff that you want out of an error and exception handling service.

It also tracks performance metrics as well, which is something that we definitely love in use using the latest you can see exactly how fast all of your routes on your entire page are loading because as your users are hitting your site. It's sending some of that information to sentry. It's almost like analytics for performance. It's fantastic. Love it. Love it. Love it. So head on over to sentry.io. Use the coupon code tasty treat all over case all one word. And you're going to get two months for free of that sweet, sweet sentry error and exception handling service. Cool. So.

So ENV variables ENV variables are one thing that can be a giant PIA and you've been doing a little bit of a deep dive and digging in here. So I'm interested to talk to you about some of your strategies and some of your ideas here, because we recently redone how we're doing all of our environment variables ourselves. And it's a world. Let's just say that. Yeah. Totally. So what are environment variables, variables are variables that are.

Set on the machine that is running your code. And they are often things that are secret. So these are variables that cannot go in your code, because they are sensitive in nature. And or they change depending on the environment in which they're running. And so things like API keys IDs for OAuth database URLs, where your database is hosted, node environment, all these things are variables that are based on that.

So what are different environments? Well, you have like development when you're running it locally on your machine. You probably want to connect to some sort of test database. And then you push that thing up and you make a pull request and then you build a preview of that. Maybe that's like a staging environment that you might have a couple different variables for that. And then when you go to production, there's a whole new set of of environmental variables. So these are values that are set on your

...