You are not alone if networking feels transactional—even awkward—to you. This puts you in a situation where you know and acknowledge that you should be networking. Yet, you have an equally strong desire to avoid the discomfort of it all. — How can you reconcile these two opposing feelings?
I’ll be in a focused learning mode, and away from content creation for a while. — That means, I’ll come up with even more content when I’m back 🤘.
…it follows that the whole of reality is like an ever-flowing stream, and that nothing is ever at rest for a moment.
How you frame a problem has a direct impact on whether you can solve it. That means, words are more important than one might think they are. When you pick your words carefully when describing your issue, you’ll have a much better chance in solving it.
This series will show how you can rapidly prototype a full-blown production-ready app in under half an hour. Interested? Let’s jump right in.
As a final step, we’ll deploy our application to an AWS EKS Kubernetes cluster and make sure that it’s healthy, up, and running.
We have an app that works locally. Now it’s time to put it into a container and yeet it out to a cluster. And that’s what we’ll do.
We are done with the authentication part. We are almost near the end of our application’s initial implementation. We just need a questions handlers, which, in essence, is a glorified file server with some path traversal protection for an added level of security.
This section will introduce a middleware layer to our project and we’ll write a sample middleware to see it in action.
Having implemented our middlewares, now it’s time to implement the missing OAuth0 callback, login, and logout handlers.