c1) Orientation: What EasyEngine is (and why it changes your workflow) 🧩

c1.1 — What EasyEngine CLI is (and why it’s worth switching) 🚀
What EasyEngine CLI does 
 EasyEngine ( ee ) is a server-side CLI that helps you provision and operate WordPress and other web stacks using containers (commonly Docker-based). Instead of clicking around in a shared-hosting control panel, you manage sites with repeatable commands , which makes your workflow: 
 
 
 Faster 
 
 Create, update, and operate sites in seconds/minutes. 
 
 
 
 More consistent 
 
 The same commands produce the same setup every time (great for staging/prod parity). 
 
 
 
 More operationally powerful 
 
 You get direct access to services like Nginx, PHP, DB, Redis , and the ability to automate routines (backups, cron, cache clears, etc.). 
 
 
 
 
 How it “thinks”: sites as managed units 
 With EasyEngine, a site (like example.com ) becomes a managed unit you can operate with subcommands such as: 
 
 
 Lifecycle 
 
 Create, enable/disable, update, delete 
 
 
 
 Operations 
 
 Reload/restart services, clear caches ( ee site clean ) 
 
 
 
 Access 
 
 Shell into the site’s containers ( ee shell ) 
 
 
 
 Publishing & sharing 
 
 Temporarily expose a local/secured site via a share link ( ee site share ) 🔗 
 
 
 
 Scheduling 
 
 Manage cron jobs with ee cron ⏱️ 
 
 
 
 This aligns strongly with real DevOps-style workflows: declare intent → run command → verify state . 
 
 What changes vs shared hosting (the practical mindset shift) 
 You’re moving from “panel-driven hosting” to “infrastructure you control” : 
 
 
 You manage the server 
 
 Updates, firewall, SSH keys, resources, backups become your responsibility. 
 
 
 
 You gain performance & control 
 
 Tuning PHP/Nginx, adding Redis, isolating sites, debugging via logs/shell access. 
 
 
 
 You automate more 
 
 Commands are scriptable; cron becomes explicit; troubleshooting becomes faster. 
 
 
 
 
 Core tools you’ll use daily (from your excerpt) 
 Here’s how the parts in your provided docs fit together: 
 
 
 ee site ... 
 
 
 Day-to-day site operations 
 
 
 Examples from excerpt: 
 
 ee site clean → clears page/object cache 
 ee site share → share a site via an online link (with --refresh , --disable , --token=... ) 
 
 
 
 
 
 ee shell ... 
 
 Your “daily driver” to run WP-CLI, inspect configs, read logs inside the right container context 
 
 
 
 ee cron ... 
 
 Create/list/update/delete/run scheduled tasks cleanly 
 
 
 
 
 Outcomes you can expect after this course ✅ 
 By the time you complete the chapters, you should be able to: 
 
 Provision WordPress sites confidently (including PHP/DB choices) 
 Operate and debug sites via ee shell 
 Manage caching and routine maintenance ( ee site clean , reload/restart) 
 Create reliable scheduled tasks with ee cron 
 Use share links safely and intentionally ( ee site share ) 
 
 
 Next: pick c1.2 or tell me your goal 🎯 
 If you want a natural continuation, I suggest: 
 
 c1.2 — Installation & prerequisites (server requirements, Docker, DNS, ports, safety basics), or 
 c2.4 — Create a WordPress site end-to-end (fastest path to “I’m productive”), or 
 Tell me: Do you plan to run one server for multiple client sites, or one server per project?