'idempotency'

Author: SuryaKTiwari11

.github/README.md

@@ -0,0 +1,77 @@
+# GitHub Actions for Learning
+
+## What is GitHub Actions?
+
+GitHub Actions is a CI/CD (Continuous Integration/Continuous Deployment) system built into GitHub. Think of it as a robot that automatically runs tasks when you push code.
+
+## Why learn this as a student?
+
+1. **Industry Standard**: Every company uses CI/CD
+2. **Portfolio Value**: Shows you understand professional workflows
+3. **Prevents Bugs**: Catches errors before they reach main branch
+4. **Free Learning**: GitHub gives you free compute time to experiment
+
+## The Three Workflows Explained:
+
+### 1. CI Pipeline (ci.yml)
+
+**Purpose**: Test your code automatically
+**When it runs**: Every time you push code or create a pull request
+**What it does**:
+
+- Installs your dependencies
+- Runs your tests
+- Builds your frontend
+- Tests Docker builds
+- If ANY step fails, it marks the commit as "broken"
+
+### 2. CD Pipeline (cd.yml)
+
+**Purpose**: Deploy your code (COMMENTED OUT FOR LEARNING)
+**Status**: Not needed yet since you're not deploying anywhere
+**What it would do**: Push your app to a server when tests pass
+
+### 3. PR Checks (pr-checks.yml)
+
+**Purpose**: Validate pull requests before merging
+**When it runs**: When you open a pull request
+**What it does**: Same as CI but adds a comment to your PR
+
+## For Learning Phase:
+
+**Keep**: CI Pipeline - This will teach you professional testing habits
+**Comment Out**: CD Pipeline - You don't need deployment yet
+**Keep**: PR Checks - Good for team projects or practice
+
+## How to use this:
+
+1. Push your code to GitHub
+2. Go to your repo -> Actions tab
+3. Watch the workflows run
+4. See green checkmarks (pass) or red X (fail)
+5. Click on failed jobs to see what went wrong
+6. Fix the issues and push again
+
+## Learning Benefits:
+
+- Forces you to write tests
+- Teaches you Docker
+- Shows you industry practices
+- Builds good coding habits
+- Looks professional on your GitHub profile
+
+## Simple Commands:
+
+```bash
+# Test locally first
+cd backend && npm test
+
+# Then push
+git add .
+git commit -m "your changes"
+git push
+
+# GitHub Actions will automatically test your code
+```
+
+This setup will make you a better developer by forcing good practices.

.github/workflows/cd.yml

@@ -0,0 +1,26 @@
+
+#
+# This file is commented out because you're in learning mode.
+# Uncomment everything below when you're ready to deploy to production.
+#
+# What this would do:
+# - Run only when CI tests pass
+# - Build production Docker images
+# - Deploy your app to a server
+#
+# For now, focus on the CI pipeline (ci.yml) which tests your code.
+
+# Uncomment the lines below when ready for deployment:
+
+# name: CD Pipeline
+# on:
+#   push:
+#     branches: [ main ]
+# jobs:
+#   deploy:
+#     runs-on: ubuntu-latest
+#     steps:
+#     - name: Checkout code
+#       uses: actions/checkout@v4
+#     - name: Deploy app
+#       run: echo "Deploying to production..."

.github/workflows/ci.yml

@@ -0,0 +1,84 @@
+name: CI Pipeline
+
+# When to run this workflow
+on:
+    push:
+        branches: [main, develop]
+    pull_request:
+        branches: [main]
+
+jobs:
+    # Test the backend
+    test-backend:
+        runs-on: ubuntu-latest
+
+        steps:
+            # Step 1: Get the code from GitHub
+            - name: Checkout code
+              uses: actions/checkout@v4
+
+            # Step 2: Install Node.js
+            - name: Setup Node.js
+              uses: actions/setup-node@v4
+              with:
+                  node-version: "18"
+                  cache: "npm"
+                  cache-dependency-path: backend/package-lock.json
+
+            # Step 3: Install dependencies
+            - name: Install backend dependencies
+              run: |
+                  cd backend
+                  npm ci
+
+            # Step 4: Run tests (THIS IS THE IMPORTANT PART)
+            - name: Run backend tests
+              run: |
+                  cd backend
+                  npm test
+
+    # Build and test frontend
+    test-frontend:
+        runs-on: ubuntu-latest
+
+        steps:
+            - name: Checkout code
+              uses: actions/checkout@v4
+
+            - name: Setup Node.js
+              uses: actions/setup-node@v4
+              with:
+                  node-version: "18"
+                  cache: "npm"
+                  cache-dependency-path: frontend/package-lock.json
+
+            - name: Install frontend dependencies
+              run: |
+                  cd frontend
+                  npm ci
+
+            # Check for code style issues
+            - name: Lint frontend code
+              run: |
+                  cd frontend
+                  npm run lint
+
+            # Make sure frontend builds without errors
+            - name: Build frontend
+              run: |
+                  cd frontend
+                  npm run build
+
+    # Optional: Test Docker builds (comment out if you don't want this yet)
+    docker-build:
+        runs-on: ubuntu-latest
+        needs: [test-backend, test-frontend]
+
+        steps:
+            - name: Checkout code
+              uses: actions/checkout@v4
+
+            - name: Test Docker build
+              run: |
+                  docker-compose build
+                  echo "Docker images built successfully"

.github/workflows/pr-checks.yml

@@ -0,0 +1,47 @@
+name: PR Checks
+
+# Run on pull requests
+on:
+    pull_request:
+        branches: [main, develop]
+
+jobs:
+    pr-checks:
+        runs-on: ubuntu-latest
+
+        steps:
+            - name: Checkout code
+              uses: actions/checkout@v4
+
+            - name: Setup Node.js
+              uses: actions/setup-node@v4
+              with:
+                  node-version: "18"
+
+            # Check backend
+            - name: Install and test backend
+              run: |
+                  cd backend
+                  npm ci
+                  npm test
+
+            # Check frontend
+            - name: Install and build frontend
+              run: |
+                  cd frontend
+                  npm ci
+                  npm run lint
+                  npm run build
+
+            # Add a comment to PR with results
+            - name: Comment PR
+              if: always()
+              uses: actions/github-script@v7
+              with:
+                  script: |
+                      github.rest.issues.createComment({
+                        issue_number: context.issue.number,
+                        owner: context.repo.owner,
+                        repo: context.repo.repo,
+                        body: '🤖 **PR Checks Complete!**\n\n✅ Tests passed\n✅ Build successful\n✅ Ready for review!'
+                      })

backend/Dockerfile

@@ -0,0 +1,20 @@
+# Use Node.js official image
+FROM node:18-alpine
+
+# Set working directory inside container
+WORKDIR /app
+
+# Copy package.json and package-lock.json (if available)
+COPY package*.json ./
+
+# Install dependencies
+RUN npm install
+
+# Copy the rest of the application code
+COPY . .
+
+# Expose the port your app runs on (adjust if different)
+EXPOSE 3000
+
+# Command to run your application
+CMD ["npm", "start"]

backend/configuration/passport.js

@@ -7,9 +7,7 @@ import { configDotenv } from "dotenv";
 import crypto from "crypto";
 
 configDotenv();
-const randomPass = () => {
-  return crypto.randomBytes(16).toString("hex");
-};
+
 
 passport.use(
   "google",

backend/configuration/s3Config.js

@@ -1,38 +1,16 @@
-import {
-  S3Client,
-  CreateBucketCommand,
-  HeadBucketCommand,
-} from "@aws-sdk/client-s3";
+import { S3Client } from "@aws-sdk/client-s3";
+import dotenv from "dotenv";
+dotenv.config();
+
+const AWS_REGION = process.env.AWS_REGION || "ap-south-1";
+const BUCKET_NAME = process.env.AWS_BUCKET_NAME || "vermaco123";
 
 const s3Client = new S3Client({
-  endpoint: process.env.AWS_ENDPOINT_URL || "http://localhost:4566",
+  region: AWS_REGION,
   credentials: {
-    accessKeyId: process.env.AWS_ACCESS_KEY_ID || "test",
-    secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY || "test",
+    accessKeyId: process.env.AWS_ACCESS_KEY_ID,
+    secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY,
   },
-  region: process.env.AWS_REGION || "us-east-1",
-  forcePathStyle: true, //!needed for localstack
 });
 
-const BUCKET_NAME = process.env.S3_BUCKET_NAME || "employee-documents";
-
-async function setupS3() {
-  try {
-    await s3Client.send(new HeadBucketCommand({ Bucket: BUCKET_NAME }));
-    console.log(`Bucket ${BUCKET_NAME} already exists.`);
-    // Bucket exists
-    //!this means that the bucket already exists
-  } catch (error) {
-    if (error.name === "NotFound" || error.$metadata?.httpStatusCode === 404) {
-      await s3Client.send(new CreateBucketCommand({ Bucket: BUCKET_NAME }));
-      console.log(`Bucket ${BUCKET_NAME} created successfully.`);
-      // Bucket created
-      //!this means the bucket does not exist, so we create it
-    } else {
-      console.error("S3 setup failed:", error.message);
-      // Make sure LocalStack is running
-    }
-  }
-}
-
-setupS3();
+export { s3Client, BUCKET_NAME };