Merge pull request #46 from techdiary-dev/shoaibsharif/delete-scheduled-articles

feat: schedule article deletion

Author: kingRayhan

.gitignore

@@ -32,6 +32,8 @@ yarn-error.log*
 
 # local env files
 .env*.local
+.env
+.dev.vars
 
 # vercel
 .vercel

CLAUDE.md

@@ -0,0 +1,133 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Development Commands
+
+### Development Server
+- `bun run dev` - Start development server with Turbo
+- Open http://localhost:3000 to view the application
+
+### Database Operations
+- `bun run db:generate` - Generate database migrations from schema changes
+- `bun run db:push` - Push schema changes to database
+- `bun run db:studio` - Open Drizzle Studio (database GUI)
+
+### Build & Deployment
+- `bun run build` - Build for production
+- `bun run start` - Start production server
+- `bun run lint` - Run ESLint checks
+
+### Backend Development
+- `bun run play` - Run backend playground script (`src/backend/play.ts`)
+
+## Architecture Overview
+
+### Technology Stack
+- **Frontend**: Next.js 15 (App Router), React 19, TypeScript
+- **Styling**: Tailwind CSS, shadcn/ui components
+- **Backend**: Next.js API routes, Drizzle ORM
+- **Database**: PostgreSQL
+- **Authentication**: GitHub OAuth
+- **Search**: MeilSearch
+- **File Storage**: Cloudinary
+- **State Management**: Jotai, React Hook Form with Zod validation
+
+### Core Directory Structure
+
+#### Frontend (`/src/app/`)
+- Route groups using Next.js App Router:
+  - `(home)` - Main homepage and article feed
+  - `(dashboard-editor)` - Protected dashboard routes
+  - `[username]` - User profile pages
+  - `[username]/[articleHandle]` - Individual article pages
+- API routes in `/api/` for OAuth and development
+
+#### Backend (`/src/backend/`)
+- **Domain Models** (`/domain/`) - Core business logic entities
+- **Persistence** (`/persistence/`) - Database schemas and repositories
+- **Services** (`/services/`) - Business logic actions
+- **Input Validation** - Zod schemas for type-safe inputs
+
+#### Component Architecture (`/src/components/`)
+- **UI Components** - shadcn/ui based design system
+- **Feature Components** - Domain-specific (Editor, Navbar, etc.)
+- **Layout Components** - Page layouts and providers
+
+### Database Schema Architecture
+
+Key entities and their relationships:
+- **Users** - User profiles with social authentication
+- **Articles** - Blog posts with markdown content and metadata
+- **Series** - Article collections/sequences
+- **Comments** - Nested commenting system with resource association
+- **Tags** - Article categorization
+- **Bookmarks** - User content saving
+- **Reactions** - Emoji-based reactions (LOVE, FIRE, WOW, etc.)
+- **User Sessions** - Session management
+- **User Socials** - OAuth provider connections
+
+### Content Management
+- **Rich Text**: Markdoc for markdown parsing and rendering
+- **File Uploads**: Cloudinary integration for images/media
+- **Search**: MeilSearch for full-text search capabilities
+- **Internationalization**: Custom i18n implementation (Bengali/English)
+
+### State Management Patterns
+- **Server State**: Drizzle ORM with PostgreSQL
+- **Client State**: Jotai for global state management
+- **Form State**: React Hook Form with Zod validation
+- **Environment**: Type-safe environment variables with @t3-oss/env-nextjs
+
+## Required Environment Variables
+
+Server-side:
+- `DATABASE_URL` - PostgreSQL connection string
+- `GITHUB_CLIENT_ID` - GitHub OAuth client ID
+- `GITHUB_CLIENT_SECRET` - GitHub OAuth client secret
+- `GITHUB_CALLBACK_URL` - OAuth callback URL
+- `CLOUDINARY_URL` - Cloudinary configuration
+- `MEILISEARCH_ADMIN_API_KEY` - MeilSearch admin API key
+
+Client-side:
+- `NEXT_PUBLIC_MEILISEARCH_API_HOST` - MeilSearch API host URL
+- `NEXT_PUBLIC_MEILISEARCH_SEARCH_API_KEY` - MeilSearch search API key
+
+## Key Features Implementation
+
+### Authentication Flow
+- GitHub OAuth integration via `/api/auth/github`
+- User sessions managed in `userSessionsTable`
+- Social provider connections in `userSocialsTable`
+
+### Content Creation
+- Rich markdown editor with drag-and-drop support
+- Image upload and optimization via Cloudinary
+- Article series management for content organization
+- Tag-based categorization system
+
+### Search Implementation
+- MeilSearch for full-text search across articles
+- Search configuration and indexing handled in backend services
+- Client-side search interface with real-time results
+
+### Community Features
+- Nested commenting system with resource association
+- Emoji-based reactions (LOVE, FIRE, WOW, etc.)
+- User following and bookmarking functionality
+- Social sharing and user profiles
+
+## Development Workflow
+
+1. Database changes require running `npm run db:generate` followed by `npm run db:push`
+2. Backend logic testing can be done via `npm run play` playground script
+3. Type safety is enforced through Zod schemas for all inputs
+4. UI components follow shadcn/ui patterns and conventions
+5. All forms use React Hook Form with Zod validation schemas
+
+## Special Considerations
+
+- **Bengali Language Support**: Custom font loading (Kohinoor Bangla) and i18n
+- **SEO Optimization**: Dynamic sitemaps, Open Graph tags, and schema markup
+- **Performance**: Next.js Image optimization, bundle splitting, and caching
+- **Security**: Input validation via Zod, secure OAuth flow, environment variable validation

CLOUDFLARE_CRON_SETUP.md

@@ -0,0 +1,143 @@
+# Cloudflare Cron Setup for Article Cleanup
+
+This document explains how to set up Cloudflare Cron Triggers to automatically delete expired articles.
+
+## Overview
+
+The system consists of:
+1. **API Route**: `/api/cron/cleanup-articles` - Handles the actual cleanup logic
+2. **Cloudflare Worker**: `src/workers/cron-worker.ts` - Cron trigger that calls the API
+3. **Backend Service**: `src/backend/services/article-cleanup-service.ts` - Database operations
+
+## Setup Instructions
+
+### 1. Install Wrangler CLI
+
+```bash
+npm install -g wrangler
+# or
+bun install -g wrangler
+```
+
+### 2. Authenticate with Cloudflare
+
+```bash
+wrangler login
+```
+
+### 3. Configure Environment Variables
+
+Update `wrangler.toml` with your actual domain:
+
+```toml
+[vars]
+CRON_TARGET_URL = "https://your-actual-domain.com/api/cron/cleanup-articles"
+```
+
+### 4. Set Secret (Optional but Recommended)
+
+For additional security, set a secret that the cron worker will send:
+
+```bash
+wrangler secret put CRON_SECRET
+# Enter your secret when prompted
+```
+
+Then add the same secret to your Next.js environment:
+
+```bash
+# .env.local
+CRON_SECRET=your-secret-key
+```
+
+### 5. Deploy the Cron Worker
+
+```bash
+wrangler deploy src/workers/cron-worker.ts
+```
+
+### 6. Verify Cron Schedule
+
+The cron is configured to run daily at 2:00 AM UTC. You can modify the schedule in `wrangler.toml`:
+
+```toml
+[triggers]
+crons = [
+  "0 2 * * *"  # Daily at 2:00 AM UTC
+]
+```
+
+Other common schedules:
+- `"0 * * * *"` - Every hour
+- `"0 2 * * 0"` - Every Sunday at 2:00 AM
+- `"0 2 1 * *"` - First day of every month at 2:00 AM
+
+### 7. Monitor Cron Executions
+
+You can monitor executions in the Cloudflare dashboard:
+1. Go to Workers & Pages
+2. Select your worker
+3. Check the "Logs" tab for execution logs
+
+## Manual Testing
+
+You can test the cleanup manually by calling the API directly:
+
+```bash
+# GET request for testing
+curl https://your-domain.com/api/cron/cleanup-articles
+
+# POST request (mimics cron call)
+curl -X POST https://your-domain.com/api/cron/cleanup-articles \
+  -H "Content-Type: application/json" \
+  -H "x-cron-secret: your-secret-key"
+```
+
+## How It Works
+
+1. **Article Scheduling**: Articles can be scheduled for deletion by setting the `delete_scheduled_at` field
+2. **Cron Trigger**: Cloudflare runs the worker daily at 2:00 AM UTC
+3. **API Call**: Worker calls `/api/cron/cleanup-articles` endpoint
+4. **Cleanup Logic**: Service finds articles where `delete_scheduled_at < current_time` and deletes them
+5. **Response**: API returns count of deleted articles and their details
+
+## Database Schema
+
+Articles are scheduled for deletion using the `delete_scheduled_at` timestamp field:
+
+```sql
+-- Example of scheduling an article for deletion in 30 days
+UPDATE articles 
+SET delete_scheduled_at = NOW() + INTERVAL '30 days'
+WHERE id = 'article-id';
+```
+
+## Additional Functions
+
+The cleanup service also provides:
+- `scheduleArticleForDeletion(articleId, deleteAt)` - Schedule an article
+- `cancelScheduledDeletion(articleId)` - Cancel scheduled deletion  
+- `getScheduledArticles()` - Get all articles scheduled for deletion
+
+## Troubleshooting
+
+### Common Issues
+
+1. **404 Error**: Check that your `CRON_TARGET_URL` is correct
+2. **401 Unauthorized**: Verify `CRON_SECRET` matches between worker and API
+3. **500 Error**: Check database connection and permissions
+4. **No Articles Deleted**: Verify articles have `delete_scheduled_at` set and are past due
+
+### Debugging
+
+1. Check Cloudflare Worker logs in the dashboard
+2. Check your Next.js application logs
+3. Test the API endpoint manually
+4. Verify database records with `getScheduledArticles()`
+
+## Security Considerations
+
+1. Use `CRON_SECRET` to verify requests come from your worker
+2. Consider rate limiting the endpoint
+3. Log all cleanup operations for audit trails
+4. Ensure proper database permissions for the cleanup operations

package.json

@@ -10,7 +10,9 @@
     "db:generate": "npx drizzle-kit generate",
     "db:push": "npx drizzle-kit push",
     "db:studio": "npx drizzle-kit studio",
-    "play": "npx tsx ./src/backend/play.ts"
+    "play": "npx tsx ./src/backend/play.ts",
+    "wrangler:dev": "wrangler dev",
+    "cf-typegen": "wrangler types"
   },
   "dependencies": {
     "@aws-sdk/client-s3": "^3.828.0",
@@ -80,6 +82,7 @@
     "prettier": "^3.5.3",
     "tailwindcss": "^4.1.1",
     "tsx": "^4.19.3",
-    "typescript": "^5.8.2"
+    "typescript": "^5.8.2",
+    "wrangler": "^4.20.0"
   }
 }

src/app/api/cron/cleanup-articles/route.ts

@@ -0,0 +1,52 @@
+import { NextRequest, NextResponse } from "next/server";
+import { deleteExpiredArticles } from "@/backend/services/article-cleanup-service";
+
+export async function POST(request: NextRequest) {
+  try {
+    // Verify the request is from Cloudflare Cron (optional security measure)
+    const cronSecret = request.headers.get("x-cron-secret");
+    if (process.env.CRON_SECRET && cronSecret !== process.env.CRON_SECRET) {
+      return NextResponse.json({ error: "Unauthorized" }, { status: 401 });
+    }
+
+    // Execute the cleanup
+    const result = await deleteExpiredArticles();
+
+    return NextResponse.json({
+      success: true,
+      message: `Successfully deleted ${result.deletedCount} expired articles`,
+      deletedCount: result.deletedCount,
+    });
+  } catch (error) {
+    console.error("Error in cleanup-articles cron job:", error);
+    return NextResponse.json(
+      {
+        error: "Internal server error",
+        message: error instanceof Error ? error.message : "Unknown error",
+      },
+      { status: 500 }
+    );
+  }
+}
+
+// Also support GET for manual testing
+export async function GET() {
+  try {
+    const result = await deleteExpiredArticles();
+
+    return NextResponse.json({
+      success: true,
+      message: `Successfully deleted ${result.deletedCount} expired articles`,
+      count: result.deletedCount,
+    });
+  } catch (error) {
+    console.error("Error in cleanup-articles manual execution:", error);
+    return NextResponse.json(
+      {
+        error: "Internal server error",
+        message: error instanceof Error ? error.message : "Unknown error",
+      },
+      { status: 500 }
+    );
+  }
+}

src/backend/services/article-cleanup-service.ts

@@ -0,0 +1,31 @@
+"use server";
+import { and, lt, neq } from "sqlkit";
+import { persistenceRepository } from "../persistence/persistence-repositories";
+import { handleActionException } from "./RepositoryException";
+
+/**
+ * Delete articles that have passed their scheduled deletion time
+ */
+export async function deleteExpiredArticles() {
+  try {
+    const currentTime = new Date();
+
+    const deleteResult = await persistenceRepository.article.delete({
+      where: and(
+        neq("delete_scheduled_at", null),
+        lt("delete_scheduled_at", currentTime)
+      ),
+    });
+
+    console.log(
+      `Successfully deleted ${deleteResult?.rowCount} expired articles`
+    );
+
+    return {
+      deletedCount: deleteResult?.rowCount || 0,
+    };
+  } catch (error) {
+    console.error("Error deleting expired articles:", error);
+    throw handleActionException(error);
+  }
+}