← Cycles
design · c49archivedstarted Jun 11Auto draft — not yet reviewed

Fix the Cloudflare Pages Deploy

Why we did this

Pushing our work no longer updated the live design site. Builds kept failing on access problems, and the site froze with broken pages.

What happened

We stopped building in the cloud. One command builds the site on Mark's laptop and Cloudflare simply serves it. It has worked since September 27.

In wordsThe site is built on Mark's laptop, and Cloudflare serves the finished pages without building anything.
At a glance
4
changes
0
conversations
4
decisions
0
outside helpers

What changed

The two changes that matter most, in plain words. Open any one to see it.

  1. 1

    The site is built on Mark's laptop, and Cloudflare serves the finished pages without building anything.

    One command publishes the site · came from Mark Parson

  2. 2

    Because the build runs next to the sister projects, the live site lists their cycles too.

    Every project's cycles, live

Also in this cycle
  • Each deploy records exactly which versions went into it. In words
  • June's cloud-build fixes and a September move to Cloudflare's own builder each hit the same access wall. In words

How we got here

Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.

Someone said

From the record: no recorded conversation behind this one.

We decided

c49-D1 Make the build a manual local step instead of repairing the cloud build. — Mark Parson

c49-D2 Build locally, push the result to a deploy branch, and have Cloudflare serve it with no build step. — Mark Parson

So now

The site is built on Mark's laptop, and Cloudflare serves the finished pages without building anything.

Someone said

From the record: no recorded conversation behind this one.

We decided

c49-D2 Build locally, push the result to a deploy branch, and have Cloudflare serve it with no build step. — Mark Parson

So now

Because the build runs next to the sister projects, the live site lists their cycles too.

Thanks to

People outside Qpoint first. Every thank-you points at something they said or made.

MP
Mark Parson
Qpoint team

Called for the build to become a local step

After the September 25 break, said to make building a manual step on his laptop; picked the deploy-branch route on September 27 and switched Cloudflare's settings himself.

TF
Tyler Flint
Qpoint team

Moved the site onto Cloudflare's builder

On September 2 replaced the old upload project with a Git-connected one, which deployed every push until September 21.

All images

Every picture from this cycle. Click any one to step through them all.

The pairs

Everything captured · 0

The full record 4 decisions · 9 key-change entries · 1,749 words · 0 captures

The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.

Open the record for c49 →

Qpoint Brand Style Guide