Deploy to Cloudflare
Deploy your app to Cloudflare Pages for fast, global delivery.
Cloudflare Pages is a fast, global hosting platform for static sites and JAMstack applications. Zynnode deploys your app to Cloudflare's edge network, so your site loads quickly for visitors anywhere in the world.
Before deploying, make sure you've connected your Cloudflare account.
What Cloudflare Pages Is Best For
- Static websites and landing pages
- Single-page applications (React, Vue, Svelte)
- JAMstack apps built with Next.js (static export), Astro, or similar frameworks
- Documentation sites, blogs, and marketing pages
If your app needs a running backend server, consider deploying to AWS EC2, GCP Cloud Run, or Azure VM instead.
Setting Up Your Project
During the project configuration step in the new project wizard:
- Select your GitHub repository.
- Zynnode auto-detects your framework and build settings.
- Choose Cloudflare Pages as your deployment target from the dropdown.
- Review the build settings:
- Build Command — e.g.,
npm run build - Output Directory — e.g.,
dist,build,out, or.next(for Next.js static export)
- Build Command — e.g.,
- Add any environment variables your app needs.
- Continue to the provider selection and choose Cloudflare.
What Happens During Deployment
- Zynnode clones your repository and runs the build command.
- The build output (your static files) is uploaded to Cloudflare Pages.
- Cloudflare distributes the files across its global edge network.
- Your app is live at a Cloudflare Pages URL.
The deployment URL is shown in your Zynnode dashboard once the build completes.
After Deployment
Your Live URL
Cloudflare Pages gives your project a URL like https://your-project.pages.dev. This URL is shown in your Zynnode dashboard project card. You can also add a custom domain.
Automatic Redeployments
Every time you push to your default branch on GitHub, Zynnode automatically triggers a new build and deploys the updated files to Cloudflare Pages.
Global Performance
Cloudflare Pages serves your site from data centers in over 300 cities worldwide. Your visitors get the site from the nearest location, which means fast load times everywhere.
Good to Know
- Static output only — Cloudflare Pages hosts static files (HTML, CSS, JS, images). Server-side rendering or API routes that require a running server won't work here.
- Next.js users — If you're using Next.js, make sure your
next.config.jsincludesoutput: 'export'for a fully static build. Otherwise, consider GCP Cloud Run or AWS ECS for server-side rendering. - Build size limits — Cloudflare Pages has a maximum build output size of 25,000 files and 25 MB per file. Most apps are well under these limits.
Troubleshooting
Build succeeds but the site shows a blank page
- Check that your output directory in the project settings matches where your framework puts the built files. Common values:
- React (Vite):
dist - Create React App:
build - Next.js (static):
out - Astro:
dist - Vue:
dist
- React (Vite):
"ERR_TOO_MANY_REDIRECTS" error
This usually means your Cloudflare domain's SSL setting is causing a redirect loop.
- Open the Cloudflare Dashboard.
- Select the domain you're using.
- In the left sidebar, click SSL/TLS.
- Change the encryption mode to Full (Strict).
Site loads but styles or images are missing
- Make sure your framework is configured to use relative paths (not absolute paths starting with
/). - Check the browser developer console for 404 errors on specific files.
For more common issues, see the Troubleshooting guide.