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.
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.
My role
Architecture, development and operations.
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.
Technical architecture
- Apache + Let's Encrypt
- www → apex redirect
- gzip & cache headers
- Company site + admin CMS
- Academy
- Media
- CRM
- EduSuite
- Node.js / Express per app
- PM2 process manager
- PostgreSQL per app
- S3-compatible uploads
- Vite builds
- SSR prerender + sitemaps
- One-command deploy
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.
Challenges & solutions
SEO for a single-page app
ChallengeClient-rendered pages showed crawlers and link previews only the generic shell.
SolutionA 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.
Editing without deploys
ChallengeContent edits shouldn't require a developer.
SolutionAn admin CMS stores content in PostgreSQL; publishing re-runs the prerender into the web root.
Many apps, one box
ChallengeFive apps and several APIs must coexist with existing services on the same server.
SolutionPath-based routing in Apache, one PM2 process per API, and per-app databases.
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