online-ide

KO | EN

gitlite — search

#hacktoberfest #typescript #go #golang #rust #deep-learning #linux #java #nodejs #cli #vue #security #ios #mcp

(★ 31)

Leetcode like platform to practice coding

online-ide Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Online IDE

Leetcode like platform to practice logic based coding problems. Built using Express.js, React.js, Postgres, and Docker containers for code execution.

![Screenshot](https://raw.githubusercontent.com/MananGandhi1810/online-ide/main/assets/screenshot.png)

## Table of Contents

- [Features](#features)
- [Tech Stack](#tech-stack)
- [How It Works](#how-it-works)
- [Setup](#setup)
    - [Using Docker Compose](#using-docker-compose)
    - [Running Backend and Frontend Separately](#running-backend-and-frontend-separately)
- [Contributing](#contributing)

## Features

- JWT Based User Authentication
    - Register
    - Login
    - Email token verification
    - Forgot password with OTP
- Code Editor
    - Syntax Highlighting (with Shiki.js)
    - 4 Languages Supported (Python, C, C++, Java)
    - Problem Statements rendered as Markdown, with support for code blocks
    - Sample Test Cases for each problem with expected output
    - Custom testcases can be set by the user
    - Custom starter code for each problem statement and language
- Sandboxed Code Execution
    - Docker container for each code execution
    - Limit time used by code
- Test code against sample test cases before submission
- Verify output against hidden test cases
- Persist code to local storage
- AI Assistant
    - LLaMA will provide hints for the problem statement, with access to the code written by the user as context
    - Streaming response from the AI Assistant, for a more interactive experience
- Points
    - +10 if the user solves a problem statement in the first submission
    - +5 if the user solves a problem statement in more than one submission
    - no points awarded if user solves a problem statement correctly more than once
- Leaderboard ranking based on points
- User Profile
    - GitHub-like submission graph
    - Total submissions
    - Points earned
    - Problems solved
- Editorials for each problem statement
    - Markdown rendered editorials
    - Code blocks in editorials
    - User can submit editorials after solving the problem statement
- Critical endpoints are rate limited to prevent abuse
- Analytics using PostHog
    - Track user interactions on the platform
- View Past Submissions
    - View code submitted for each problem statement

## Tech Stack

- Express.js (Backend + Execution Worker)
- Python (for code execution on the container)
- React.js (Frontend)
- Redis (for internal messaging, storing OTPs, saving code execution results)
- PostgreSQL (with Prisma ORM)
- Docker (with docker-compose)
- Dockerode (for managing docker containers)
- Resend (for sending emails)
- Shadcn/UI (for frontend components)
- Shiki.js with Monaco Editor (for code editing with syntax highlighting)
- Meta LLaMA 4 17b (CloudFlare Workers AI)
- GitHub Actions (for CI/CD)
- PostHog (for analytics)

## How it works

![Diagram](https://raw.githubusercontent.com/MananGandhi1810/online-ide/main/assets/flow-diagram.png)

1. The user writes code in the frontend and clicks execute or submit.
2. The frontend sends the request to the backend server.
3. The backend stores user and code data in PostgreSQL.
4. The backend publishes the execution job to Redis PubSub.
5. The code execution worker consumes the queued job.
6. The worker starts a Docker container and runs the submitted code with the provided test cases.
7. The worker records the execution result, execution time, and success or failure status back in PostgreSQL.

This setup keeps the web request fast, isolates code execution inside containers, and lets the backend and worker communicate asynchronously through Redis.

## Setup

You can either use the docker-compose file to run the project or run the backend and frontend separately.

### Using Docker Compose

- Clone the repository
- Copy the `.env.example` file to `.env` and fill in the required values in both `frontend/` and `backend/` directories.
- Run `docker compose up` in the root directory
- The project will be running on `localhost:8000`

### Running Backend and Frontend Separately

> [!NOTE]
> You will still need to have Docker installed on your system.

- Clone the repository
- Copy the `.env.example` file to `.env` and fill in the required values in both `frontend/` and `backend/` directories.
- Run Redis and PostgreSQL using Docker
    - Run `docker compose up redis postgresql -d` in the root directory
- Run the backend server
    - Navigate to the `backend` directory
    - Run `npm install`
    - Run `npm run dev`
- The backend server will be running on `localhost:3000`
- Run the frontend server
    - Navigate to the `frontend` directory
    - Run `npm install`
    - Run `npm start`
- The project will be running on `localhost:5173`

## Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change. For more details, please refer to the [CONTRIBUTING.md](CONTRIBUTING.md) file.

online-ide

online-ide Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

online-ide

online-ide Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README