<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rajumanoj on Medium]]></title>
        <description><![CDATA[Stories by Rajumanoj on Medium]]></description>
        <link>https://medium.com/@rajumanoj?source=rss-441a1de114d9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qmvO67QhdKpZHxDNP3OrCQ.jpeg</url>
            <title>Stories by Rajumanoj on Medium</title>
            <link>https://medium.com/@rajumanoj?source=rss-441a1de114d9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:35:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rajumanoj/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Jenkins for Absolute Beginners: From Zero to Your First CI/CD Pipeline]]></title>
            <link>https://medium.com/@rajumanoj/jenkins-for-absolute-beginners-from-zero-to-your-first-ci-cd-pipeline-ea93b1eb2500?source=rss-441a1de114d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea93b1eb2500</guid>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[jenkins-pipeline]]></category>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[pipeline]]></category>
            <category><![CDATA[jenkinsfile]]></category>
            <dc:creator><![CDATA[Rajumanoj]]></dc:creator>
            <pubDate>Fri, 12 Jun 2026 17:51:52 GMT</pubDate>
            <atom:updated>2026-06-12T17:51:52.197Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A hands-on guide no prior CI/CD experience needed. By the end, you’ll have Jenkins running on your own machine and a real pipeline turning green.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0KQ5aLnBdYeyyTI1s3QJCw.png" /><figcaption>Jenkins</figcaption></figure><p><strong>The Problem Jenkins Solves (Why Should You Care?)</strong></p><p>Picture this: you write some code, it works on your laptop, you push it to GitHub, and… your teammate pulls it and everything breaks. Sound familiar?</p><p>Or maybe this: every Friday, someone on your team spends three hours manually building the app, running tests, zipping files, and uploading them to a server. One missed step and the release is broken.</p><p>This is the problem <strong>Continuous Integration and Continuous Delivery (CI/CD)</strong></p><p>solves:</p><ul><li><strong>Continuous Integration (CI):</strong> Every time anyone pushes code, a machine automatically builds it and runs the tests. Broken code gets caught in minutes, not days.</li><li><strong>Continuous Delivery (CD):</strong>Once the code passes all checks, it’s automatically packaged and shipped — to a test server, a staging environment, or even production.</li></ul><p><strong>Jenkins is the machine that does all of this for you.</strong>It’s an open-source automation server that watches your code, builds it, tests it, and deploys it on a schedule, on every push, or on demand.</p><p>Jenkins has been around since 2011 (and before that as “Hudson” since 2005). It’s free, runs anywhere Java runs, and has a plugin ecosystem of over 1,800 plugins. It is still one of the most widely deployed CI/CD tools in the world, which means the skills you learn here show up in real job descriptions every single day.</p><p><strong>How Jenkins Works (The 5-Minute Mental Model)</strong></p><p>Before we touch anything, let’s build a mental model. Jenkins has four core concepts:</p><p><strong>1. The Controller (the brain)</strong></p><p>Think of the <strong>Controller </strong>as Jenkins’ brain. It decides what work needs to be done and keeps track of all builds. It stores your configuration, schedules work, and shows you the results. When you open `http://localhost:8080`, you’re looking at the controller.</p><p><strong>2. Jobs and Pipelines (the work)</strong></p><p>A <strong>job</strong> is a unit of work “build my app”, “run my tests”, “deploy to staging”. The modern way to define a job is a <strong>Pipeline</strong>: a script (written in a file called a `Jenkinsfile`) that describes every step of your build as code. Pipeline-as-code means your build process lives in version control right next to your application code.</p><p><strong>3. Stages and Steps (the structure)</strong></p><p>A pipeline is divided into <strong>stages</strong> (Build → Test → Deploy), and each stage contains <strong>steps**</strong> (the actual commands, like `npm install` or `mvn test`). Stages give you that satisfying visual progress bar in the Jenkins UI.</p><p><strong>4. Agents (the muscle)</strong></p><p><strong>Agents</strong> are the machines that actually execute your pipeline. In a small setup (like ours today), the controller runs the builds itself. In real companies, a single controller farms work out to dozens of agents — Linux boxes, Windows machines, Docker containers, Kubernetes pods.</p><p>The flow looks like this:</p><pre> You push code  ──▶  Jenkins notices  ──▶  Pipeline runs on an agent<br>                                                      │<br>        ┌─────────────┬───────────────┬───────────────┘<br>        ▼             ▼               ▼<br>     Build         Test            Deploy<br>        └─────────────┴───────────────┘<br>                      │<br>                      ▼<br>        ✅ Green build (or ❌ red build + instant feedback)</pre><p>That’s it. That’s the whole idea. Everything else is detail.</p><p>If Jenkins were a restaurant:</p><ul><li>Controller = Manager</li><li>Pipeline = Recipe</li><li>Stages = Cooking steps</li><li>Agent = Chef</li></ul><p>The manager gives the recipe to a chef, who follows each step until the meal is ready.</p><h3><strong>What You’ll Need</strong></h3><p>Just two things:</p><p>1. <strong>Java 17 or 21 (LTS).</strong>Jenkins runs on the Java Virtual Machine. Check what you have:</p><pre>java -version</pre><p>You want to see something like `java version “21.0.9”`. If you don’t have Java, grab it from <a href="https://www.oracle.com/java/technologies/javase/jdk21-archive-downloads.html">https://www.oracle.com/java/technologies/javase/jdk21-archive-downloads.html</a></p><p>2. <strong>The Jenkins WAR file.</strong> This is the entire Jenkins application packed into a single ~97 MB file. Download `jenkins.war` from <a href="https://www.jenkins.io/download/">https://www.jenkins.io/download/</a>.</p><p>The <strong>LTS (Long-Term Support)</strong> version is the right choice for beginners — it’s the stable, battle-tested line.</p><p>That’s the entire installation. No installer wizards, no database setup, no configuration files. One Java runtime, one file.</p><p>&gt; <strong>Note:</strong> Jenkins also offers native installers (Windows `.msi`, macOS, Linux packages) and an official Docker image. They’re all fine. We’re using the WAR file because it’s the most transparent way to learn you can see exactly what’s happening.</p><p><strong>Step 1: Start Jenkins (One Command)</strong></p><p>Open a terminal in the folder where you downloaded `jenkins.war` and run:</p><pre>java -jar jenkins.war --httpPort=8080</pre><p>A wall of log output will scroll by. Jenkins is unpacking itself, creating its home directory, and starting its web server. After 30–60 seconds, look for this line:</p><pre>```<br>Jenkins is fully up and running<br>```</pre><p>But before that line, something <em>*very important*</em> scrolls past — a block that looks like this:</p><pre>```<br>*************************************************************<br>Jenkins initial setup is required. An admin user has been created<br>and a password generated.<br>Please use the following password to proceed to installation:<br>a1b2c3d4e5f64789abcdef0123456789<br>This may also be found at: C:\Users\you\.jenkins\secrets\initialAdminPassword<br>*************************************************************<br>```</pre><p><strong>Copy that password.</strong> It’s a one-time unlock code. (If you missed it, no panic it’s saved in the file path shown, inside the `.jenkins` folder in your home directory.)</p><p>&gt; <strong>What just happened?</strong> Jenkins created a folder called `.jenkins` in your home directory (this is `JENKINS_HOME`). Every job, plugin, and setting lives there. Delete that folder and you get a factory-fresh Jenkins. Back it up and you can restore your entire CI setup.</p><p><strong>Step 2: Unlock and Set Up (The Setup Wizard)</strong></p><p>Open your browser and go to: <a href="http://localhost:8080/">http://localhost:8080</a></p><p>You’ll see the <strong>Unlock Jenkins</strong> screen. Paste the password from Step 1 and click <strong>Continue</strong>.</p><p>Next, Jenkins asks how you want to install plugins:</p><ul><li><strong>Install suggested plugins</strong> ← click this one.</li><li>~~Select plugins to install~~ (skip — you can always add more later)</li></ul><p>The suggested set includes everything we need today: the Pipeline plugin, Git integration, folder organization, and more. Installation takes a few minutes — grab a coffee and watch the progress bars.</p><p>When plugins finish, Jenkins asks you to <strong>create your first admin user**</strong>. Fill it in (and remember the password — this replaces the unlock code). Confirm the Jenkins URL as `http://localhost:8080/` and click <strong>Start using Jenkins</strong></p><p>Welcome to the Jenkins dashboard. It’s empty. Let’s fix that.</p><p><strong>Step 3: Your First Pipeline</strong></p><p>We’re going to create a pipeline the modern way: by writing a `Jenkinsfile`-style script. To keep this tutorial machine-independent, we’ll write the pipeline directly in the Jenkins UI first (you’ll move it into your Git repo at the end I’ll show you how).</p><ol><li>On the dashboard, click <strong>+ New Item</strong> (top-left).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*PHFX0SUA5q5w6adlZV1SQA.png" /><figcaption>New Item Butt</figcaption></figure><p>2. Name it `my-first-pipeline`.</p><p>3. Select <strong>Pipeline </strong>and click <strong>OK</strong>.</p><p>4. Scroll down to the <strong>Pipeline</strong> section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jlDhS58Pd6K_fv4luDiwjw.png" /><figcaption>Pipeline section</figcaption></figure><p>5. Paste this into the <strong>Script </strong>box:</p><p>groovy</p><pre>pipeline {<br>    agent any<br><br>    stages {<br>        stage(&#39;Build&#39;) {<br>            steps {<br>                echo &#39;Compiling the application...&#39;<br>                // In a real project: sh &#39;mvn package&#39; or bat &#39;npm run build&#39;<br>            }<br>        }<br><br>        stage(&#39;Test&#39;) {<br>            steps {<br>                echo &#39;Running the test suite...&#39;<br>                // In a real project: sh &#39;mvn test&#39; or bat &#39;npm test&#39;<br>            }<br>        }<br><br>        stage(&#39;Deploy&#39;) {<br>            steps {<br>                echo &#39;Deploying to the staging server...&#39;<br>                // In a real project: copy artifacts, restart services, etc.<br>            }<br>        }<br>    }<br><br>    post {<br>        success {<br>            echo &#39;Pipeline finished — everything is green! 🎉&#39;<br>        }<br>        failure {<br>            echo &#39;Pipeline failed — check the logs above.&#39;<br>        }<br>    }<br>}</pre><p>6. Click <strong>Save</strong>, then click <strong>▶ Build Now</strong> in the left sidebar.</p><p>Within seconds you’ll see build <strong>#1 </strong>appear, and the <strong>Stage View </strong>will show three green columns: Build → Test → Deploy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g5wOEZlbl8IfwBIzbG960g.png" /><figcaption><strong>Stage View</strong></figcaption></figure><p><strong>Congratulations ! you just ran your first CI/CD pipeline.</strong></p><p>Click on the build number, then <strong>Console Output </strong>, to see exactly what Jenkins did, line by line. This console is where you’ll live when things go wrong, so get familiar with it now while everything is green.</p><h3>Understanding What You Just Wrote</h3><p>Think of a Jenkins Pipeline like a to-do list that Jenkins follows automatically. The pipeline {} block is the container that holds the entire list of instructions. The agent any line tells Jenkins, &quot;You can run these instructions on any available machine.&quot; Inside the stages {} section, we divide the work into different steps, just like breaking a school project into tasks such as planning, building, and checking. Each stage() represents one of these tasks and helps us see the progress clearly in Jenkins.</p><p>Inside every stage, the steps {} block contains the actual actions Jenkins needs to perform. In simple examples, echo is used to print a message on the screen, similar to Jenkins saying, &quot;I&#39;m working on this task now.&quot; In real projects, these steps might compile code, run tests, or deploy an application. After all the stages are finished, the post {} section tells Jenkins what to do next, such as showing a success message, reporting a failure, or cleaning up temporary files. Although you may find older Jenkins examples using node {}, beginners should focus on the modern Declarative Pipeline format with pipeline {} because it is easier to read, understand, and maintain.</p><p><strong>Step 4: Make It Fail (On Purpose)</strong></p><p>A CI tool’s real job is to catch failures, so let’s see one. Edit your pipeline (job page → <strong>Configure</strong>) and change the Test stage to:</p><pre>stage(&#39;Test&#39;) {<br>    steps {<br>        echo &#39;Running the test suite...&#39;<br>        error &#39;Oops — 3 tests failed!&#39;<br>    }<br>}</pre><p>Save and <strong>Build Now</strong> again.</p><p>Build <strong>#2</strong> goes red. The Stage View shows Build in green, Test in red, and Deploy was <em>never executed</em> Jenkins stopped the moment a stage failed. Your `post { failure }` block printed the failure message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/978/1*ad7MiGTiemlj57oYjhMRtw.png" /><figcaption>Build <strong>#2</strong></figcaption></figure><p>This is the entire value proposition of CI in one screenshot: <strong>*bad code gets stopped before it reaches deployment, automatically, every time.</strong></p><p>Now change it back, build again, and enjoy build #3 going green.</p><p><strong>Where the Real Power Is: Pipeline as Code</strong></p><p>Typing scripts into a web form is fine for learning, but real teams keep the pipeline in a file named `Jenkinsfile` at the root of their Git repository:</p><pre>my-project/<br>├── src/<br>├── tests/<br>├── Jenkinsfile ← your pipeline lives here, version-controlled<br>└── README.md<br></pre><p>To switch your job over: <strong>Configure</strong>→ Pipeline section → change <strong>Definition**</strong> from “Pipeline script” to <strong>”Pipeline script from SCM”</strong> → pick Git, paste your repository URL, and set the script path to `Jenkinsfile`.</p><p>From then on, Jenkins pulls the pipeline from your repo on every run. Change the build process? That’s a code-reviewed pull request, not a config change someone forgot to document. This is why “pipeline as code” became the industry standard.</p><p>Pair it with a <strong>webhook</strong> (GitHub → Settings → Webhooks → point it at your Jenkins URL) and the loop closes completely: every `git push` triggers a build within seconds, with zero manual clicks.</p><p><strong>Where to Go From Here</strong></p><p>You now have the foundation. Here’s the natural learning path, in order:</p><p>1. <strong>Connect a real repository.</strong> Take any project you have, add a `Jenkinsfile`, and make the stages run your actual build and test commands (`sh ‘npm test’`, `bat ‘mvn verify’`, etc.).</p><p>2. <strong>Triggers.</strong>Explore “Build Triggers”webhooks for instant builds, or `pollSCM`/`cron` schedules for nightly jobs.</p><p>3. <strong>Credentials.</strong> Jenkins has a built-in encrypted store (Manage Jenkins → Credentials) so your pipelines can use API keys and passwords without ever hardcoding them.</p><p>4. <strong>Agents.</strong> Move builds off the controller and onto dedicated agent machines or Docker containers — this is how Jenkins scales to thousands of builds a day.</p><p>5. <strong>Blue Ocean / Pipeline visualization plugins</strong> for a prettier pipeline UI.</p><p>6. <strong>Shared Libraries </strong>once you have five pipelines that look alike, you’ll want to factor out the common parts.</p><p>And bookmark these:</p><ul><li>Official docs: <a href="https://www.jenkins.io/doc/">jenkins.io/doc</a></li><li>Pipeline syntax reference: <a href="https://www.jenkins.io/doc/book/pipeline/syntax/">jenkins.io/doc/book/pipeline/syntax</a></li><li>The built-in <strong>Pipeline Syntax</strong> generator (linked from every pipeline job’s sidebar) it writes step code for you.</li></ul><p>— -</p><p><strong>Wrapping Up</strong></p><p>In one sitting, you went from “what is Jenkins?” to:</p><ul><li>Understanding the CI/CD problem and Jenkins’ mental model (controller, pipelines, stages, agents)</li><li>Running Jenkins from a single WAR file with one command</li><li>Completing the setup wizard and creating an admin user</li><li>Writing, running, breaking, and fixing a real three-stage Declarative Pipeline</li><li>Knowing the path from UI scripts to version-controlled `Jenkinsfile`s</li></ul><p>The dirty secret of CI/CD is that this <em>is</em> the core of it. Everything else Docker agents, Kubernetes, multi-branch pipelines, deployment strategies is layered on top of exactly what you built today.</p><p>You now know enough Jenkins to automate a real project. Start small, experiment often, and don’t be afraid to break things that’s how everyone learns Jenkins.</p><p><em>If this helped you, a clap or two helps other beginners find it. Questions? Drop them in the comments I read all of them.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea93b1eb2500" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[18 Agentic CLIs You Need to Know]]></title>
            <link>https://medium.com/@rajumanoj/18-agentic-clis-you-need-to-know-87ab6d2aa07f?source=rss-441a1de114d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/87ab6d2aa07f</guid>
            <category><![CDATA[github-copilot]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[gemini]]></category>
            <dc:creator><![CDATA[Rajumanoj]]></dc:creator>
            <pubDate>Mon, 08 Dec 2025 09:55:56 GMT</pubDate>
            <atom:updated>2025-12-08T09:55:56.233Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UHQ5dL38adZ1G4SKwNcVcQ.png" /></figure><h3>The New Frontier of Software Development: A Deep Look at 18 Agentic CLIs Transforming the Terminal</h3><p>For decades, the command line has been the quiet engine room of software development. It is where developers troubleshoot systems, automate workflows, and shape the foundations of codebases. Despite the rise of graphical tools, the terminal has persisted as the most powerful and efficient environment for engineering work.</p><p>Today, it is undergoing a major transformation.</p><p>A new generation of <strong>agentic CLIs</strong> — command-line tools powered by large language models — are reshaping how developers think, write, and maintain code. These tools bring natural language reasoning, repository understanding, and autonomous workflows directly into the terminal. The result is a development experience that is faster, clearer, and more adaptable than ever before.</p><p>This article explores eighteen of the most influential agentic CLIs available today. Each one showcases how AI is becoming a trusted partner rather than just another utility.</p><h3>1. Gemini CLI</h3><p><strong>Website:</strong> <a href="https://github.com/google-gemini/gemini-cli">https://github.com/google-gemini/gemini-cli</a><br> Google’s Gemini CLI brings the reasoning capabilities of the Gemini model directly into the terminal. Developers can generate code, analyse files, and run tasks using everyday language.</p><p><strong>Install</strong></p><pre>npm install -g @google/gemini-cli</pre><h3>2. Qwen CLI</h3><p><strong>Website:</strong> <a href="https://github.com/QwenLM/qwen-code">https://github.com/QwenLM/qwen-code</a><br> Alibaba’s Qwen CLI provides access to the Qwen models with simple commands. It is known for efficient reasoning and strong multilingual capabilities.</p><p><strong>Install</strong></p><pre>npm install -g @qwen-code/qwen-code@latest<br>qwen --version</pre><h3>3. Augment CLI</h3><p><strong>Website:</strong> <a href="https://augmentcode.com/">https://augmentcode.com</a><br> Augment focuses on large-scale development tasks. It assists with code upgrades, automated refactoring, and generating complete pull requests.</p><p><strong>Install</strong></p><pre>npm install -g augment-cli</pre><h3>4. Codebuff CLI</h3><p><strong>Website:</strong> <a href="https://codebuff.ai/">https://codebuff.ai</a><br> Codebuff provides file-level and project-level reasoning to help developers generate, review, and modify code directly from the terminal.</p><p><strong>Install</strong></p><pre>npm install -g codebuff</pre><h3>5. OpenCode CLI</h3><p><strong>Website:</strong> <a href="https://opencode.run/">https://opencode.run</a><br> OpenCode is an open-source agent that navigates repositories, proposes structural changes, and applies patches with model-driven clarity.</p><p><strong>Install</strong></p><pre>curl -fsSL https://opencode.ai/install | bash</pre><h3>6. Cline</h3><p><strong>Website:</strong> <a href="https://cline.dev/">https://cline.dev</a><br> Cline has become popular for its accurate diff-based editing. It works well with Claude and OpenAI models while staying grounded in the current file structure.</p><p><strong>Install</strong></p><pre>npm install -g cline</pre><h3>7. GitHub Copilot CLI</h3><p><strong>Website:</strong> <a href="https://github.com/features/copilot">https://github.com/features/copilot</a><br> GitHub Copilot extends its AI assistance to the terminal, helping developers draft shell commands, debug issues, and understand configuration files.</p><p><strong>Install</strong></p><pre>npm install -g @githubnext/github-copilot-cli<br>github-copilot-cli auth</pre><h3>8. ClaudeCode CLI</h3><p><strong>Website:</strong> <a href="https://claudecode.ai/">https://claudecode.ai</a><br> Designed around Anthropic’s Claude models, ClaudeCode offers clear reasoning and is particularly effective for repository exploration and code refactoring.</p><p><strong>Install</strong></p><pre>irm https://claude.ai/install.ps1 | iex</pre><h3>9. Codex CLI</h3><p><strong>Website:</strong> <a href="https://openai.com/">https://openai.com</a><br> Codex was one of the first AI models to meaningfully improve programming workflows. The CLI provides basic generation and assistance for code tasks.</p><p><strong>Install</strong></p><pre>npm install -g @openai/codex</pre><h3>10. Kiro CLI</h3><p><strong>Website:</strong> <a href="https://kiro.ai/">https://kiro.ai</a><br> Kiro focuses on smart code improvements. It provides insight-based suggestions and applies modifications that fit naturally into existing codebases.</p><p><strong>Install</strong></p><pre>curl -fsSL https://cli.kiro.dev/install | bash</pre><h3>11. Amazon Q Developer CLI</h3><p><strong>Website:</strong> <a href="https://github.com/aws/amazon-q-developer-cli">https://github.com/aws/amazon-q-developer-cli</a> ,<br><a href="https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/what-is.html">https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/what-is.html</a></p><p>Amazon Q helps developers write AWS applications faster. The CLI connects cloud workflows, code suggestions, and architectural guidance.</p><p><strong>Install</strong></p><pre>pip install amazon-q-developer</pre><h3>12. Kilocode CLI</h3><p><strong>Website:</strong> <a href="https://kilocode.com/">https://kilocode.com</a><br> Kilocode brings multi-agent collaboration to the terminal. It is effective for debugging, writing tests, and performing multi-step code updates.</p><p><strong>Install</strong></p><pre>npm install -g kilocode</pre><h3>13. Aider</h3><p><strong>Website:</strong> <a href="https://aider.chat/">https://aider.chat</a><br> Aider is one of the most lightweight and reliable AI coding agents. It uses a precise diff-based approach, making it suitable for serious workflows and production code.</p><p><strong>Install</strong></p><pre>pip install aider</pre><h3>14. Cursor CLI</h3><p><strong>Website:</strong> <a href="https://cursor.sh/">https://cursor.sh</a><br> The Cursor CLI extends the Cursor IDE’s intelligence directly to the terminal. It helps developers run larger refactors and automate tasks without opening the editor.</p><p><strong>Install</strong></p><pre>curl -fsSL https://cursor.sh/install | bash</pre><h3>15. OpenSpec CLI</h3><p><strong>Website:</strong> <a href="https://openspec.dev/">https://openspec.dev</a><br> OpenSpec converts complex codebases into readable documentation and technical specifications. It is especially useful for onboarding and compliance.</p><p><strong>Install</strong></p><pre>npm install -g openspec</pre><h3>16. Agentuity CLI</h3><p><strong>Website:</strong> <a href="https://agentuity.com/">https://agentuity.com</a><br> Agentuity automates documentation, PR reviews, dependency updates, and various maintenance tasks. It acts as a long-term internal code steward.</p><p><strong>Install</strong></p><pre>curl -fsS https://agentuity.sh | sh</pre><h3>17. Rovo Dev CLI (Atlassian)</h3><p><strong>Website:</strong> <a href="https://www.atlassian.com/rovo">https://www.atlassian.com/rovo</a><br> Rovo Dev brings Atlassian’s AI assistant into the terminal. It integrates with Jira, Confluence, and Bitbucket, helping developers understand tasks and connect code to project context.</p><p><strong>Install</strong></p><pre>npm install -g rovo-dev<br>rovo login</pre><h3>18. Qoder CLI</h3><p><strong>Website:</strong> <a href="https://qoder.ai/">https://qoder.ai</a><br> Qoder is a command-line agent that helps generate code, run workflows, and understand project structures using natural language commands.</p><p><strong>Install</strong></p><pre>curl -fsSL https://qoder.com/install | bash</pre><h3>A Changing Landscape</h3><p>As these tools mature, the terminal is evolving into a more collaborative environment. Instead of isolated commands, developers can now describe what they want in natural language, and an intelligent agent interprets, executes, and refines the work.</p><p>This shift restores the simplicity of early computing where commands were clear and direct while offering the advanced reasoning of modern AI models. The result is not just faster development but a new relationship between developers and their tools.</p><p>Agentic CLIs represent a major step toward a future where coding feels more conversational, more intuitive, and more focused on solving problems rather than managing complexity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87ab6d2aa07f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Full Stack Development Roadmap: Java and Python Paths]]></title>
            <link>https://medium.com/@rajumanoj/full-stack-development-roadmap-java-and-python-paths-071c0a8da176?source=rss-441a1de114d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/071c0a8da176</guid>
            <category><![CDATA[full-stack]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[roadmaps]]></category>
            <dc:creator><![CDATA[Rajumanoj]]></dc:creator>
            <pubDate>Sun, 01 Jun 2025 17:36:50 GMT</pubDate>
            <atom:updated>2025-06-01T17:36:50.739Z</atom:updated>
            <content:encoded><![CDATA[<p>Code your future: <strong>Java</strong> or <strong>Python</strong>. Your stack, your rules</p><h3>Introduction</h3><p>This comprehensive roadmap guides beginners through becoming full stack developers using either Java or Python for backend development. The guide includes all essential technologies, tools, and resources needed to build complete web applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EYtBGPp7hhPQCCUvRCZzOw.png" /></figure><h3>Development Environment Setup</h3><p><strong>Essential Tools:</strong></p><ul><li>Code Editor: <a href="https://vscode.dev/">Visual Studio Code</a></li><li>Java IDE: <a href="https://spring.io/tools">Spring Tool Suite (STS)</a></li><li>Database Tool: <a href="https://dev.mysql.com/downloads/workbench/">MySQL Workbench</a></li><li>Container Registry: <a href="https://hub.docker.com/">Docker Hub</a></li><li>CI/CD Platform: <a href="https://www.jenkins.io/">Jenkins</a></li><li>Cloud Platform: <a href="https://aws.amazon.com/free/">AWS Free Tier</a></li></ul><h3>Phase 1: Foundation Skills</h3><h3>Programming Fundamentals</h3><ul><li><strong>Java Basics</strong>: Variables, control flow, OOP principles</li><li>Practice: <a href="https://codingbat.com/">CodingBat Java</a></li><li>Focus: Classes, inheritance, interfaces, collections</li><li><strong>Python Basics</strong>: Syntax, data structures, functions</li><li>Practice: <a href="https://codingbat.com/">CodingBat Python</a></li><li>Focus: Lists, dictionaries, functions, modules</li></ul><h3>Web Development Essentials</h3><p><strong>HTML5</strong>: Document structure, semantic elements, forms</p><ul><li>Practice: <a href="https://coddy.tech/">Coddy Tech</a></li></ul><p><strong>CSS3</strong>: Selectors, box model, layouts, responsive design</p><ul><li>Practice: <a href="https://coddy.tech/">Coddy Tech</a></li></ul><p><strong>JavaScript</strong>: DOM manipulation, events, asynchronous programming</p><ul><li>Practice: <a href="https://coddy.tech/">Coddy Tech</a></li><li>Key concepts: Promises, fetch API, ES6 features</li></ul><h3>Version Control</h3><p><strong>Git &amp; GitHub</strong>: Basic workflow, branching, collaboration</p><ul><li>Interactive tutorial: <a href="https://learngitbranching.js.org/">Learn Git Branching</a></li><li>Video course: <a href="https://youtu.be/zTjRZNkhiEU?si=eM8ZfISVIW5Bz86v">Learn Git — Full Course for Beginners</a></li><li>Reference guide: <a href="https://medium.com/@rajumanoj/git-and-github-6f36a21f4b0f">Git and GitHub Explained</a></li></ul><h3>Database Fundamentals</h3><p><strong>SQL &amp; MySQL</strong>: Tables, queries, relationships</p><ul><li>Interactive tutorial: <a href="https://sqlbolt.com/">SQLBolt</a></li><li>Video course: <a href="https://youtu.be/hlGoQC332VM?si=A2bSrl4A2TYZ4RQ9">SQL — Complete Course in 3 Hours</a></li></ul><h3>Phase 2: Frontend Development</h3><h3>Frontend Framework Options</h3><h3>Option 1: Angular</h3><p><strong>Angular Fundamentals</strong>: Components, services, directives</p><ul><li>Video tutorial: <a href="https://youtu.be/k5E2AVpwsko?si=ypB9-FQpDNQJwWDA">Angular Tutorial for Beginners</a></li><li>Setup guide: <a href="https://v17.angular.io/guide/setup-local">Angular Setup</a></li><li>Reference notes: <a href="https://angularnotes.hashnode.dev/angular-notes">Angular Notes</a></li></ul><p><strong>Overview</strong>: Learn to build single-page applications with TypeScript</p><p><strong>Prerequisites</strong>: Basic HTML, CSS, JavaScript knowledge</p><p><strong>Topics covered</strong>: Components, templates, data binding, services, routing, forms</p><h3>Option 2: React.js</h3><p><strong>React Fundamentals</strong>: Components, props, state, hooks</p><ul><li>Project-based learning: <a href="https://github.com/practical-tutorials/project-based-learning">Practical Tutorials GitHub</a></li><li>Key concepts: JSX, component lifecycle, React hooks, context API</li></ul><h3>Advanced Frontend Topics</h3><ul><li>State management</li><li>Routing and navigation</li><li>Form handling and validation</li><li>API integration</li><li>Testing strategies</li></ul><h3>Phase 3: Backend Development</h3><h3>Java Backend Path</h3><h3>Spring Ecosystem</h3><p><strong>Spring Framework</strong>: Core concepts, dependency injection</p><ul><li>Video tutorial: <a href="https://youtu.be/-Fe0zk-F4OA?si=v1QdpT_BC53XuR7a">Spring Framework and Spring Boot Tutorial</a></li><li>Official documentation: <a href="https://spring.io/projects/spring-boot">Spring Boot</a></li><li>Key concepts:</li><li>Inversion of Control (IoC)</li><li>Aspect-Oriented Programming (AOP)</li><li>Spring MVC architecture</li></ul><p><strong>Spring Boot</strong>: Auto-configuration, starters, REST APIs</p><ul><li>Key features:</li><li>Embedded servers</li><li>Spring Boot Actuator</li><li>Application properties</li><li>Profiles and configuration</li></ul><p><strong>Maven</strong>: Project structure, dependency management</p><ul><li>Build lifecycle</li><li>POM file configuration</li><li>Dependency resolution</li></ul><h3>Advanced Java Backend Topics</h3><ul><li>Spring Data JPA for database operations</li><li>Spring Security for authentication and authorization</li><li>Testing Spring applications</li><li>Microservices with Spring Cloud</li><li>Video tutorial: <a href="https://youtu.be/yn_stY3HCr8?si=tz1HxX__f1SITkCD">Spring Boot 3 Microservices with Kubernetes and Angular</a></li></ul><h3>Python Backend Path</h3><h3>Option 1: Django</h3><p><strong>Django Framework</strong>: MVT architecture, ORM, admin</p><ul><li>Video tutorial: <a href="https://youtu.be/JxzZxdht-XY?si=tIvwOyRKfK1IXbMt">Django Tutorial</a></li><li>Key components:</li><li>Models and database integration</li><li>Views and templates</li><li>Forms and validation</li><li>Admin interface</li><li>Authentication system</li></ul><h3>Option 2: FastAPI</h3><p><strong>FastAPI Framework</strong>: Modern, high-performance APIs</p><ul><li>Video tutorial: <a href="https://youtu.be/foGklduxhM0?si=metj6eewOXQCWPOP">FastAPI Crash Course</a></li><li>Key features:</li><li>Asynchronous request handling</li><li>Automatic documentation</li><li>Data validation with Pydantic</li><li>Dependency injection system</li></ul><h3>JavaScript Backend (Optional)</h3><p><strong>Node.js &amp; Express.js</strong>: Server-side JavaScript</p><ul><li>Project-based learning: <a href="https://github.com/practical-tutorials/project-based-learning">Practical Tutorials GitHub</a></li><li>Key concepts:</li><li>Event-driven architecture</li><li>Middleware pattern</li><li>RESTful API design</li><li>MongoDB integration</li></ul><h3>Phase 4: DevOps &amp; Deployment</h3><h3>Containerization</h3><p><strong>Docker</strong>: Container basics, images, Dockerfile</p><ul><li>Video explanation: <a href="https://youtu.be/H8Lyj2D_cWo?si=sFPqzizv0nR93vmm">What is Docker? Simply Explained</a></li><li>Visual guide: <a href="https://medium.com/@rajumanoj/docker-explained-using-the-given-diagram-29541b207389">Docker Explained Using Diagrams</a></li><li>Hands-on lab: <a href="https://learn.kodekloud.com/courses/udemy-labs-docker-for-the-absolute-beginner?utm_source=udemy&amp;utm_medium=labs&amp;utm_campaign=docker">Docker for the Absolute Beginner</a></li></ul><p><strong>Key concepts</strong>:</p><ul><li>Container vs. virtual machine</li><li>Docker Compose for multi-container applications</li><li>Docker networking and volumes</li></ul><h3>Continuous Integration/Continuous Deployment</h3><p><strong>Jenkins</strong>: Automation server, pipelines, jobs</p><ul><li>Video tutorial: <a href="https://youtu.be/mk2FBuTMwDc?si=weA5_xa-be_ZBqLB">CI/CD Pipeline Using Jenkins</a></li></ul><p><strong>Key concepts:</strong></p><ul><li>Pipeline as code</li><li>Build triggers</li><li>Integration with Git</li><li>Artifact management</li></ul><h3>Cloud Services</h3><p><strong>AWS</strong>: Core services, deployment strategies</p><ul><li>Video tutorial: <a href="https://youtu.be/B8i49C8fC3E?si=3WZrJ8ZwFdAQRYFZ">AWS Complete Tutorial 2023</a></li></ul><p><strong>Essential services:</strong></p><ul><li>EC2 (virtual servers)</li><li>S3 (object storage)</li><li>RDS (relational database)</li><li>Lambda (serverless functions)</li><li>IAM (identity management)</li></ul><h3>Phase 5: Integration Projects</h3><h3>Full Stack Project with Java Backend</h3><p><strong>Spring Boot + Angular + Docker + Kubernetes</strong></p><ul><li>Video tutorial: <a href="https://youtu.be/QjIiCBgEyy8?si=BAnndg3ayEo3fagn">DevOps Live Project with Spring Boot and Angular</a></li><li>Project components:</li><li>RESTful API with Spring Boot</li><li>Frontend with Angular</li><li>Containerization with Docker</li><li>Orchestration with Kubernetes</li><li>CI/CD pipeline</li></ul><h3>Full Stack Project with Python Backend</h3><p><strong>FastAPI + Angular + MySQL</strong></p><ul><li>Video tutorial: <a href="https://youtu.be/ip7b4JBW19k?si=HOmssAOq07G5pTK1">Build an App using Angular 17, Python Fast API and MySQL</a></li><li>Project components:</li><li>API development with FastAPI</li><li>Frontend with Angular</li><li>Database integration with MySQL</li><li>Authentication and authorization</li></ul><h3>Learning Path Progression</h3><h3>Beginner Level</h3><ol><li>Master programming fundamentals (Java or Python)</li><li>Learn HTML, CSS, JavaScript basics</li><li>Understand Git version control</li><li>Build simple static websites</li><li>Create basic database queries</li></ol><h3>Intermediate Level</h3><ol><li>Learn a frontend framework (Angular or React)</li><li>Master a backend framework (Spring Boot or Django/FastAPI)</li><li>Implement database integration</li><li>Build full CRUD applications</li><li>Understand RESTful API design</li></ol><h3>Advanced Level</h3><ol><li>Learn containerization with Docker</li><li>Implement CI/CD with Jenkins</li><li>Deploy applications to AWS</li><li>Build microservices architecture</li><li>Implement authentication and authorization</li><li>Create complete full stack applications</li></ol><h3>Practical Learning Approach</h3><h3>Project-Based Learning</h3><ul><li>Start with small components</li><li>Gradually integrate technologies</li><li>Follow the <a href="https://github.com/practical-tutorials/project-based-learning">Project-Based Learning GitHub</a> repository</li><li>Build portfolio-worthy projects</li></ul><h3>Learning Methodology</h3><ol><li><strong>Understand concepts</strong> through tutorials</li><li><strong>Practice</strong> with hands-on exercises</li><li><strong>Build</strong> small projects to reinforce learning</li><li><strong>Integrate</strong> multiple technologies</li><li><strong>Deploy</strong> applications to production environments</li></ol><h3>Technology Stack Summary</h3><h3>Frontend Technologies</h3><ul><li>HTML5, CSS3, JavaScript</li><li>Angular or React.js</li><li>TypeScript (for Angular)</li></ul><h3>Backend Technologies</h3><ul><li><strong>Java Path</strong>: Java, Spring Framework, Spring Boot, Maven</li><li><strong>Python Path</strong>: Python, Django or FastAPI</li><li><strong>Optional</strong>: Node.js, Express.js</li></ul><h3>Database Technologies</h3><ul><li>MySQL (relational database)</li><li>ORM tools (JPA/Hibernate for Java, Django ORM for Python)</li></ul><h3>DevOps &amp; Deployment</h3><ul><li>Git &amp; GitHub for version control</li><li>Docker for containerization</li><li>Jenkins for CI/CD</li><li>AWS for cloud hosting</li></ul><h3>Recommended Learning Schedule</h3><h3>Weekly Schedule (20–25 hours/week)</h3><ul><li><strong>Theory &amp; Tutorials</strong>: 8–10 hours</li><li><strong>Hands-on Practice</strong>: 8–10 hours</li><li><strong>Project Work</strong>: 4–5 hours</li></ul><h3>Daily Routine</h3><ol><li>Learn new concepts (1–2 hours)</li><li>Practice coding (1–2 hours)</li><li>Review and consolidate (30 minutes)</li></ol><h3>Career Development</h3><h3>Portfolio Building</h3><ul><li>Maintain a GitHub repository of projects</li><li>Document your learning journey</li><li>Create a personal website showcasing your skills</li></ul><h3>Professional Skills</h3><ul><li>Problem-solving techniques</li><li>Code review practices</li><li>Technical documentation</li><li>Team collaboration</li></ul><h3>Learning Path Summary</h3><pre>[Foundation] → HTML/CSS/JS + Java/Python Basics + Git<br>[Frontend] → Advanced JS → Angular/React<br>[Backend - Java] → Core Java → Spring Framework → Spring Boot → Spring Data/Security<br>[Backend - Python] → Advanced Python → Django/FastAPI<br>[Database] → MySQL (+ NoSQL optionally)<br>[DevOps] → Docker → Jenkins → AWS<br>[Integration] → Microservices → Full Stack Projects</pre><h3>Disclaimer</h3><p>This roadmap represents one possible learning path based on current technologies and practices as of 2024. The field of software development evolves rapidly, and some technologies, tools, or approaches may change over time. This guide should be used as a general reference rather than a definitive or absolute path. Always verify the relevance of specific technologies before investing significant time in learning them. The creator of this roadmap cannot guarantee that following this exact path will lead to employment or success in all contexts. Please adapt this roadmap to your specific goals, learning style, and the current state of the industry.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=071c0a8da176" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build An WebApp Using AWS]]></title>
            <link>https://medium.com/@rajumanoj/build-an-webapp-using-aws-f1b020c421c9?source=rss-441a1de114d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/f1b020c421c9</guid>
            <category><![CDATA[aws-api-gateway]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[aws-amplify]]></category>
            <category><![CDATA[aws-dynamodb]]></category>
            <dc:creator><![CDATA[Rajumanoj]]></dc:creator>
            <pubDate>Wed, 21 May 2025 14:40:40 GMT</pubDate>
            <atom:updated>2025-05-21T14:40:40.988Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Web Application Summary:</strong></p><p>This web application is a <strong>serverless, scalable, and fully managed platform</strong> built on AWS. It allows users to submit, view, and manage data (such as tasks, notes, or product items) in real-time through a user-friendly web interface.</p><p><strong>Purpose:</strong></p><p>The purpose of the application is to demonstrate how to build a <strong>modern, full-stack serverless web app</strong> using AWS services, ensuring high availability, low operational overhead, and automatic scaling without managing infrastructure.</p><p><strong>Key AWS Services Used:</strong></p><p><strong>AWS Lambda</strong>:</p><p>Handles backend business logic in a serverless fashion. When users interact with the app (e.g., submitting or retrieving data), Lambda functions are triggered to process the requests.</p><p><strong>Amazon API Gateway</strong>:</p><p>Acts as the entry point for HTTP requests to the backend. It routes client requests to the appropriate Lambda functions securely and efficiently.</p><p><strong>Amazon DynamoDB</strong>:</p><p>Serves as the NoSQL database for storing and retrieving application data with millisecond performance and automatic scaling.</p><p><strong>AWS Amplify</strong>:</p><p>Hosts and deploys the front-end web application. It provides a seamless CI/CD workflow and integrates easily with backend services like API Gateway and DynamoDB.</p><blockquote><em>Key AWS services used: Lambda, API Gateway, DynamoDB, AWS Amplify</em></blockquote><h3>System Architecture</h3><ul><li>Major components and their interactions</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*p1fFjJX6l2pDOdXj" /></figure><h3>Frontend Design</h3><ul><li>Technology/framework used with AWS Amplify</li><li>Connection to backend APIs</li></ul><h3>API Design</h3><ul><li>List of REST API endpoints exposed via API Gateway</li><li>Request/response schemas</li></ul><h3>Lambda Functions</h3><ul><li>Overview of key Lambda functions and their responsibilities</li><li>Trigger sources (e.g., API Gateway, DynamoDB Streams)</li><li>AWS Lambda provides <strong>serverless compute</strong> running <strong>small pieces of code (functions)</strong> <strong>triggered by events</strong> like S3 uploads.</li><li>It offers <strong>automatic scaling</strong> and potential <strong>cost savings</strong>, fitting for tasks like S3-triggered video processing.</li><li>Lambda has a <strong>free tier</strong>, but <strong>always clean up resources</strong> to avoid surprise bills and <strong>prevent infinite loops</strong>.</li></ul><h3>Data Model</h3><ul><li>DynamoDB table design (primary keys, indexes)</li><li>Data flow between components</li></ul><h3>Deployment Plan</h3><ul><li>Manual deployment steps</li><li>Use of AWS Amplify for frontend hosting</li></ul><h3>“Process for Developing a Web Application”</h3><h3>DynamoDB</h3><ul><li>Create a table and name it.</li><li>In the <strong>Partition key</strong> field, enter “ID” and create the table. Leave all other settings at their defaults.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7duHHFoA-oj6dV3eEMlxjQ.png" /><figcaption>DynamoDB window</figcaption></figure><ul><li>Click on Create table that Created the table as show in below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yX22Q3PPi54NQXNtOLZlYg.png" /><figcaption>Table Created With the name of ‘myTable’</figcaption></figure><p>After creating the table you will be find this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xl81XdQp-tqkTulD_jjsRQ.png" /></figure><ul><li>Under Settings you will find Find <strong>“ARN”</strong></li><li>Copy this ARN a Side Because We use this ARN in IAM role policy in Lambda Function Role policy</li></ul><p>This the page that you will find the ARN</p><h3>Lambda Function</h3><ul><li>Here the lambda Function Page</li><li>Create a Function According to your project this Lambda Function which We connect to “AWS API Gateway”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YsejKCMEe5rCxw5gzS0D4g.png" /><figcaption>Here the fuction name is “AddFunc”</figcaption></figure><h3>Step 1:</h3><ul><li>Create Your Function</li><li>Name the Function as your wish</li><li>Select the Runtime according to your project requirement As Now Select this to python</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-BM4BPWyEbGcVxD51mP3NA.png" /></figure><p>Note : Remember do select Related Runtime According to your project/App (ex: python , node, java…)</p><h3>Step2:</h3><ul><li>After creating the function</li><li>Write the Lambda function shown below, or create your own function based on your requirements</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-C77RC0ZPCA1yPvGhDt2hA.png" /><figcaption>Write Below code in lambda_function.py</figcaption></figure><p>Write a Lambda Code</p><pre>import json<br>import boto3<br>import time<br>from botocore.exceptions import ClientError<br># Create a DynamoDB client<br>dynamodb = boto3.resource(&#39;dynamodb&#39;)<br>table = dynamodb.Table(&#39;myTable&#39;)  # Correct table name<br>def lambda_handler(event, context):<br>    # Extract the numbers from the event<br>    num1 = event.get(&#39;num1&#39;)<br>    num2 = event.get(&#39;num2&#39;)<br>    if num1 is None or num2 is None:<br>        return {<br>            &#39;statusCode&#39;: 400,<br>            &#39;body&#39;: json.dumps({&#39;message&#39;: &#39;Both num1 and num2 are required&#39;})<br>        }<br>    # Calculate the sum<br>    sum_result = num1 + num2<br>    # Generate a unique ID for the Partition Key (ID)<br>    partition_key = str(int(time.time() * 1000))  # Unique ID based on timestamp<br>    # Generate a Sort Key (you can modify this based on your design)<br>    sort_key = str(int(time.time()))  # Or you can use something like &#39;Sum&#39; or &#39;Timestamp&#39;<br>    # Prepare the item to insert into DynamoDB<br>    item = {<br>        &#39;ID&#39;: partition_key,  # Partition Key<br>        &#39;Timestamp&#39;: sort_key,  # Sort Key (you can replace this with your actual Sort Key attribute)<br>        &#39;num1&#39;: num1,<br>        &#39;num2&#39;: num2,<br>        &#39;sum&#39;: sum_result<br>    }<br>    # Put the item into the DynamoDB table<br>    try:<br>        table.put_item(Item=item)<br>    except ClientError as e:<br>        return {<br>            &#39;statusCode&#39;: 500,<br>            &#39;body&#39;: json.dumps({&#39;message&#39;: f&#39;Error storing data in DynamoDB: {e.response[&quot;Error&quot;][&quot;Message&quot;]}&#39;})<br>        }<br>    # Return the response with the sum and the ID of the stored item<br>    return {<br>        &#39;statusCode&#39;: 200,<br>        &#39;body&#39;: json.dumps({<br>            &#39;message&#39;: &#39;Sum calculated and stored successfully&#39;,<br>            &#39;result&#39;: {<br>                &#39;ID&#39;: partition_key,<br>                &#39;Timestamp&#39;: sort_key,<br>                &#39;num1&#39;: num1,<br>                &#39;num2&#39;: num2,<br>                &#39;sum&#39;: sum_result<br>            }<br>        })<br>    }</pre><h3>Step 3:</h3><ul><li>First, deploy the code and then test it.</li></ul><pre>{ &quot;num1&quot;: 5, &quot;num2&quot;: 10 }</pre><ul><li>Enter the JSON body above to test the code. If you receive a Status Code 200 OK, then the test has passed.</li></ul><p>Now we make some Changes in the role policy</p><p>Go to Configuration → Permissions → click on <strong>“Role Name”</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rRYjXFK6c3AUgYx3c3iqKA.png" /></figure><ul><li>After Click On the Role name You will find the Add permissions on top corner</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gwuTXG0UeKJGQzBIwAAz5w.png" /></figure><ul><li>Click On the Add Permission then inline Policy</li><li>You will find Policy editor</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FNGZcM7lX6Zek30ai0kcvw.png" /></figure><ul><li>Go to Filters and Select the DynamoDB then Actions(what Required to Lambda Function and API Gateway)</li></ul><p>Policy Editor Mandatory Fields</p><ol><li>Action</li><li>Resource</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4j7DjJY5ET_Zb1_GPfAQwA.png" /></figure><h3>Go to DynamoDB Window → Here ARN link of DynamoDB is found in DynamoDB window</h3><ul><li>Copy ARN link from here and paste in the resource in Double quotes</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jv6-4Dpk3ETT2CDDLAi8Jw.png" /></figure><ul><li><strong>Name the Policy and create the inline policy</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3xRy2532txBOgt34C_LcMg.png" /></figure><h3>API GATEWAY</h3><ul><li>Create API</li><li>Select REST API build</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4t8fvzEb79Cj-3MFFlTrTw.png" /></figure><ul><li>Name The API (* Do not Change anything)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FDpUTCImud0LGolgUhDQ7g.png" /></figure><ul><li>Create a Method As per the Requirement<br> As per Now make POST request</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rfzmpkpSWKwCaxC79-fBlQ.png" /></figure><ul><li>After Clicking the Create Method You Find this interface As per Now Select the “POST”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*USVOB3mf3lDzG6rcNItyEg.png" /></figure><ul><li>Now Select Lambda Function as we create Already Created</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rcFBfZ00ClGxC9HQJqcT0w.png" /></figure><ul><li>Click on / (here you will find the option CROS)</li><li>Enable the CROS it must and should because It will connect to Frontend and Backend</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dGuMP5X9_MBk-ODFiJlF2A.png" /></figure><ul><li>After Clicking CROS Enable Select POST and Save</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aX2uasjaLen6kxgDTQMX-g.png" /></figure><ul><li>Now Deploy the API → New Stage → name the stage as ‘dev’ or as your wish</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LhgKWwMEFcCxghxACz7gjg.png" /></figure><ul><li>After Deploy API → We find Invoke URL</li><li>This URL which is connected with our Lambda Function</li><li>This URL is invoke our function and based on this your we should develop the frontend I mean take this Use this URL build the Frontend</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xudF9kw-h0OuIoGHiSadTQ.png" /></figure><h3>AWS Amplify</h3><p>Here We deploy the Our Application we can connect with all other providers or We can deploy Manually</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WQE3lAQ6fygPqLR4yYxl4g.png" /><figcaption>Select Deploy Without git as Now</figcaption></figure><ul><li>Select Deploy Without git as Now</li><li>Upload Your Frontend code</li><li>Name Your Application</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lmboucOFkSZYfdVMLKYLhQ.png" /><figcaption>We Should Upload Only Zip file.</figcaption></figure><p>Below I provide the HTML , CSS , JAVASCRIPIT convert this 3 into Zip file and Upload</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GJvFdfZMarlSID--AW8_oA.png" /><figcaption>Final Screen</figcaption></figure><ul><li>Final Screen : After Deploying finally URL will be displayed here</li></ul><p>Here Below code is for Frontend Website Which Contains Basic Html ,CSS, JavaScript If you want to building Web Application You can also use other frameworks and tools for Developing Frontend Website</p><p>JavaScript</p><pre>document.addEventListener(&#39;DOMContentLoaded&#39;, function() {<br>    // Define API endpoint<br>    const API_ENDPOINT = &#39;&lt;https://5nur6rhsjb.execute-api.us-east-1.amazonaws.com/dev&gt;&#39;;<br>    <br>    // Get DOM elements<br>    const calculatorForm = document.getElementById(&#39;calculatorForm&#39;);<br>    const num1Input = document.getElementById(&#39;num1&#39;);<br>    const num2Input = document.getElementById(&#39;num2&#39;);<br>    const calculateBtn = document.getElementById(&#39;calculateBtn&#39;);<br>    const btnText = document.getElementById(&#39;btnText&#39;);<br>    const loadingSpinner = document.getElementById(&#39;loadingSpinner&#39;);<br>    const errorAlert = document.getElementById(&#39;errorAlert&#39;);<br>    const errorMessage = document.getElementById(&#39;errorMessage&#39;);<br>    const resultSection = document.getElementById(&#39;resultSection&#39;);<br>    <br>    // Result fields<br>    const resultId = document.getElementById(&#39;resultId&#39;);<br>    const resultTimestamp = document.getElementById(&#39;resultTimestamp&#39;);<br>    const resultNum1 = document.getElementById(&#39;resultNum1&#39;);<br>    const resultNum2 = document.getElementById(&#39;resultNum2&#39;);<br>    const resultSum = document.getElementById(&#39;resultSum&#39;);<br>    <br>    // Form submission handler<br>    calculatorForm.addEventListener(&#39;submit&#39;, function(event) {<br>        event.preventDefault();<br>        <br>        // Hide any previous error messages and results<br>        errorAlert.classList.add(&#39;d-none&#39;);<br>        resultSection.classList.add(&#39;d-none&#39;);<br>        <br>        // Get input values<br>        const num1 = parseFloat(num1Input.value);<br>        const num2 = parseFloat(num2Input.value);<br>        <br>        // Validate input (just in case HTML5 validation fails)<br>        if (isNaN(num1) || isNaN(num2)) {<br>            showError(&#39;Please enter valid numbers&#39;);<br>            return;<br>        }<br>        <br>        // Show loading state<br>        setLoadingState(true);<br>        <br>        // Prepare data for the API<br>        const requestData = {<br>            num1: num1,<br>            num2: num2<br>        };<br>        <br>        // Call the API<br>        fetch(API_ENDPOINT, {<br>            method: &#39;POST&#39;,<br>            headers: {<br>                &#39;Content-Type&#39;: &#39;application/json&#39;<br>            },<br>            body: JSON.stringify(requestData)<br>        })<br>        .then(response =&gt; {<br>            if (!response.ok) {<br>                return response.json().then(errData =&gt; {<br>                    throw new Error(errData.message || &#39;Server error&#39;);<br>                });<br>            }<br>            return response.json();<br>        })<br>        .then(data =&gt; {<br>            setLoadingState(false);<br>            <br>            // Process the response<br>            if (data.statusCode &amp;&amp; data.statusCode === 200 &amp;&amp; data.body) {<br>                try {<br>                    // Parse the nested body string, as the API returns a stringified JSON<br>                    const resultData = typeof data.body === &#39;string&#39; <br>                        ? JSON.parse(data.body) <br>                        : data.body;<br>                    <br>                    // Display the result<br>                    displayResult(resultData);<br>                } catch (err) {<br>                    showError(&#39;Error parsing the result: &#39; + err.message);<br>                }<br>            } else {<br>                showError(&#39;Unexpected API response format&#39;);<br>            }<br>        })<br>        .catch(error =&gt; {<br>            setLoadingState(false);<br>            showError(error.message || &#39;An error occurred while communicating with the API&#39;);<br>        });<br>    });<br>    <br>    // Function to show error message<br>    function showError(message) {<br>        errorMessage.textContent = message;<br>        errorAlert.classList.remove(&#39;d-none&#39;);<br>    }<br>    <br>    // Function to set loading state<br>    function setLoadingState(isLoading) {<br>        if (isLoading) {<br>            btnText.textContent = &#39;Calculating...&#39;;<br>            loadingSpinner.classList.remove(&#39;d-none&#39;);<br>            calculateBtn.disabled = true;<br>        } else {<br>            btnText.textContent = &#39;Calculate Sum&#39;;<br>            loadingSpinner.classList.add(&#39;d-none&#39;);<br>            calculateBtn.disabled = false;<br>        }<br>    }<br>    <br>    // Function to display the result<br>    function displayResult(data) {<br>        // Make sure we have a result object<br>        if (!data.result) {<br>            showError(&#39;No result data in the API response&#39;);<br>            return;<br>        }<br>        <br>        const result = data.result;<br>        <br>        // Format timestamp to human-readable date if needed<br>        let timestampDisplay = result.Timestamp;<br>        if (result.Timestamp &amp;&amp; !isNaN(result.Timestamp)) {<br>            const date = new Date(parseInt(result.Timestamp) * 1000);<br>            timestampDisplay = date.toLocaleString();<br>        }<br>        <br>        // Update result fields<br>        resultId.textContent = result.ID || &#39;N/A&#39;;<br>        resultTimestamp.textContent = timestampDisplay || &#39;N/A&#39;;<br>        resultNum1.textContent = result.num1;<br>        resultNum2.textContent = result.num2;<br>        resultSum.textContent = result.sum;<br>        <br>        // Show result section<br>        resultSection.classList.remove(&#39;d-none&#39;);<br>    }<br>});</pre><p>index.html</p><pre>&lt;!DOCTYPE html&gt;<br>&lt;html&gt;<br>&lt;head&gt;<br>    &lt;meta charset=&quot;UTF-8&quot;&gt;<br>    &lt;title&gt;Sum Calculator&lt;/title&gt;<br>    &lt;!-- Styling for the client UI --&gt;<br>    &lt;style&gt;<br>    h1 {<br>        color: #FFFFFF;<br>        font-family: system-ui;<br>        margin-left: 20px;<br>        }<br>    body {<br>        background-color: #222629;<br>        }<br>    label {<br>        color: #86C232;<br>        font-family: system-ui;<br>        font-size: 20px;<br>        margin-left: 20px;<br>        margin-top: 20px;<br>        }<br>     button {<br>        background-color: #86C232;<br>        border-color: #86C232;<br>        color: #FFFFFF;<br>        font-family: system-ui;<br>        font-size: 20px;<br>        font-weight: bold;<br>        margin-left: 30px;<br>        margin-top: 20px;<br>        width: 140px;<br>        cursor: pointer;<br>        }<br>     input {<br>        color: #222629;<br>        font-family: system-ui;<br>        font-size: 20px;<br>        margin-left: 10px;<br>        margin-top: 20px;<br>        width: 100px;<br>        }<br>    #result {<br>        color: #FFFFFF;<br>        font-family: system-ui;<br>        font-size: 18px;<br>        margin-left: 20px;<br>        margin-top: 30px;<br>        padding: 15px;<br>        background-color: #333;<br>        border-radius: 5px;<br>        max-width: 600px;<br>        display: none;<br>    }<br>    &lt;/style&gt;<br>    &lt;script&gt;<br>        // callAPI function that takes two numbers as parameters<br>        var callAPI = (num1, num2)=&gt;{<br>            // instantiate a headers object<br>            var myHeaders = new Headers();<br>            // add content type header to object<br>            myHeaders.append(&quot;Content-Type&quot;, &quot;application/json&quot;);<br>            // using built in JSON utility package turn object to string and store in a variable<br>            var raw = JSON.stringify({&quot;num1&quot;: parseInt(num1), &quot;num2&quot;: parseInt(num2)});<br>            // create a JSON object with parameters for API call and store in a variable<br>            var requestOptions = {<br>                method: &#39;POST&#39;,<br>                headers: myHeaders,<br>                body: raw,<br>                redirect: &#39;follow&#39;<br>            };<br>            // make API call with parameters and use promises to get response<br>            fetch(&quot;&lt;https://5nur6rhsjb.execute-api.us-east-1.amazonaws.com/dev&gt;&quot;, requestOptions)<br>            .then(response =&gt; response.text())<br>            .then(result =&gt; {<br>                var responseObj = JSON.parse(result);<br>                var resultObj = JSON.parse(responseObj.body);<br>                <br>                // Display result in a nicer format than an alert<br>                var resultDiv = document.getElementById(&#39;result&#39;);<br>                resultDiv.innerHTML = `<br>                    &lt;strong&gt;Result:&lt;/strong&gt; ${resultObj.message}&lt;br&gt;<br>                    &lt;strong&gt;Sum:&lt;/strong&gt; ${resultObj.result.num1} + ${resultObj.result.num2} = ${resultObj.result.sum}&lt;br&gt;<br>                    &lt;strong&gt;ID:&lt;/strong&gt; ${resultObj.result.ID}&lt;br&gt;<br>                    &lt;strong&gt;Timestamp:&lt;/strong&gt; ${resultObj.result.Timestamp}<br>                `;<br>                resultDiv.style.display = &#39;block&#39;;<br>            })<br>            .catch(error =&gt; {<br>                console.log(&#39;error&#39;, error);<br>                document.getElementById(&#39;result&#39;).innerHTML = `&lt;strong&gt;Error:&lt;/strong&gt; ${error}`;<br>                document.getElementById(&#39;result&#39;).style.display = &#39;block&#39;;<br>            });<br>        }<br>    &lt;/script&gt;<br>&lt;/head&gt;<br>&lt;body&gt;<br>    &lt;h1&gt;SUM CALCULATOR&lt;/h1&gt;<br>    &lt;form&gt;<br>        &lt;label&gt;Number 1:&lt;/label&gt;<br>        &lt;input type=&quot;number&quot; id=&quot;num1&quot;&gt;<br>        &lt;label&gt;Number 2:&lt;/label&gt;<br>        &lt;input type=&quot;number&quot; id=&quot;num2&quot;&gt;<br>        &lt;!-- set button onClick method to call function we defined passing input values as parameters --&gt;<br>        &lt;button type=&quot;button&quot; onclick=&quot;callAPI(document.getElementById(&#39;num1&#39;).value,document.getElementById(&#39;num2&#39;).value)&quot;&gt;CALCULATE&lt;/button&gt;<br>    &lt;/form&gt;<br>    &lt;div id=&quot;result&quot;&gt;&lt;/div&gt;<br>&lt;/body&gt;<br>&lt;/html&gt;</pre><p>style.css</p><pre>body {<br>    background-color: var(--bs-dark-bg-subtle);<br>    padding-bottom: 2rem;<br>}<br>.card {<br>    border-radius: 10px;<br>    overflow: hidden;<br>}<br>.card-header {<br>    border-bottom: 1px solid rgba(255, 255, 255, 0.1);<br>}<br>input:focus, <br>button:focus {<br>    box-shadow: 0 0 0 0.25rem rgba(var(--bs-primary-rgb), 0.25) !important;<br>}<br>#resultSection {<br>    animation: fadeIn 0.5s ease-in-out;<br>}<br>@keyframes fadeIn {<br>    from { opacity: 0; transform: translateY(10px); }<br>    to { opacity: 1; transform: translateY(0); }<br>}<br>.form-control:focus {<br>    border-color: var(--bs-primary);<br>}<br>/* Make sure numeric inputs have the same width in all browsers */<br>input[type=number] {<br>    -moz-appearance: textfield;<br>}<br>input::-webkit-outer-spin-button,<br>input::-webkit-inner-spin-button {<br>    -webkit-appearance: none;<br>    margin: 0;<br>}<br>code {<br>    background-color: rgba(255, 255, 255, 0.1);<br>    padding: 0.2em 0.4em;<br>    border-radius: 4px;<br>    font-size: 85%;<br>}</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1b020c421c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Docker Explained Using the Given Diagram]]></title>
            <link>https://medium.com/@rajumanoj/docker-explained-using-the-given-diagram-29541b207389?source=rss-441a1de114d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/29541b207389</guid>
            <category><![CDATA[docker-image]]></category>
            <category><![CDATA[commands]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[dockerfiles]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Rajumanoj]]></dc:creator>
            <pubDate>Mon, 10 Feb 2025 03:44:36 GMT</pubDate>
            <atom:updated>2025-02-10T03:44:36.869Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P5dlEJRwyKyqzWI-nfF7ig.png" /><figcaption><strong>Docker architecture</strong></figcaption></figure><h3>What is Docker?</h3><p>Docker is a platform that allows developers to package applications and their dependencies into lightweight, portable containers. Containers ensure that applications run consistently across different environments.</p><h3>Understanding Docker with the Given Diagram</h3><p>The diagram represents a <strong>Docker workflow</strong> with three main sections:</p><ol><li><strong>Client</strong> (Docker Commands)</li><li><strong>Images and Containers</strong></li><li><strong>Registry</strong> (Image Storage)</li></ol><h3>1. Client (Docker Commands)</h3><p>The <strong>Client</strong> is where you interact with Docker. It allows users to build, run, and manage containers using commands like:</p><ul><li>docker pull → Downloads an image from a registry.</li><li>docker run → Runs a container from an image.</li><li>docker build → Creates a new image from a Dockerfile.</li></ul><p>These commands are used to fetch images, start containers, and build custom images.</p><h3>2. Images and Containers</h3><ul><li><strong>Images</strong>: Pre-configured application environments that can be used to create containers.</li><li>In the diagram, <strong>Linux, Python, and Redis</strong> are images.</li><li><strong>Containers</strong>: Running instances of images that execute applications in isolated environments.</li><li>The diagram shows two running <strong>containers</strong> from the Python and Redis images.</li></ul><p>How this works:</p><ol><li>The user pulls an image (e.g., Python or Redis) using docker pull.</li><li>The image is used to create a container using docker run.</li><li>The container runs the application in an isolated environment.</li></ol><h3>3. Registry (Image Storage)</h3><p>The <strong>Registry</strong> is a storage system for Docker images. Popular registries include:</p><ul><li><strong>Docker Hub</strong> (default public registry)</li><li><strong>Private Registries</strong> (self-hosted)</li></ul><p>The diagram shows different categories:</p><ol><li><strong>Images</strong> (Prebuilt application environments like NGINX, Ubuntu, PostgreSQL, BusyBox)</li><li><strong>Extensions</strong> (Add-ons like JFrog, Tailscale)</li><li><strong>Plugins</strong> (Integrations with tools like Docker, Grafana, VMware)</li></ol><p>Docker can <strong>pull images from a registry</strong> and <strong>push custom images to a registry</strong>.</p><h3>Main Docker Commands</h3><p>Here are essential Docker commands categorized for practical use:</p><h3>1. Basic Commands</h3><ul><li>docker --version → Check Docker version.</li><li>docker info → Get system-wide Docker information.</li><li>docker help → Get help on Docker commands.</li></ul><h3>2. Image Management</h3><ul><li>docker pull &lt;image&gt; → Download an image from the registry.</li><li>docker images → List downloaded images.</li><li>docker rmi &lt;image&gt; → Remove an image.</li></ul><h3>3. Container Management</h3><ul><li>docker run &lt;image&gt; → Create and start a container.</li><li>docker ps → List running containers.</li><li>docker ps -a → List all containers (running + stopped).</li><li>docker stop &lt;container&gt; → Stop a running container.</li><li>docker rm &lt;container&gt; → Remove a container.</li></ul><h3>4. Building Custom Images</h3><ul><li>docker build -t myapp . → Build an image from a Dockerfile.</li><li>docker tag myapp myrepo/myapp:v1.0 → Tag an image.</li><li>docker push myrepo/myapp:v1.0 → Push an image to a registry.</li></ul><h3>5. Volume and Network</h3><ul><li>docker volume create myvolume → Create a volume.</li><li>docker network create mynetwork → Create a custom network.</li></ul><h3>Practical Example: Running a Python + Redis Application with Docker</h3><p>Follow these <strong>step-by-step</strong> instructions to practice using Docker.</p><h3>Step 1: Install Docker</h3><p>Ensure Docker is installed on your system by running:</p><pre>docker --version</pre><h3>Step 2: Pull Required Images</h3><pre>docker pull python<br>docker pull redis</pre><p>This downloads the <strong>Python</strong> and <strong>Redis</strong> images.</p><h3>Step 3: Run Containers</h3><p>Run the <strong>Python container</strong>:</p><pre>docker run -d --name python-app python</pre><p>Run the <strong>Redis container</strong>:</p><pre>docker run -d --name redis-server redis</pre><p>Now both containers are running in the background (-d flag).</p><h3>Step 4: Check Running Containers</h3><pre>docker ps</pre><p>This will list all running containers.</p><h3>Step 5: Access the Python Container</h3><pre>docker exec -it python-app bash</pre><p>This opens a terminal inside the <strong>Python container</strong>.</p><h3>Step 6: Stop and Remove Containers</h3><p>To stop:</p><pre>docker stop python-app redis-server</pre><p>To remove:</p><pre>docker rm python-app redis-server</pre><h3>Conclusion</h3><p>By following these steps, you have:</p><p>✅ Pulled images<br> ✅ Created and ran containers<br> ✅ Managed containers using commands</p><p>This tutorial provides a strong foundation in Docker, allowing you to build and deploy applications efficiently. 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29541b207389" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mentorship Programs and Internships in Software Engineering]]></title>
            <link>https://medium.com/@rajumanoj/mentorship-programs-and-internships-in-software-engineering-5e230f37ea04?source=rss-441a1de114d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e230f37ea04</guid>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[mentorship-program]]></category>
            <category><![CDATA[help]]></category>
            <category><![CDATA[part-time-jobs]]></category>
            <dc:creator><![CDATA[Rajumanoj]]></dc:creator>
            <pubDate>Sun, 02 Feb 2025 10:42:05 GMT</pubDate>
            <atom:updated>2025-02-02T10:42:05.670Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uZBNMedfMuSBr9SW" /><figcaption>Photo by <a href="https://unsplash.com/@brookecagle?utm_source=medium&amp;utm_medium=referral">Brooke Cagle</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Fulbright-Nehru Master’s Fellowships:</strong> <a href="https://www.usief.org.in/fulbright-nehru-fellowships.aspx">https://www.usief.org.in/fulbright-nehru-fellowships.aspx</a></p><p><strong>The Theil Fellowship :</strong> <a href="https://thielfellowship.org/">https://thielfellowship.org/</a></p><p><strong>Outreachy :</strong> <a href="https://www.outreachy.org/">https://www.outreachy.org/</a></p><p><strong>LFX Mentorship :</strong> <a href="https://mentorship.lfx.linuxfoundatio/">https://mentorship.lfx.linuxfoundatio</a>...</p><p><strong>LFN Mentorship Program :</strong> <a href="https://wiki.lfnetworking.org/display">https://wiki.lfnetworking.org/display</a>...</p><p><strong>Linux Kernel Mentorship Program :</strong> <a href="https://wiki.linuxfoundation.org/lkmp">https://wiki.linuxfoundation.org/lkmp</a></p><p><a href="https://github.com/cncf/mentoring/blo">https://github.com/cncf/mentoring/blo</a>...</p><p><strong>Adobe Women In Technology :</strong> <a href="https://research.adobe.com/adobe-indi">https://research.adobe.com/adobe-indi</a>...</p><p><strong>Microsoft Open Source Fest :</strong> <a href="https://www.microsoft.com/en-us/resea">https://www.microsoft.com/en-us/resea</a>...</p><p><strong>GHC :</strong> <a href="https://ghc.anitab.org/attend/scholar">https://ghc.anitab.org/attend/scholar</a>...</p><p><strong>SN Bose Scholars Program :</strong> <a href="https://iusstf.org/s-n-bose-scholars-">https://iusstf.org/s-n-bose-scholars-</a>...</p><p><strong>24 Pull Requests :</strong> <a href="https://24pullrequests.com/about">https://24pullrequests.com/about</a></p><p><strong>Hacktoberfest :</strong> <a href="https://hacktoberfest.digitalocean.com/">https://hacktoberfest.digitalocean.com/</a></p><p><strong>Hyperledger Mentorship Program :</strong> <a href="https://wiki.hyperledger.org/display/">https://wiki.hyperledger.org/display/</a>...</p><p><strong>Season of KDE :</strong> <a href="https://season.kde.org/">https://season.kde.org/</a></p><p><strong>Open Mainframe Project :</strong> <a href="https://www.openmainframeproject.org/">https://www.openmainframeproject.org/</a>...</p><p><strong>Summer of Bitcoin :</strong> <a href="https://www.summerofbitcoin.org/">https://www.summerofbitcoin.org/</a></p><p><strong>Summer of Code Google :</strong><a href="https://summerofcode.withgoogle.com/a">https://summerofcode.withgoogle.com/a</a>...</p><p><strong>Google Summer of Docs :</strong><a href="https://developers.google.com/season-">https://developers.google.com/season-</a>...</p><p><strong>Alibaba Summer of Code :</strong><a href="https://www.alibabacloud.com/campaign">https://www.alibabacloud.com/campaign</a>...</p><p><strong>Meta Fellowship :</strong><a href="https://research.facebook.com/fellows/">Fellows — Emerging Scholars — Meta Research</a></p><p><strong>Qualcomm Scholars :</strong><a href="https://www.iie.org/Programs/WeTech/S">https://www.iie.org/Programs/WeTech/S</a>...</p><p><strong>MLH Fellowship :</strong><a href="https://fellowship.mlh.io/">https://fellowship.mlh.io</a></p><p><strong>Summer of Haskell :</strong> <a href="https://summer.haskell.org/">https://summer.haskell.org/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e230f37ea04" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[gRPC Server Setup with Gradle]]></title>
            <link>https://medium.com/@rajumanoj/grpc-server-setup-with-gradle-f88bf66dabce?source=rss-441a1de114d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/f88bf66dabce</guid>
            <category><![CDATA[gradle]]></category>
            <category><![CDATA[grpc-java]]></category>
            <category><![CDATA[grpc-client]]></category>
            <category><![CDATA[grpc]]></category>
            <category><![CDATA[servers]]></category>
            <dc:creator><![CDATA[Rajumanoj]]></dc:creator>
            <pubDate>Wed, 29 Jan 2025 10:29:24 GMT</pubDate>
            <atom:updated>2025-01-29T10:29:24.638Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Grpc" src="https://cdn-images-1.medium.com/max/1024/1*UtJlXF-yvV0nuBZqxGM3Rw.png" /></figure><p>Step 1 : Add This Code into <em>bulid.gradle</em> and Change the version Accordingly</p><pre>plugins {<br>    id &#39;java&#39;<br>    id &#39;idea&#39;<br>    id &#39;com.google.protobuf&#39; version &#39;0.9.4&#39;<br>}<br>group = &#39;org.example.com&#39;<br>version = &#39;1.0-SNAPSHOT&#39;<br>repositories {<br>    mavenCentral()<br>}<br>protobuf {<br>    protoc {<br>        artifact = &quot;com.google.protobuf:protoc:3.25.5&quot;<br>    }<br>    plugins {<br>        grpc {<br>            artifact = &#39;io.grpc:protoc-gen-grpc-java:1.70.0&#39;<br>        }<br>    }<br>    generateProtoTasks {<br>        all()*.plugins {<br>            grpc {}<br>        }<br>    }<br>}<br>sourceSets.main.java.srcDir new File(buildDir, &#39;generated/source&#39;)<br>dependencies {<br>    runtimeOnly &#39;io.grpc:grpc-netty-shaded:1.70.0&#39;<br>    implementation &#39;io.grpc:grpc-protobuf:1.70.0&#39;<br>    implementation &#39;io.grpc:grpc-stub:1.70.0&#39;<br>    compileOnly &#39;org.apache.tomcat:annotations-api:6.0.53&#39; // necessary for Java 9+<br>    testImplementation platform(&#39;org.junit:junit-bom:5.10.0&#39;)<br>    testImplementation &#39;org.junit.jupiter:junit-jupiter&#39;<br>}<br>test {<br>    useJUnitPlatform()<br>}</pre><p>Step 2 : Save and Build the project using gradle icon</p><p>Step 3 : Add a package to src/main package name is proto</p><pre>syntax =&#39;proto3&#39;;<br>package dummy;<br>option java_package=&#39;com.proto.dummy&#39;;<br>option java_multiple_files= true;<br>message Dummymessage{<br>}<br>service Dummyservice{}</pre><p>Step 4 : Add Another package with name greeting.server in src/main/java</p><p>Step 5 : Create a java file name GreetingServer</p><pre>package greeting.server;<br>import io.grpc.Server;<br>import io.grpc.ServerBuilder;<br>import java.io.IOException;<br>public class GreetingServer {<br>    public static void main(String[] args) throws IOException, InterruptedException {<br>        int port =50051;<br>        Server server = ServerBuilder.forPort(port).build();<br>        server.start();<br>        System.out.println(&quot;Server started&quot;);<br>        System.out.println(&quot;listening to port&quot;+ port);<br>        Runtime.getRuntime().addShutdownHook(new Thread(() -&gt; {<br>            System.out.println(&quot;received shutdown request&quot;);<br>            server.shutdown();<br>            System.out.println(&quot;Server Stopped&quot;);<br>        }));<br>        server.awaitTermination();<br>    }<br>}<br></pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/579/1*oJ3PSNNAwgIp1x2nbL1jvw.png" /><figcaption>Project Structure</figcaption></figure><h3>Before Running the above code we need some changes</h3><p>— Go to settings and find gradle the change</p><p>Build and run in to<strong> IntelliJ IDEA</strong> and change Run tests into<strong> IntelliJ IDEA</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j17RW20bNkkjx0VDrct31g.png" /><figcaption>Settings</figcaption></figure><p><strong>Then Go To Edit configurations add Application</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/330/1*8no4uY5Pac-1gE18fN5nCA.png" /></figure><p>Change Name : GreetingServer</p><p>Build and Run To java 17</p><p>-cp to Grpc-java.main</p><p>Add GreetingServer file in main file</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*twiqEzzdaTfe3_ZsmIR3KA.png" /></figure><p>Apply and Okay</p><p>Then Run the project</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/898/1*__P_7rbT_nZalWcOvN3kFw.png" /></figure><p>OUTPUT for Above program</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f88bf66dabce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Protobuf installation for gRPC — gradle]]></title>
            <link>https://medium.com/@rajumanoj/protobuf-installation-for-grpc-gradle-a063d69214c1?source=rss-441a1de114d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/a063d69214c1</guid>
            <category><![CDATA[grpc-java]]></category>
            <category><![CDATA[gradle]]></category>
            <category><![CDATA[protobuf]]></category>
            <category><![CDATA[grpc]]></category>
            <category><![CDATA[installation]]></category>
            <dc:creator><![CDATA[Rajumanoj]]></dc:creator>
            <pubDate>Thu, 16 Jan 2025 08:48:59 GMT</pubDate>
            <atom:updated>2025-01-16T08:48:59.890Z</atom:updated>
            <content:encoded><![CDATA[<h3>Protobuf Installation for gRPC — gradle</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*goVupTYgVycIxQasHN_WlQ.jpeg" /></figure><p><strong>Step1</strong>: Create a Project Intellij IDEA</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X_5G2cY7UoEN7xF9LJ94Cg.png" /><figcaption>project Intellij IDEA</figcaption></figure><p><strong>Step2</strong>: Go to <strong>build.gradle</strong> and add some plugins and dependencies as requirement and update versions as give below</p><p><a href="https://github.com/google/protobuf-gradle-plugin">https://github.com/google/protobuf-gradle-plugin</a></p><pre>plugins {<br>    id &#39;java&#39;<br>    id &#39;idea&#39;<br>    id &quot;com.google.protobuf&quot; version &quot;0.9.4&quot;<br>}<br>group = &#39;org.example&#39;<br>version = &#39;1.0-SNAPSHOT&#39;<br>repositories {<br>    mavenCentral()<br>}<br>protobuf {<br>    protoc {<br>        artifact = &#39;com.google.protobuf:protoc:4.29.3&#39;<br>    }<br>}<br>dependencies {<br>    implementation group: &#39;com.google.protobuf&#39;, name: &#39;protobuf-java&#39;, version: &#39;4.29.3&#39;<br>    implementation group: &#39;com.google.protobuf&#39;, name: &#39;protobuf-java-util&#39;, version: &#39;4.29.3&#39;<br>    testImplementation platform(&#39;org.junit:junit-bom:5.10.0&#39;)<br>    testImplementation &#39;org.junit.jupiter:junit-jupiter&#39;<br>}<br>test {<br>    useJUnitPlatform()<br>}</pre><p><strong>Step3</strong>: Run the command in the terminal</p><pre>./gradlew build</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_SO_f_she4jDMgwRY9lkpg.png" /></figure><p><strong>Step4</strong>: Create a package inside main Name the package Proto in that <strong>create a proto file</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-PZ4e5tQt33GJER-aW5YXQ.png" /></figure><p><strong>Step5</strong> : On right side You will file <em>gradle symbol</em> click on it you will find folders select other then click on <strong>generateproto</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/809/1*8oY8lJUBarNKJTyQebWziA.png" /></figure><p><strong>Step6</strong>: You will find the generated proto file in build folder <strong>“Go to generated then Go to source”</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/664/1*eIAxVamlXAAsRxgARCS60Q.png" /><figcaption>Project Structure</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WraCPfITHU6OaXWBjIKkCw.png" /><figcaption>This is the Generated java code by protoc</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a063d69214c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MySQL Installation In MAC]]></title>
            <link>https://medium.com/@rajumanoj/mysql-installation-in-mac-7a1899a41a52?source=rss-441a1de114d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a1899a41a52</guid>
            <category><![CDATA[mysql-workbench]]></category>
            <category><![CDATA[installation]]></category>
            <category><![CDATA[mysql]]></category>
            <dc:creator><![CDATA[Rajumanoj]]></dc:creator>
            <pubDate>Fri, 29 Nov 2024 17:15:20 GMT</pubDate>
            <atom:updated>2024-11-29T17:15:20.111Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7sLvvyuaKQEKSpSn" /><figcaption>Photo by <a href="https://unsplash.com/@scottrodgerson?utm_source=medium&amp;utm_medium=referral">Scott Rodgerson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Method 1: Using the MySQL Installer</strong><br>-<em>Download MySQL Installer:<br>-Go to the MySQL Community Downloads page.<br>-Select the macOS version and download the DMG archive.</em><br>Install MySQL:<br>-<em>Open the downloaded DMG file.<br>-Follow the installation prompts, clicking “Continue” and “Install” as needed.<br>-Set a strong root password when prompted.<br>-Start MySQL Server:<br>-After installation, go to System Preferences.<br>-Click on the MySQL icon.<br>-Click Start MySQL Server.</em><br><strong>Method 2: Using Homebrew<br>Install Homebrew (if not already installed):</strong><br>Open Terminal and run:<br><em>/bin/bash -c “$(curl -fsSL </em><a href="https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh"><em>https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh</em></a><em>)&quot;</em></p><p>Update Homebrew:<br>Run:<br><em>brew update</em></p><p>Install MySQL:<br>Run:<br><em>brew install mysql</em></p><p>Start MySQL Server:<br>Run:<br><em>brew services start mysql</em></p><p>Secure MySQL Installation:<br>Run:<br><em>mysql_secure_installation</em></p><p>Follow the prompts to set a root password and secure your MySQL installation.<br>Verify Installation<br>Open Terminal:<br>Run:<br><em>mysql -u root -p</em></p><p>Enter the root password you set during installation.<br>Check Databases:<br>Run:</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a1899a41a52" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CSS Cascading Style Sheets]]></title>
            <link>https://medium.com/@rajumanoj/css-cascading-style-sheets-4a9d65b071fb?source=rss-441a1de114d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a9d65b071fb</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[web]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[website]]></category>
            <dc:creator><![CDATA[Rajumanoj]]></dc:creator>
            <pubDate>Wed, 16 Oct 2024 15:21:54 GMT</pubDate>
            <atom:updated>2024-10-16T15:21:54.999Z</atom:updated>
            <content:encoded><![CDATA[<ol><li>CSS stands for Cascading Style Sheets</li><li>CSS is a style sheet language used to control the layout and appearance of web pages</li><li>CSS is separate from HTML, though they often work together</li></ol><h3>Basic Concepts of CSS</h3><ol><li>CSS is based on the box model, which includes padding, border, margin, width, and height properties</li><li>CSS selectors allow you to target specific elements in your HTML document</li><li>CSS properties define the styles applied to selected elements</li></ol><h3>CSS Basic Structure</h3><p>The basic structure of a CSS rule consists of a selector and a declaration block:</p><pre>selector {<br>  property: value;<br>  property: value;<br>}</pre><p>Here’s a breakdown of the components:</p><ul><li><strong>Selector:</strong> Specifies which HTML element(s) the rule applies to</li><li><strong>Declaration block:</strong> Contains one or more declarations enclosed in curly braces</li><li><strong>Declaration:</strong> Consists of a property and a value, separated by a colon</li><li><strong>Property:</strong> The style attribute you want to change</li><li><strong>Value:</strong> The setting you want to apply to the property</li></ul><p>Multiple CSS rules can be combined to create complex styling for web pages.</p><h3>Important CSS Properties</h3><p>Category Properties Box-related properties padding, margin, border Text-related properties color, font-family, font-weight, font-size, line-height Layout-related properties width, height, max-width, max-height, position, z-index, top, right, bottom, left Flexbox properties display, flex, align-items, justify-content Media queries @media</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a9d65b071fb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>