Enhance: Deploy via GitHub & Worker Processes Guide

1. Deploying via GitHub (Automatic Push & Manual)

You and your customers can now manually or automatically on push deploy public or private repositories from a connected GitHub account to new or existing production or staging websites.

Deploy via GitHub can be performed via three streamlined paths:

• Add New Website Flow: Choose GitHub as your source repository when creating a new website. Enhance clones the repo, installs dependencies, and issues an SSL certificate automatically.
• Account-Level Connection (Left-Hand Spine): Authenticate your personal or organization GitHub account once to grant repository access across all websites you manage.
• Website Management Dashboard: Open any existing website and click the dedicated GitHub section to configure branch mappings (e.g. main for production, staging for preview), toggle auto-deploy on push, view commit history, and trigger manual redeployments.

For in-depth setup steps and webhook security, refer to the Official Enhance GitHub Deploy Documentation.

2. Running Background Worker Processes

It is now possible to run PHP, Node.js, Laravel, static websites and Custom Applications (for instance a runtime built in Rust or Go) worker processes. UI support is available under the Worker Processes section on the website management dashboard.

Worker processes run inside dedicated container cgroups with automatic restart supervisors, live logging, and configurable process counts:

• Laravel Queues: Run php artisan queue:work --sleep=3 --tries=3 to handle emails, media processing, and webhooks in the background.
• Node.js Daemons: Run persistent Express, NestJS, WebSocket, or Next.js background engines.
• Custom Applications: Run native compiled binaries built in Rust or Go directly with custom port bindings and environment variables.
• Automatic Restart & Supervision: If a worker process exits or crashes, Enhance's supervisor automatically restarts it immediately.
• Live Log Streaming: Inspect real-time stdout and stderr logs directly in the browser without needing terminal SSH access.

3. The Platform Details Card for MOs & Resellers

A Platform details card on the Master Organisations (MOs) and Resellers dashboard now highlights key connection information in a single unified view:

• Control Panel URL: Direct white-label login link for you and your clients (e.g. https://cp.doublehosting.net).
• Webmail URL: Quick-access webmail client endpoint for domain email accounts.
• Staging Domain Suffix: Automatic wildcard suffix (e.g. *.staging.doublehosting.net) used for instant pre-production preview sites.
• phpMyAdmin URL: Single-sign-on database portal for managing MySQL databases securely.
• Account Nameservers: Primary and secondary nameservers for connecting custom client domains.

4. Deployment & Security Best Practices

Follow these best practices to ensure smooth deployments and maximum stability:

• Keep Secrets in Environment Variables: Never commit database passwords or API keys to GitHub repositories. Use the Environment Variables tool in Enhance to define them securely.
• Test on Staging First: Use Enhance's one-click staging environments to test GitHub branches before deploying to production.
• Monitor Memory Limits: Verify worker processes stay within allocated RAM thresholds in the Enhance resource metrics tab.