Posts

๐Ÿณ Docker Diaries: Your First Container — Step by Step

Docker Diaries: Your First Container — Let's familiar with docker Hello again, friends! ๐Ÿ‘‹ In the last blog, we explored the magical world of containers. ๐Ÿงณ Now it's time to get our hands a little dirty and actually build our very first container using Docker! ๐Ÿšข Whether you're a student, a developer, or just curious, this blog is your simple, no-jargon guide to Docker and container creation. First Things First: What is Docker? Let’s quickly recap: Docker is a platform that helps you build, run, and manage containers. Imagine Docker as a kitchen where you prepare your app (like a meal), pack it (in a box = container), and deliver it anywhere — whether it’s your laptop, server, or the cloud. ๐Ÿฑ ๐Ÿ› ️ Step 1: Install Docker Before you start, you need Docker installed on your system. ๐Ÿ‘‰ For Windows or Mac: Visit: https://www.docker.com/products/docker-desktop Download Docker Desktop and follow the installation steps. ๐Ÿ‘‰ For Linux (Ubuntu): bash sudo apt update ...

While Building a Real-Time Game: Why a Single Stable Port Matters More Than You Think

 When we started developing our real-time multiplayer Rock-Paper-Scissors game with hand gesture recognition, one of the early issues we faced was port switching. It seemed harmless at first—our development environment would simply switch from port 3000 to 3001 if one was busy. But in a real-time WebSocket-based game, this caused major problems. This blog dives into why port stability is critical for any real-time game, especially when using WebSockets and gesture recognition , and how we fixed it. Let me explain the port switching situation and clarify why it's happening and why it's actually not desirable for our game: Why Port Switching Was Happening (The Problem): The port switching between 3000 and 3001 wasn't intentional or beneficial It was happening due to two issues: Nodemon's crash handler trying to kill port 3000 Our code attempting to find alternative ports when 3000 was in use Why Multiple Ports Are NOT Good for Our Game: WebSocket connections (Socket.I...

Web Application-Threats and Security

Volume-1 - Web App Concepts - Web App Threats - Web App Hacking Methodology Web App Concepts Web Applications run on a remote application server and are available for clients over the Internet. A web application can be available on different platforms, for example, browsers and software. The use of web applications has increased enormously in the last few years.  They depend on a client-server relationship and provide an interface for clients to use web services. Web pages may be generated on the server or may contain scripts for dynamic execution on the client web browser. Web App Threats Threats to Web Applications include:  Cookie Poisoning   Insecure Storage   Information Leakage   Directory Traversal   Parameter/Form Tampering   DOS Attack  Buffer Overflow   Log Tampering  SQL Injection   Cross-Site (XSS) Cross-Site Request Forgery Security Misconfiguration  Broken Session Management...