PES Public Portal Deployment Guide

Secure GitHub Actions & Private Repo Blueprint

Strict, step-by-step instructions designed to clean public keys, manage local dependencies, and upload the PES Public Website Portal to an isolated, fully private GitHub repository with automated multi-cloud deployment flows.

🗺️ Interactive Deployment Workflow

Hover or click nodes below to inspect exact milestone parameters, security checklists, and build gates.

Plan 1: Public Website (Private Repo)
1. Workspace Preparation 2. Secret Scrubbing Check 3. Git Init & Local Commit 4. Create Private GitHub Remote 5. CI/CD
Milestone Detail Inspector

1. Workspace Preparation

Navigate to the local workspace folder at c:\Users\e_vas\PEffectiveSol\pes_website_google. Inspect local configurations and make sure that the project folder contains a proper .gitignore and compiles cleanly.

📋 Step-by-Step Execution Plan

1
Verify .gitignore Structure

Verify that node_modules/, build folders (dist/), credentials (.env), and Terraform state structures are locked down in the root configuration.

Step 1 Completed
2
Scrub Plaintext API Credentials

Examine ContactUs.jsx and secure public variables to default placeholder configurations, blocking credential leak paths on Git remote stages.

Step 2 Ready
3
Initialize Git & Execute First Commit

Spin up local Git tracking, check staged files using status scopes, and record the initial system baseline snapshot.

Step 3 CLI commands
4
Establish Private GitHub Repository

Navigate to GitHub.com, configure the pes-public-website repository parameters, and enforce mandatory **Private** visibility.

Step 4 Manual Setup
5
Configure CI/CD Pipelines & Secrets

Map secure AWS and GCP tokens inside GitHub Repository Secrets to unlock safe static bucket syncing and edge cache purge tasks.

Step 5 Verification
powershell — Step 1 
# 1. Navigate to public portal workspace
cd c:\Users\e_vas\PEffectiveSol\pes_website_google

# 2. Check that .gitignore is properly present
cat .gitignore
⚠️

Critical Pre-Flight Check: Mandated Repository Isolation & Private Status

Both codebases contains proprietary layouts, multicloud keys architecture models, and automated build flows. Under no circumstances must this repository's visibility be toggled to Public. Verify repository status on GitHub immediately after execution.