Skip to content
Platform engineering · DevOpsLive in production

nayaprayog.com Platform & Infrastructure

Five apps on one domain and one server (company site, Academy, Media, CRM and EduSuite), with an admin CMS, build-time prerendering for SEO and a one-command deploy.

Role
Architecture, development and operations.
Platforms
Web · Infra
Stack
  • React
  • Vite
  • Node.js
  • Express
  • PostgreSQL
  • Apache
  • PM2
  • Let's Encrypt
  • Linux
01

Overview

The platform behind nayaprayog.com: React SPAs built with Vite, Node.js/Express APIs on PostgreSQL, all served from one Linux VPS behind Apache with HTTPS. The company site has an admin CMS where every section, product and project is editable; saving republishes the prerendered SEO pages without a redeploy.

02

Problem

A growing set of products (company site, academy, media, CRM, EduSuite) needed to live on one domain, share content and leads, rank in search, and be deployable by one person without downtime surprises.

03

My role

Architecture, development and operations.

04

Engineering approach

Each app is a separate Vite build mounted at its own path, with its own API process. Apache routes paths to static builds or proxies them to the APIs. A build step server-renders product, portfolio and service pages to static HTML, so crawlers and link previews get full content without JavaScript.

05

Technical architecture

01Edge
  • Apache + Let's Encrypt
  • www → apex redirect
  • gzip & cache headers
02Apps
  • Company site + admin CMS
  • Academy
  • Media
  • CRM
  • EduSuite
03APIs
  • Node.js / Express per app
  • PM2 process manager
04Data
  • PostgreSQL per app
  • S3-compatible uploads
05Build
  • Vite builds
  • SSR prerender + sitemaps
  • One-command deploy
06

Infrastructure & deployment

AlmaLinux VPS with Apache (reverse proxy for every API), Let's Encrypt TLS, PM2 for automatic restarts, PostgreSQL, and a deploy script that pulls, installs, builds every frontend, prerenders, and restarts the APIs. Database migrations run automatically when an API starts.

07

Challenges & solutions

  1. SEO for a single-page app

    Challenge

    Client-rendered pages showed crawlers and link previews only the generic shell.

    Solution

    A build-time SSR pass renders key pages to static HTML with their own title, canonical and JSON-LD; Apache serves them, and React takes over in the browser.

  2. Editing without deploys

    Challenge

    Content edits shouldn't require a developer.

    Solution

    An admin CMS stores content in PostgreSQL; publishing re-runs the prerender into the web root.

  3. Many apps, one box

    Challenge

    Five apps and several APIs must coexist with existing services on the same server.

    Solution

    Path-based routing in Apache, one PM2 process per API, and per-app databases.

08

Features

  • Admin CMS for every section, product and project
  • Leads inbox with UTM attribution
  • Prerendered pages and generated sitemaps
  • Shared blog fed from EduSuite
  • Cross-app course cart and checkout