Merge branch 'CodeChefVIT:staging' into staging

Author: abhitrueprogrammer

.dockerignore

@@ -0,0 +1,6 @@
+node_modules
+npm-debug.log
+.DS_Store
+.git
+.gitignore
+.env

.env.example

@@ -24,4 +24,9 @@ NEXT_PUBLIC_CRYPTO_SECRET=""
 KV_URL=""
 KV_REST_API_URL=""
 KV_REST_API_TOKEN=""
-KV_REST_API_READ_ONLY_TOKEN=""
+KV_REST_API_READ_ONLY_TOKEN=""
+SERVER_URL=""
+# Google Sheets Integration
+GOOGLE_CLIENT_EMAIL=""
+GOOGLE_PRIVATE_KEY=""
+SHEET_ID=""

.gitignore

@@ -34,10 +34,14 @@ yarn-error.log*
 # local env files
 # do not commit any .env files to git, except for the .env.example file. https://create.t3.gg/en/usage/env-variables#using-environment-variables
 .env
+.env.lcal
 .env*.local
-
+.env.prod
 # vercel
 .vercel
-
+.env.staging
 # typescript
 *.tsbuildinfo
+
+# vscode
+./vscode

.npmrc

@@ -0,0 +1 @@
+public-hoist-pattern[]=pdfjs-dist

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[email protected].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

Dockerfile

@@ -1,20 +1,58 @@
-# Step 1: Specify the base image
-FROM node:22
+# Step 1: Build stage
+FROM node:23-alpine AS builder
 
-# Step 2: Set the working directory inside the container
+# Install dependencies required for building native modules
+RUN apk add --no-cache \
+    python3 \
+    make \
+    g++ \
+    pkgconfig \
+    pixman-dev \
+    cairo-dev \
+    pango-dev \
+    glib-dev \
+    jpeg-dev \
+    giflib-dev
+
+# Install pnpm globally
+RUN npm install -g pnpm
+
+# Set the working directory
 WORKDIR /app
 
-# Step 3: Copy package.json and package-lock.json files
-COPY package*.json ./
+# Copy package.json and pnpm-lock.yaml
+COPY package.json pnpm-lock.yaml ./
 
-# Step 4: Install dependencies
-RUN npm install
+# Install dependencies using pnpm
+RUN pnpm install --frozen-lockfile
 
-# Step 5: Copy the rest of the application code
+# Copy the rest of the application code
 COPY . .
 
-# Step 6: Expose the port the application runs on
+# Build the application
+RUN pnpm run build
+
+# Step 2: Production stage
+FROM node:23-alpine
+
+# Install pnpm globally
+RUN npm install -g pnpm
+
+# Set the working directory
+WORKDIR /app
+
+# Set NODE_ENV to production
+ENV NODE_ENV=production
+
+# Copy only the built application and necessary files from the builder stage
+COPY --from=builder /app/package.json ./
+COPY --from=builder /app/pnpm-lock.yaml ./
+COPY --from=builder /app/node_modules ./node_modules
+COPY --from=builder /app/.next ./.next
+COPY --from=builder /app/public ./public
+
+# Expose the port the application runs on
 EXPOSE 3000
 
-# Step 7: Define the command to run the application
-CMD ["npm","run","dev"]
+# Define the command to start the application
+CMD ["pnpm", "start"]

README.md

@@ -7,7 +7,8 @@
 > <p>Prepare to excel in your CATs and FATs with CodeChef-VIT's dedicated repository of past exam papers. Access key resources to review concepts, tackle challenging questions, and familiarize yourself with exam patterns. Boost your confidence, sharpen your strategy, and get ready to ace your exams!</p>
 
 ## 🌐 Deploy
-[https://papers.codechefvit.com/](https://papers.codechefvit.com/)
+
+[https://papers.codechefvit.com](https://papers.codechefvit.com/)
 
 ## ⚙️ Tech Stack:
 
@@ -62,6 +63,28 @@ To start your development server run:
 pnpm dev
 ```
 
+## 🐳 Using Docker
+
+To run the application using Docker, follow these steps:
+
+1. **Build the Docker Image**:
+
+   ```bash
+   docker build -t papers-codechef .
+   ```
+
+2. **Run the Docker Container**:
+
+   ```bash
+   docker run -p 3000:3000 --env-file .env papers-codechef
+   ```
+
+3. **Using Docker Compose**:
+   If you prefer `docker-compose`, ensure the `docker-compose.yml` file is configured, then run:
+   ```bash
+   docker-compose up
+   ```
+
 Before getting started, please ensure that the .env file is properly configured. The .env.example file has been provided for your reference, with examples of environment variables to be listed.
 
 ## License

docker-compose.yml

@@ -0,0 +1,7 @@
+services:
+  app:
+    build: .
+    ports:
+      - "3000:3000"
+    env_file:
+      - .env.local

next.config.js

@@ -6,15 +6,16 @@ await import("./src/env.js");
 
 /** @type {import("next").NextConfig} */
 const config = {
+  swcMinify: false,
+
   images: {
     domains: ["res.cloudinary.com"],
   },
-  webpack: (
-    config, options
-  ) => {
+  webpack: (config, options) => {
+    config.resolve.alias.canvas = false;
     config.module.rules.push({
       test: /\.node/,
-      use: 'raw-loader',
+      use: "raw-loader",
     });
     return config;
   },

ongoing-papers.ts

@@ -1,54 +1,38 @@
-import { type IPaper } from "@/interface";
+import { type IUpcomingPaper } from "@/interface";
 
-const papers: IPaper[] = [
+const papers: IUpcomingPaper[] = [
   {
     _id: "6708fd8002a75017a4f08759",
-    finalUrl:
-      "https://res.cloudinary.com/dtorpaj1c/image/upload/v1728642405/papers/orbppimhujcijj2ywhvm.pdf",
-    thumbnailUrl:
-      "https://res.cloudinary.com/dtorpaj1c/image/upload/w_400,h_400,c_fill/v1728642405/papers/orbppimhujcijj2ywhvm.jpg",
     subject: "Discrete Mathematics and Graph Theory [BMAT205L]",
-    slot: "A2",
-    year: "2023",
-    exam: "CAT-2",
-    semester: "Fall Semester",
-    campus: "Vellore",
+    slots: ["A2", "B2"],
   },
   {
     _id: "670980523ec3fdad83b2d211",
-    finalUrl:
-      "https://res.cloudinary.com/dtorpaj1c/image/upload/v1728675912/papers/lvtypsfdtref5mjskley.pdf",
-    thumbnailUrl:
-      "https://res.cloudinary.com/dtorpaj1c/image/upload/w_400,h_400,c_fill/v1728675912/papers/lvtypsfdtref5mjskley.jpg",
     subject: "Compiler Design [BCSE307L]",
-    slot: "A2",
-    year: "2024",
-    exam: "CAT-2",
-    semester: "Fall Semester",
-    campus: "Vellore",
+    slots: ["C1", "D1"],
   },
   {
     _id: "670a105e6272bcf9da4e2362",
 
-    finalUrl:
+    final_url:
       "https://res.cloudinary.com/dtorpaj1c/image/upload/v1728712773/papers/ifkrnjgwdudtev9rxpki.pdf",
-    thumbnailUrl:
+    thumbnail_url:
       "https://res.cloudinary.com/dtorpaj1c/image/upload/w_400,h_400,c_fill/v1728712773/papers/ifkrnjgwdudtev9rxpki.jpg",
     subject: "Complex Variables and Linear Algebra [BMAT201L]",
-    slot: "A1",
+    slots: ["A1", "B1"],
     year: "2023",
     exam: "CAT-2",
     semester: "Fall Semester",
     campus: "Vellore",
   },
   {
     _id: "67097e7b3ec3fdad83b2d205",
-    finalUrl:
+    final_url:
       "https://res.cloudinary.com/dtorpaj1c/image/upload/v1728675439/papers/pyyqotz1mzuh2wmq1k9s.pdf",
-    thumbnailUrl:
+    thumbnail_url:
       "https://res.cloudinary.com/dtorpaj1c/image/upload/w_400,h_400,c_fill/v1728675439/papers/pyyqotz1mzuh2wmq1k9s.jpg",
     subject: "Computer Networks [BCSE308L]",
-    slot: "C2",
+    slots: ["C2", "D2"],
     year: "2023",
     exam: "CAT-2",
     semester: "Fall Semester",