@RudrakshLaddha

Rudraksh Laddha

@RudrakshLaddhaIndiaJoined July 2023

Building Virendana || Consulting from Development to Deployment || DevOps Engineer || Technical Writer || Web Developer ||

Website

About

I'm Rudraksh Laddha — a DevOps engineer and emerging full-stack developer, passionate about building scalable, reliable systems that solve real-world problems. With a solid foundation in cloud infrastructure automation using tools like Kubernetes, Docker, Terraform, and AWS, I thrive in environments where efficiency, resilience, and automation are key. But my journey doesn't stop at infrastructure. I'm actively expanding into full-stack development, building dynamic applications using React, Node.js, and MongoDB. Whether it's designing cloud-native CI/CD pipelines or developing intuitive user interfaces, I enjoy creating end-to-end solutions — from server to screen. Right now, I'm: 🧩 Building full-stack applications that merge DevOps reliability with engaging frontend experiences 🛠️ Contributing to open-source projects, learning through collaboration and real-world scenarios 🚀 Growing Virendana Ui, my own UI library focused on expressive, clean design systems 🚀 Growing Learn Virendana, where I share my personalized learning journey — from beginner to experienced 🎮 Developing side projects like 2048 Rush, blending product thinking with scalable infrastructure My long-term goal? To bridge DevOps and development — building products that are not just functional and fast, but also resilient, beautiful, and ready for scale.

Available for

Building my SaaS project end-to-end — from development to deployment. Open to collaborating on open-source and freelance projects.

Rudraksh Laddha's blogs

Rudraksh.techhashnode.rudrakshladdha.xyz70 posts

About

Available for

Building my SaaS project end-to-end — from development to deployment. Open to collaborating on open-source and freelance projects.

Rudraksh Laddha's blogs

Rudraksh.techhashnode.rudrakshladdha.xyz70 posts

Articles Comments

Comments

At that time, my full project code was not available, and in this article, I provided only a basic introductory example, not a fully tested one. I have a question for you: Did you try running the project step by step first, or did you directly create a Dockerfile? I strongly suggest running the project manually, executing commands one by one, debugging any issues, and then creating and running the container. This will help you identify and resolve errors more effectively. Let me know if you need any help!