Simplify Production Debugging with ngrok: Live Demo and Traffic Policies Explained
- Date
- Runtime
- 10:24
- Share
About this video
What You'll Learn
- Route production requests to a local machine with ngrok for live debugging.
- Use traffic policies to steer specific traffic without changing your deployed code.
- Reproduce real production failures against your dev environment and inspect them directly.
In this video, learn how to effectively use ngrok to debug and troubleshoot your applications in production. We'll explore a practical use case where production traffic is routed to a local machine for debugging using ngrok traffic policies.
Transcript
Generated from English captions. Select a timestamp to jump to that moment.
Read and search the transcript
0:00 You know the situation. You run your application locally in dev mode. You hit refresh. Your application works. But then you push it to production, and oh no. What is going on? In this video, we're going to take a look at a pretty cool feature and use case for ngrok that will help you get rid of this situation, or at least make debugging it a whole lot simpler. Let's have some fun. Now, even though I know that you know that you have 100% test coverage across unit tests, integration tests, acceptance 00:00:00: 00:00:00: integration tests, 00: unit tests, 00: <i.e tests, 00: 00: #1, you have a lot of your application 00: you have a lot of your application 00: <strongly 00: 00: <i.evaluations tests, 00: <font-size tests, 00: <i.e 00: <unkown
0:45 tests, smoke tests, chaos tests, performance and synthetics. 00:00: 100%20: #louisv tests, smoke tests, canary tests, chaos tests, performance and 00:00:46.495 --> 00:00:
Technologies featured
Comments
More about ngrok
Academy publications by email
Get an email when Rawkode Academy publishes new tutorials, articles, and videos.
Loading email signup. If it does not load, manage email preferences in account settings.