PP

Build & Deploy — Owner's Guide

Everything you need to publish your Marketing site & Community portal — in plain words.

Read this once, keep it handy. It covers your whole setup: how to build the community, how to push both sites to your two servers with one click, how failover keeps you online, and what's already done for SEO. No jargon — just steps.
The big picture — what the pieces are 1 · Build the Community portal — in the platform 2 · Deploy to both servers — one-click Fleet Deploy 3 · Deploy the Marketing site — static, to both servers 4 · Turn on failover — free Cloudflare 5 · SEO — already done + keep it healthy 6 · Change your logo / images 7 · Your everyday routine — the short version 8 · If something goes wrong

◆ The big picture

You have two websites and two servers, tied together so you're always online.

🌐
Marketing site
Static pages that sell PPPHP (home, docs). No database. Lives at Extra/MarketingSite.
💬
Community portal
The Q&A forum. Uses a database. It's a project inside the platform (admin/community).
🖥️
Two servers
Primary = ppradhan.com · Secondary = ppradhan.com.np. The same site lives on both.
🗄️
One shared database
The community's data lives in one place, so you never type a question/answer twice.
☁️
Cloudflare (free)
Sits in front of ppradhan.com. If the primary server is down, it instantly serves the secondary.
Golden rule for search rankings: the world only ever uses ppradhan.com. The .com.np domain is a silent backup — never advertise it as a second site.

1 Build the Community portal

This turns your latest design + content into files ready to upload.

  1. Open the platform, go to the community project.
  2. Click Build (the one-click build). Wait for “Build successful”.
  3. That's it — the finished app is written to output/community.
The marketing site needs no build — it's already plain files in Extra/MarketingSite. You only “build” the community.
New Q&A note: community questions/answers live in the database. New ones you added on your computer only reach the live site when that same database is the shared one (see “one shared database” in the big picture). Adding Q&A is done in the forum itself, once.

2 Deploy to both servers — Fleet Deploy New

One click pushes the community to both servers. No cPanel, no DirectAdmin.

Where is the button? In the platform, open your menu → Deliverables → Community portal. Scroll to the “Live servers — Fleet Deploy” panel. Everything below happens right there on that page.

First-time setup (do once — on the Community portal page):

  1. In the Primary server card, enter ppradhan.com's host, username, password (or SSH key passphrase), and the Community folder to upload into (e.g. /home/you/public_html/community).
  2. Do the same in the Secondary server card for ppradhan.com.np.
  3. Fill in the Shared community database (host + database name + login) — the one database both servers use, so content is never entered twice.
  4. Click Save servers. Then click Test on each card to confirm it connects.

Every time you want to publish:

  1. Click “Rebuild & deploy to both servers” (the blue button). It rebuilds first if anything changed, then uploads.
  2. Watch the per-server ✓ results (Primary + Secondary), each with an “open” link.
  3. If one server shows ✗, fix it and click again — the other stays fine.
Safe & private: your passwords are stored encrypted and never leave your platform. Both servers get the same shared database automatically, so your content is never doubled. The live login lock and source config are never uploaded.

3 Deploy the Marketing site

The marketing site is static, so publishing is just an upload to both servers.

Same place, one click: open Deliverables → Marketing website and use the “Live servers — Fleet Deploy” panel there. Set the Marketing folder on each server card (e.g. /home/you/public_html), Save servers, then click “Deploy to both servers”. The two servers are shared with the Community page — set them up once and both pages use them.

Prefer a command instead? You can also run it from your machine:

  1. Open storage/deploy-static.php and fill in your two servers' details (a template is already created for you). This file is private and never leaves your machine.
  2. Run:
php tools/deploy-static.php --dry-run   # preview: shows what would upload
php tools/deploy-static.php             # upload to BOTH servers

Or fully manual: upload everything inside Extra/MarketingSite to each server's web folder with any FTP program (FileZilla, etc.). Do it for both servers.

Docs are included — the docs folder lives inside the marketing site, so it deploys together automatically.

4 Turn on failover — free Cloudflare

So if the primary server ever goes down, visitors are sent to the secondary — automatically, for free.

  1. Create a free Cloudflare account and add ppradhan.com (point your domain's nameservers to Cloudflare when it asks).
  2. Add a DNS record origin-a.ppradhan.com → your Primary server's IP, set to DNS only (grey cloud).
  3. Make sure ppradhan.com.np points to your Secondary server.
  4. Go to Workers & Pages → Create Worker, paste the failover script (in HOSTING-HA-PLAN.md), and set the two origins.
  5. Add a Worker Route: ppradhan.com/* → your Worker.
Done. Visitors always use ppradhan.com; Cloudflare quietly serves the healthy server. It keeps working even if your platform is off. The full script & details are in HOSTING-HA-PLAN.md.

5 SEO — already set up

Search engines are configured. Here's what's live and how to keep it healthy.

Keep it healthy:

6 Change your logo / images

All your brand images live in one folder for easy reuse.

To change the look later, just ask — the editable master is images/ppphp-crystal-logo.svg.

7 Your everyday routine (short version)

Changed the community?
Open Deliverables → Community portal → click “Rebuild & deploy to both servers”. Done.
Changed the marketing site?
Open Deliverables → Marketing website → click “Deploy to both servers”. Done.

That's the whole day-to-day. Everything else (failover, SEO) runs by itself.

8 If something goes wrong

PPPHP RAD Studio · Owner's Build & Deploy Guide · keep this file for reference