Skip to main content
Welcome to the Server Requirements guide for the Medium Clone Script (React + Node.js). This guide outlines the essential server specifications and hosting options to ensure a successful deployment. Whether you’re a developer or launching your own SaaS platform, this checklist will help you prepare your environment.
Important: To run this script, you must have a VPS or a dedicated server. Shared hosting is not supported.

​
Core Requirements

​
Runtime Versions

Your server must support the following runtime environments:

Node.js Version

18.x or later

MongoDB Version

6.0 or later
Using the latest LTS (Long Term Support) versions of Node.js and MongoDB ensures the best performance, security, and compatibility.

​
Minimum Server Specifications

For optimal performance in production:

Memory

2 GB RAM minimum (4 GB recommended)

CPU

2 vCPUs or more
Our test environment uses a 4 GB RAM / 2 vCPU VPS on Hetzner, which runs smoothly for medium traffic.

​
Hosting Recommendations

You can deploy this script on a variety of environments:
Shared hosting is not supported, as it doesn’t provide Node.js or MongoDB runtime environments. Use VPS or cloud platforms.

​
Optional: PaaS (Platform as a Service)

For databases, you can either host MongoDB locally or use managed services like MongoDB Atlas.

​
Additional Requirements

  • HTTPS Support: SSL is required for production (can use Let’s Encrypt)
  • Environment Variables: Make sure to configure .env with all required keys
  • Node.js Package Manager: npm or yarn
  • PM2 or systemd (recommended for background service management)

​
Firewall and Ports

Make sure the following ports are open on your server:
  • 3000: React frontend (during development)
  • 5000: Node.js backend (production may vary)
  • 443 / 80: HTTPS / HTTP traffic
  • 27017: MongoDB (if remote access is needed)
If you use Docker, ports can be mapped accordingly. Firewall rules should be set via UFW or provider dashboard.

​
Web Server Compatibility

The app can run with or without a reverse proxy, but using Nginx is recommended for production.

Nginx

Recommended reverse proxy

Apache

Not recommended unless using as a static proxy only
With Nginx, you can handle HTTPS, caching, and compression. See our deployment docs for configuration samples.

​
Next Steps

Once your server meets these requirements, proceed to the installation guide:

Installation Guide

Learn how to install and configure the script on your server.
If you need help, feel free to reach out to our support team.