Editing Category:DESHWAL (section)

==Training on Deshwal Project Part 1. Dated 01 JULY 2025 - Tetra Support Staff - TUSHAR==

{{#ev:youtube|Sjk7CqbGVWk|640}}

'''Video summary:''' "DeshwalProject Training Part 1" -- a Hindi-language architecture and setup walkthrough for the Deshwal client's LAMP-stack environment (Linux/Apache/PHP/MySQL, plus Jenkins), which has separate Production and Staging environments. Architecture, top to bottom: a public IP/domain NATed to a private IP shared by two DMZ-facing reverse-proxy servers (Proxy 1 primary, Proxy 2 secondary) using keepalived for a floating/virtual IP, so both proxies can receive traffic simultaneously based on load, each configured to prefer its local app server (App1) and fail over to App2 only if App1 becomes unavailable for a defined window; two application servers (App1 primary, App2 secondary) behind the proxies, where App1's attached disk (holding `/data` and `/backup`) is shared out to App2 via NFS -- note this is a direct NFS export from App1 itself, not a separate third-party NFS appliance; and two database servers (DB1 master, DB2 slave) with one-way replication, where App1 always writes to DB1 and manual promotion of DB2 to master is required if DB1 fails. External backups are handled by a separate team using a Commvault backup agent. The session then walks through the actual proxy-server build: installing/upgrading Apache, a redirect vhost that forces all HTTP requests to HTTPS, and a separate reverse-proxy vhost implementing the App1-primary/App2-fallback routing, with the firewall restricted to ports 80/443/56 and keepalived installed only on Proxy 1 in production. On the app server side: mounting the dedicated data disk, storing actual application data under `/data` and symlinking it into the Apache document root (with root ownership, SGID, and group-based permissions so the Apache user can read/write without owning the files), editing the app's DB-connection config, installing PHP and its required packages (noting Ubuntu bundles PHP with Apache, requiring an Apache restart to apply config), and installing phpMyAdmin from a downloaded tarball into a defined path with its own vhost, read-only S3-backed file storage for downloadable assets, and appropriate permissions.