peteconsuegra / wordpress-plus-laravel-plugin
A WordPress Plus Laravel plugin for WordPress Pete
Package info
github.com/peterconsuegra/wordpress-plus-laravel-plugin
Language:Blade
pkg:composer/peteconsuegra/wordpress-plus-laravel-plugin
This package is auto-updated.
Last update: 2026-03-01 19:55:20 UTC
README
Hybrid WordPress & Laravel Architecture -- Deploy SaaS Apps Inside WordPress or on Subdomains
Integrate Laravel applications directly into WordPress environments using Pete Panel.
This plugin enables a powerful WordPress + Laravel hybrid stack, allowing developers, agencies, and SaaS builders to combine:
- WordPress for SEO, content, plugins, WooCommerce, and marketing
- Laravel for APIs, dashboards, SaaS logic, automation, and custom applications
Built for Pete Panel, this module automates Laravel provisioning inside existing WordPress instances with one click.
🚀 Key Features
- One-click Laravel deployment inside WordPress
- Deploy Laravel on a separate subdomain
- Import existing Laravel apps from Git repositories
- Automatic Composer install & environment setup
- Apache configuration + server reload
- APP_KEY auto-generation
- SSL generation (production mode)
- Integration logs viewer (terminal + Apache logs)
- Git SSH key display for private repo access
🧠 Use Cases
- Build SaaS dashboards connected to WordPress sites
- Add custom Laravel APIs to WordPress
- Create membership platforms powered by Laravel
- Build hybrid WooCommerce + Laravel systems
- Develop internal tools inside marketing sites
- Launch MVP products 10x faster using WordPress frontend + Laravel backend
🔧 Integration Modes
1️⃣ Same Domain (inside_wordpress)
Deploy Laravel inside WordPress directory.
Example:
https://example.com/myapp
Best for: - Marketing-driven sites - SEO-first projects - Keeping everything under one domain
2️⃣ Separate Subdomain (separate_subdomain)
Deploy Laravel on a subdomain.
Example:
https://myapp.example.com
Best for: - SaaS dashboards - Client portals - Application-heavy systems
📦 What Happens During Provisioning
When creating a WordPress ↔ Laravel Sync, Pete Panel:
- Validates Laravel version compatibility (PHP 8.1+ / 8.2+)
- Creates a new Site record
- Executes provisioning shell scripts
- Clones Laravel boilerplate or Git repository
- Runs
composer install - Generates
.envwith database & WordPress integration config - Generates
APP_KEY - Applies Apache configuration
- Reloads the server
- Stores full terminal output for review
🗂 Routes
Method Endpoint
GET /wordpress-plus-laravel GET /wordpress-plus-laravel/create POST /wordpress-plus-laravel GET /wordpress-plus-laravel/logs/{id} POST /wordpress-plus-laravel/delete POST /wordpress-plus-laravel/generate-ssl
All routes require authentication.
⚙️ Requirements
- Pete Panel (Laravel 10+)
- PHP 8.1+ (Laravel 10)
- PHP 8.2+ (Laravel 11/12)
- MySQL
- Git installed
- Composer installed
- Proper filesystem & Apache permissions
🔐 Environment Variables
Required:
- PETE_ROOT_PASS
- DB_HOST
- DB_DATABASE
- DB_USERNAME
- DB_PASSWORD
Optional:
- PETE_DEBUG=active (enables verbose script output)
📊 Logs & Debugging
Each integration stores:
- Terminal provisioning output
- Apache error.log (tail view)
- Apache access.log (tail view)
Accessible at:
/wordpress-plus-laravel/logs/{id}
🛠 Troubleshooting
If provisioning fails:
- Ensure scripts are executable:
<!-- -->
chmod +x vendor/peteconsuegra/wordpress-plus-laravel-plugin/src/scripts/*.sh
- Verify PHP version matches Laravel selection
- Confirm Git + Composer installed
- Check Apache permissions
- Enable PETE_DEBUG for verbose output
🧩 Why Hybrid WordPress + Laravel?
WordPress alone is powerful for marketing. Laravel alone is powerful for applications.
Together, they create a scalable hybrid system:
- WordPress handles SEO & content.
- Laravel handles application logic & scalability.
This architecture reduces MVP build time dramatically and keeps development flexible.
📄 License
Part of the Pete Panel commercial ecosystem.
Learn more: https://deploypete.com