Painless Deployment

Zero downtime. Instant rollbacks. No DevOps required.

// Deploy like a Fortune 500 company on £5/month shared hosting

Deployment Shouldn't Be Terrifying

Why do we accept this as "normal"?

😰

The Friday Night Fear

  • • "Hope this doesn't break production"
  • • Maintenance pages during deployment
  • • Rollbacks take hours (if they work)
💸

The DevOps Tax

  • • Complex CI/CD pipelines
  • • Expensive cloud infrastructure
  • • "You need a dedicated DevOps engineer"

What if deployment was...

😴 BORING?

No stress. No fear. No "cross your fingers and pray."

The PHPue Deployment Revolution

Zero downtime on shared hosting. Yes, really.

How It Works

1

Upload New Source Files

Your site keeps serving the old .dist/ version. Users see no changes.

2

Switch to New Version

Rename .dist/ to .dist-backup/. Site instantly serves new source files.

3

Test & Build

Visit ?build=1 if happy, or instantly rollback by renaming the backup folder.

🛟 The Safety Net

// Current State: Production serving .dist/
📂 .dist/ ← LIVE (users see this)
📂 www/* ← New version files (uploaded but inactive; upload contents only, not the folder)
// Step 1: Switch to the new version
Using FTP or File Manager:
🟡 Rename .dist/ → .dist-backup/
🟢 Upload www/* (* means contents of the folder only)
// Instantly serving new version
// Step 2: Build for Better Performance (Optional)
Once satisfied with the new version:
Visit 🟢 Run domain?build=1 → .dist/
// Emergency Step: If something breaks
Instant rollback — rename:
🔴 .dist-backup/ → .dist/
Your old version is live again (1 second).

Why This Changes Everything

⚡

Zero Downtime

No maintenance pages. No "site under construction". Just seamless updates.

🔄

1-Second Rollbacks

Made a mistake? Rename a folder. Back to previous version instantly.

😴

No Stress

Deploy on Friday at 5 PM. What could possibly go wrong? (Nothing.)

This Isn't Magic - It's Smart Design

PHPue's dual-mode architecture (source vs. compiled) gives you enterprise-grade deployment on shared hosting prices.

// Your deployment process:
1. Upload files via FTP
2. Rename one folder
3. Test live version
4. Build or rollback
// That's it. No DevOps required.

Traditional vs. PHPue Deployment

Traditional Frameworks

  • ⏱️ Hours of deployment setup
  • 🚧 Downtime during updates
  • 😰 Stressful rollback processes
  • 💸 Expensive infrastructure needed
  • 🔧 DevOps expertise required

PHPue

  • ⚡ 30-second deployment
  • 🎯 Zero downtime updates
  • 😴 1-second rollbacks
  • 💰 Works on £5/month hosting
  • 👨‍💻 No DevOps required
🔒

Important Security Note

If you deploy source files (.pvue) to production, you MUST block direct access:

  • • Block .pvue files in .htaccess/NGINX
  • • Protect components/ and views/ directories
  • • Source files expose business logic if accessible
📖 View Deployment in Documentation

Recommended: Only deploy the compiled .dist/ directory to production.

Best Practice: Build locally with ?build=1 and deploy only the .dist/ directory to production.

Stop Fearing Deployment

Join developers who deploy with confidence on any hosting platform.

🚀 Start Building Fearlessly 📖 Read the Docs

Next deployment: Stress-free. Promise.