Installation Guide

The CPU Scheduling Algorithms Simulator offers multiple deployment options to fit your needs. Choose from instant cloud access, local file execution, or containerized Docker deployment.

Requirements

Minimal Requirements

Modern web browser (Chrome, Edge, Firefox, or Safari)
No Node.js installation needed
No database required
No backend server needed

Optional Tools

Docker Desktop (for containerized deployment)
Git (for cloning the repository)
Web server (for custom hosting)

This is a 100% frontend application. All computation happens in the browser, making installation incredibly simple.

Installation Methods

Cloud Demo (Instant)
Local Files
Docker

Option 1: Access the Live Demo

The fastest way to use the simulator - no installation required!Live URL: https://planificacion-app-rcl8.onrender.com

Open Your Browser

Launch any modern web browser on your device.

Visit the Demo

Navigate to: https://planificacion-app-rcl8.onrender.com

Start Simulating

The simulator loads instantly. Select an algorithm and begin!

Best for: Quick testing, demonstrations, and classroom use

The demo is hosted on Render’s free tier. Initial load may take 30-60 seconds if the service was idle.

Option 2: Run Local HTML Files

Run the simulator directly from your filesystem without any server.

Clone the Repository

Download the project from GitHub:

git clone https://github.com/SebastianMoreno0911/AlgoritmosPlanificacion.git

Or download the ZIP file from the repository and extract it.

Navigate to the Project

Open your file explorer and go to:

AlgoritmosPlanificacion/Planificacion/

Open index.html

Double-click index.html to open it in your default browser.Or right-click and select Open With to choose a specific browser.

Verify

You should see the algorithm selection screen with five buttons:

FIFO
SJF
Round Robin
Prioridad
MLFQ

Best for: Offline use, local development, and environments without internet access

Project Structure

AlgoritmosPlanificacion/
├── Planificacion/
│   ├── css/
│   │   └── styles.css          # Custom styling
│   ├── JS/
│   │   ├── algoritmos.js       # Algorithm implementations
│   │   ├── ui.js               # UI controls and visualization
│   └── index.html              # Main entry point
├── Dockerfile                   # Container configuration
├── README.md
└── .gitignore

Some browsers may restrict local file access. If you encounter CORS errors, use the Docker method or access via http://localhost with a local web server.

Option 3: Run with Docker

Deploy the simulator in an isolated container for consistent, reproducible environments.

Install Docker

Ensure Docker Desktop is installed on your system:

Clone the Repository

git clone https://github.com/SebastianMoreno0911/AlgoritmosPlanificacion.git
cd AlgoritmosPlanificacion/Planificacion

Build the Docker Image

Create the container image:

docker build -t algoritmos-planificacion .

This uses the included Dockerfile:

FROM nginx:alpine
COPY . /usr/share/nginx/html
EXPOSE 80

The image is lightweight, based on Alpine Linux with Nginx serving static files.

Run the Container

Start the simulator on port 8080:

docker run -p 8080:80 algoritmos-planificacion

The -p 8080:80 flag maps your local port 8080 to the container’s port 80.

Access the Simulator

Open your browser and navigate to:

http://localhost:8080

The simulator should load immediately.

Best for: Production deployments, academic evaluation, and consistent testing environments

Docker Commands

docker build -t algoritmos-planificacion .

Custom Port

To use a different port, modify the -p flag:

# Run on port 3000
docker run -p 3000:80 algoritmos-planificacion

# Access at http://localhost:3000

Verification Steps

After installation, verify the simulator is working correctly:

Check Algorithm Selection

You should see five colored buttons on the landing page:

FIFO (blue)
SJF (green)
Round Robin (yellow/orange)
Prioridad (red)
MLFQ (dark red)

Test Basic Simulation

Click FIFO
Enter 2 for number of processes
Click Continue
Enter process data:
- Process 1: Arrival 0, CPU 3
- Process 2: Arrival 1, CPU 2
Click Simular

Verify Results Display

You should see:

Results table with metrics for P1 and P2
Total execution time: 5
Simulation controls (Iniciar, Pausar, Reiniciar, Volver al inicio)

Test Animation

Click ▶ Iniciar
Watch the CPU box update
Observe the Gantt chart building
Verify animation completes without errors

If all steps complete successfully, your installation is working correctly!

Deployment Options

Static Web Hosting

Since the simulator is purely static files, you can deploy to any hosting service:

Render

The official demo uses Render. Connect your GitHub repository and deploy automatically.

Netlify

Drag and drop the project folder for instant deployment with continuous updates.

GitHub Pages

Free hosting for public repositories. Enable in repository settings.

Vercel

Zero-config deployment with automatic HTTPS and global CDN.

Self-Hosted Server

For custom infrastructure, use any web server:

# Copy files to nginx html directory
sudo cp -r AlgoritmosPlanificacion/Planificacion/* /usr/share/nginx/html/
sudo systemctl restart nginx

Browser Compatibility

The simulator is tested and works on:

Google Chrome

Version 90+ (recommended)

Mozilla Firefox

Version 88+

Microsoft Edge

Version 90+ (Chromium-based)

Safari

Version 14+ (macOS/iOS)

Internet Explorer is not supported. The simulator uses modern JavaScript features (ES6+) and Tailwind CSS.

Troubleshooting

Docker build fails

Ensure Docker Desktop is running and you have internet access to pull the nginx:alpine base image.Try:

docker pull nginx:alpine
docker build -t algoritmos-planificacion .

Port 8080 already in use

Another service is using port 8080. Use a different port:

docker run -p 9000:80 algoritmos-planificacion
# Access at http://localhost:9000

Tailwind CSS not loading

The simulator uses Tailwind CDN. Ensure you have internet access or the styles won’t load. For offline use, download Tailwind CSS locally and update the <script> tag in index.html.

Local file CORS errors

Some browsers restrict local file access. Solutions:

Use Docker deployment
Run a local web server (Python, Node, etc.)
Access the cloud demo

Cloud demo is slow

Render’s free tier spins down after inactivity. The first load after idle may take 30-60 seconds. Subsequent loads are instant.

Next Steps

Quick Start Guide

Run your first simulation and learn the interface

Algorithm Overview

Understand how each scheduling algorithm works

Usage Guide

Advanced configuration and simulation techniques

GitHub Repository

View source code and contribute to the project

Getting Started

Algorithms

Usage Guide

Installation

Installation Guide

Requirements

Minimal Requirements

Optional Tools

Installation Methods

Option 1: Access the Live Demo

Option 2: Run Local HTML Files

Project Structure

Option 3: Run with Docker

Docker Commands

Custom Port

Verification Steps

Deployment Options

Static Web Hosting

Render

Netlify

GitHub Pages

Vercel

Self-Hosted Server

Browser Compatibility

Google Chrome

Mozilla Firefox

Microsoft Edge

Safari

Troubleshooting

Next Steps

Quick Start Guide

Algorithm Overview

Usage Guide

GitHub Repository

Build docs developers (and LLMs) love

Getting Started

Algorithms

Usage Guide

​Installation Guide

​Requirements

Minimal Requirements

Optional Tools

​Installation Methods

​Option 1: Access the Live Demo

​Option 2: Run Local HTML Files

​Project Structure

​Option 3: Run with Docker

​Docker Commands

​Custom Port

​Verification Steps

​Deployment Options

​Static Web Hosting

Render

Netlify

GitHub Pages

Vercel

​Self-Hosted Server

​Browser Compatibility

Google Chrome

Mozilla Firefox

Microsoft Edge

Safari

​Troubleshooting

​Next Steps

Quick Start Guide

Algorithm Overview

Usage Guide

GitHub Repository

Build docs developers (and LLMs) love

Installation Guide

Requirements

Installation Methods

Option 1: Access the Live Demo

Option 2: Run Local HTML Files

Project Structure

Option 3: Run with Docker

Docker Commands

Custom Port

Verification Steps

Deployment Options

Static Web Hosting

Self-Hosted Server

Browser Compatibility

Troubleshooting

Next Steps