Cloudflare Deployment
Relevant source files
The following files were used as context for generating this wiki page:
Cloudflare Deployment for the WIREDUP project focuses on hosting the project's web interface and documentation showcase. The system utilizes Cloudflare Pages to serve a modern, responsive landing page that visualizes the system architecture and provides quick access to the core Python AI Auto-Wiring system and the Rust-based NexTerm terminal components.
The deployment infrastructure is designed for high availability using Cloudflare's global edge network, providing automatic SSL, CDN capabilities, and integrated analytics. It supports both Git-integrated workflows for continuous deployment and manual command-line deployments via the Wrangler CLI.
Sources: CLOUDFLARE_DEPLOY.md:1-10, DEPLOYMENT_STATUS.md:68-81, public/index.html:1-10
Deployment Infrastructure
The WIREDUP web interface is a static application consisting of HTML5, CSS3, and JavaScript. It serves as the primary gateway for users to explore the project's features, including the Auto-Wiring engine and the Model Context Protocol (MCP) implementation.
Architecture Overview
The following diagram illustrates the relationship between the GitHub repository, the Cloudflare build pipeline, and the final live site distribution.
Cloudflare Pages acts as the hosting provider, pulling source code from GitHub and serving it through its global CDN.
Sources: CLOUDFLARE_DEPLOY.md:12-25, public/index.html:176-200
Build Configuration
Cloudflare is configured to recognize the /public directory as the root for static assets. Unlike complex web frameworks, this project uses a "leave empty" build command strategy, as the assets are pre-rendered static files.
| Configuration Field | Value | Description |
|---|---|---|
| Project Name | wiredup | The unique identifier in the Cloudflare dashboard. |
| Production Branch | main | The branch triggered for live updates. |
| Build Command | (leave empty) | No compilation step required for static HTML. |
| Build Output Directory | public | The folder containing the web assets. |
Sources: CLOUDFLARE_DEPLOY.md:27-33, QUICKSTART.md:25-33
Deployment Methods
The project supports three distinct methods for deploying to Cloudflare Pages, catering to different developer workflows.
1. Dashboard Integration (Recommended)
This method involves connecting the Cloudflare account directly to the GitHub repository located at RemyLoveLogicAI/WIREDUP. It enables "Push-to-Deploy" functionality where every commit to the main branch triggers an automatic update.
The sequence demonstrates the automated flow from code push to live deployment.
Sources: DEPLOYMENT.md:8-23, QUICKSTART.md:16-43
2. Wrangler CLI Deployment
For advanced users or CI/CD pipelines outside of GitHub Actions, the Wrangler CLI is used. This requires a Cloudflare API Token with "Edit Cloudflare Workers" permissions.
# Authentication and deployment via CLI
export CLOUDFLARE_API_TOKEN="your_token_here"
cd /home/user/webapp
npx wrangler pages deploy public --project-name=wiredup --branch=main
Sources: CLOUDFLARE_DEPLOY.md:38-48, DEPLOYMENT_STATUS.md:83-88
3. Manual Asset Upload
Users can manually upload the contents of the /public directory directly through the Cloudflare Pages dashboard under the "Upload assets" section for instant deployment without Git connectivity.
Sources: DEPLOYMENT.md:39-42
Web Interface Components
The deployed site at https://wiredup.pages.dev includes several key sections derived from the source files.
Feature Showcase
The landing page highlights the core technical capabilities of the project:
- Auto-Wiring Engine: Dependency injection with circular detection.
- NexTerm: The Rust-based terminal interface.
- AI Integration: Natural language command processing.
- ENV Management: Secure multi-source configuration.
- SSH Security: Connection pooling and key management.
- MCP Protocol: Standardized AI communication protocol.
Sources: public/index.html:145-185, QUICKSTART.md:46-56
Project Statistics
The interface displays live project metrics to provide transparency into the codebase scale.
| Metric | Value |
|---|---|
| Total Files | 52+ |
| Lines of Code | 7,570+ |
| Languages | Rust + Python |
| Documentation | 67KB+ |
Sources: public/index.html:120-138, DEPLOYMENT_STATUS.md:92-105
Post-Deployment Operations
Custom Domains
Cloudflare allows the attachment of custom domains (e.g., wiredup.ai). This involves updating DNS records and configuring the "Custom domains" tab in the Pages project settings. Cloudflare automatically provisions SSL certificates for these domains.
Sources: CLOUDFLARE_DEPLOY.md:65-72, QUICKSTART.md:92-100
Troubleshooting
The deployment guide identifies common failure points and their solutions:
- Build Failure: Usually caused by an incorrect "Build output directory" setting (must be
public). - 404 Errors: Occurs if
index.htmlis missing from the repository's/publicfolder. - Auth Failure: Requires reconnecting the GitHub integration in the Cloudflare dashboard.
Sources: CLOUDFLARE_DEPLOY.md:83-93, QUICKSTART.md:104-115
Summary
Deployment to Cloudflare Pages is a critical final step in the WIREDUP lifecycle, transforming the local repository into a production-ready, global web presence. By serving the /public directory as a static site, the project ensures fast loading times (< 1 minute deployment) and zero-cost hosting for the developer community.
Sources: CLOUDFLARE_DEPLOY.md:115-125, DEPLOYMENT_STATUS.md:145-155