Training Commerce & LMS Platform

Outcomes

Context

EdTech SMBs rarely need a custom LMS monolith; they need reliable integration between best-of-breed systems.

Challenge

Training businesses need course delivery, marketing pages, and paid enrollment. Running LMS and commerce as disconnected sites creates broken student journeys and duplicate user admin.

Approach

We assembled a Docker Compose ecosystem: Moodle for courses, WordPress + Divi for content/landing, WooCommerce for sales, Edwiser Bridge for LMS–commerce sync, Traefik for host-based routing and TLS, shared MySQL patterns for operable local/prod parity.

Architecture

Moodle, WordPress/Divi, WooCommerce, Edwiser Bridge, Traefik reverse proxy, MySQL, Docker Compose multi-host routing.

Scope

• —Course delivery
• —Landing/content CMS
• —Course commerce
• —Identity/course bridging
• —TLS routing

Constraints

• —Plugin upgrade coupling
• —Shared DB operational discipline
• —Student UX across two frontends

Solution highlights

• —Compose as the product definition
• —Bridge integration for enrollment continuity
• —Traefik host rules for clean public URLs

Technologies

Results

• —Single operable stack for marketing, sales, and learning
• —Bridge-based user/course commerce sync instead of manual dual admin
• —Host-based Traefik routing with optional Let’s Encrypt
• —Repeatable Compose setup for training teams

Lessons learned

• —Integration beats reinvention for training commerce.
• —Student journey QA must cross the CMS→shop→LMS boundary.
• —Proxy and TLS are part of the product, not hosting trivia.