Skip to content
Esc
↑↓navigate↵open⌘Jpreview
On this page

Move from Cloudflare Pages

Publish a Cloudflare Pages site on Spacefast. _redirects and _headers publish as they are, wrangler.toml build settings are read, and Pages Functions are rewritten as Spacefast Functions

Your _redirects and _headers files publish with your pages, and Spacefast reads the build settings in wrangler.toml. A Pages Functions folder needs rewriting, because Spacefast Functions uses different file and handler conventions.

Move the site

Create the Space

In the project directory, create an empty Space. Later publishes from this directory update it.

sf spaces create --slug my-site

Bring the environment variables

Export the project’s variables as a dotenv file, then import it before the first build so the build can read them.

sf env import .env --from cloudflare --space my-site

A line with an empty value fails the import, and empty values aren’t supported. Remove the line, or give the variable a real value. See Environment variables.

Publish the project

Run sf publish --space my-site in the project and let Spacefast build it, or publish the output folder you deploy today.

sf publish --space my-site

To build on every push instead, connect the repository with Publish from Git.

Rewrite your functions

Move each Pages function to the Functions file router. See the next section.

Point your domain

Add the domain to the Space and add the DNS records it asks for. Delete the old address records, because a leftover record blocks verification. If a proxy sits in front of the hostname, check that it does not block the HTTP validation request. Spacefast issues the certificate once DNS points at it. See Custom domains and TLS certificates.

What carries over

From Cloudflare Pages On Spacefast
_redirects and _headers files Published with your pages and applied as routing rules
wrangler.toml build settings Read after framework detection, and they override the detected build command and output directory
Environment variables Imported from a dotenv export with sf env import --from cloudflare

Rule order, conditions, and limits are on Redirects, rewrites, and headers.

Functions

Spacefast Functions detects two layouts, and neither takes Pages Functions files as they are:

  • A functions/ folder is a file router. A module’s file name is its route. It exports one function per HTTP method, such as GET or POST, or a default export that answers every method. Each one takes (request, context), with route parameters on context.params.
  • A root handler.ts, handler.js, or handler.mjs default-exports an object with a fetch method and answers the whole Space.

When you rewrite, check these differences:

Rule On Spacefast
Catch-all routes [...rest].ts, and only as the last segment
Files starting with _ Never routed. A _middleware.ts does nothing
Bindings on env Environment variables, plus the Space’s database as the D1-shaped env.DB. No other bindings are documented

Requests and responses are the standard Request and Response, so code inside a handler that uses only those usually needs little change.

What doesn’t

  • cloudflare-cdn-cache-control and the other CDN-specific cache headers are rejected with header_cdn_cache_unsupported. Spacefast manages shared caching; Cache-Control still applies to browsers. See Caching.
  • _routes.json and the .wrangler folder are dropped at publish. See what gets uploaded.
  • Features Spacefast cannot convert are flagged at publish. Move them to a supported equivalent, or pass --allow-unsupported-platform-features to publish without them.

Choose who can open it

A team’s new Spaces start private unless the team changed its default. Make the Space public, or share it with a link, in Spacefast Share.

Last updated on

Was this page helpful?