Skip to content
This repository was archived by the owner on Jun 20, 2026. It is now read-only.

Latest commit

 

History

History
103 lines (73 loc) · 3.93 KB

README.md

File metadata and controls

103 lines (73 loc) · 3.93 KB

To the App - (might take ~30 secs to load up because of free tier limitations)

A new version of the FastAPI router is being built (from scratch on a new repo) to address the package directives that have not been followed here. There are many and hence it warrants new development. The current code structure will be followed.

The frontend will be recreated in Angular SPA (new repo) interfacing directly with fastapi without a server component.

This repo will be archived soon once the above actions are completed.

A Node.js/Express server was planned to replace this simple backend router which might take place later.

Task Management Application

A full-stack task management application with a Next.js frontend, FastAPI backend, and PostgreSQL database.

🚀 Production Stack

  • Frontend: Next.js 16 (angular + express stack wip)
  • Backend: FastAPI + Python 3.13 (not really necessary but aids in learning)
  • Database: PostgreSQL

🏗️ Architecture (subject to change based on credit balance)

The whole stack is to be deployed to AWS. PostgreSQL Aurora DB + EC2 Instance

 Vercel    ->    Render    ->    Supabase
(NextJS)        (FastAPI)      (PostgreSQL)

🛠️ Local Development

Prerequisites

  • Docker & Docker Compose
  • Node.js 21
  • Python 3.12

Quick Start

  1. Clone the repository

    git clone git@github.com:MriteshAdak/Task_Manager.git
    cd Task_Manager
  2. Start with Docker Compose

    docker compose up

🔧 Configuration

Environment Variables

Backend (Railway):

  • DB_USER - PostgreSQL username
  • DB_PASSWORD - PostgreSQL password
  • DB_HOST - PostgreSQL host
  • DB_PORT - PostgreSQL port
  • DB_NAME - PostgreSQL database name
  • UI_ORIGINS - Comma-separated list of allowed UI origins for CORS

Frontend (Vercel):

  • BACKEND_URL - API URL for server-side requests

Quick Deploy Steps

  1. Setup Supabase → Collect DB_USER, DB_PASSWORD, DB_HOST, DB_PORT, DB_NAME
  2. Deploy to Render → Set the DB_* vars and UI_ORIGINS
  3. Deploy to Vercel → Set BACKEND_URL to Render URL
  4. Update CORS → Add Vercel URL to Render's UI_ORIGINS

🧪 API Endpoints

Method Endpoint Description
GET /health Health check
GET /tasks List all tasks
GET /tasks/{id} Retrieve one task
POST /tasks Create a task
PUT /tasks/{id} Update a task
DELETE /tasks/{id} Delete a task

Full API documentation available at /docs when running the backend locally.

🔒 Security

  • Environment variables for sensitive data
  • CORS protection on the backend
  • Server-side API proxy to hide backend URLs
  • Secure database connections with SSL
  • Non-root Docker user

🗺 Future Roadmap

  • Service Split: Decouple modules into a standalone internal service.

NOTE: This application has no practical purpose other than learning different stacks and transitioning from badly designed system (intentional) to a structured application design. Also, further developments will be done on dedicated repositories cause the componenets are decoupled enough. This repository will be the discarded/deprecated and the components will be in their own repositories for better management.

  • NextJS: a server component to replace the backend entirely in Next.js
  • User-Task Mapping: Transition Postgres schema to support user_id foreign keys including the interfaces in the source code.
  • Angular: Angular FrontEnd for learning purposes.
  • SpringBoot: Write the backend/router in Spring Boot for learning purposes.
  • MongoDB: Adding MongoDB in the mix for learning purposes. Additional services will be created. Either be limited to storing telemetry (auditing) or the core collections/tables.