Working with errors and stack traces in your development environment is fairly simple. You probably have a console window open and are looking at the errors as they happen. You read the stack trace, look at the code that failed and fix the bug, because you're working with the application right now.
But what happens when you have errors in production? How do you get notified of these errors? How do you stay on top of problems that your users are experiencing so that you can get them fixed before the user even knows that a problem occurred?
Deploying a production application is more than just a script to handle pushing files to a server. It involves details like environment configuration and error tracking, so that you can be proactive in your debugging and fixing of issues.
In this episode, then, you'll see how to configure Raygun.io – my personal choice for tracking errors in production – for both your development environment, and your production environment.
And better yet – as a WatchMeCode subscriber, you have access to a massive discount with Raygun! So get ready to see how easy it is to track errors in production, and save significant amounts of money while doing it!