Skip to content

docs(site): mark the Cloudflare Pages paths as historical #362

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hyperpolymath merged 1 commit into from
Oct 9, 2026
Merged

docs(site): mark the Cloudflare Pages paths as historical #362

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 13 additions & 12 deletions docs/website/CLOUDFLARE-SETUP.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
// SPDX-License-Identifier: CC-BY-SA-4.0
// SPDX-FileCopyrightText: 2026 Jonathan D.A. Jewell (hyperpolymath) <j.d.a.jewell@open.ac.uk>
= Deploying boj-server.net on Cloudflare Pages
= Deploying the boj-server site on Cloudflare
:toc: preamble
:icons: font

The public presence at https://boj-server.net[boj-server.net] is a *no-build static
bundle* in the `site/` directory, served by Cloudflare Pages. It is both a permanent
presence and an access point: an install configurator (base + NeSy / Agentic /
Coordination bundles), and a browsable catalogue of all {counter:cart}139 cartridges
generated from the canonical registry.
The public presence at https://app.boj-server.net[app.boj-server.net] is a *no-build
static bundle* in the `site/` directory, served by a Cloudflare Worker with static
assets. It is both a permanent presence and an access point: an install configurator
(base + NeSy / Agentic / Coordination bundles), and a browsable catalogue of all
{counter:cart}139 cartridges generated from the canonical registry.

== What the site is

Expand Down Expand Up @@ -39,10 +39,11 @@ record, without noting the existing record first. In a non-interactive run (CI),
wrangler sets `override_existing_dns_record` and `override_existing_origin` to `true`
without prompting, so the existing record is replaced silently.

The sections below describe the earlier Cloudflare Pages path and are kept for
reference.
The two sections below describe the earlier Cloudflare Pages path and are kept for
reference only. Do not follow them now: both attach the apex `boj-server.net`, which
is reserved for the outer site.

== Go-live path A — Dashboard Git-connect (recommended, chosen)
== Historical Pages path A — Dashboard Git-connect

`boj-server.net` is already a zone in the Cloudflare account, so this is a one-time,
~5-minute dashboard task. No secrets are stored in the repo or CI.
Expand All @@ -68,7 +69,7 @@ Click *Save and Deploy*. The first deploy lands at `https://boj-server.pages.dev
That is the entire go-live. Every push to `main` then auto-deploys; pull requests get
preview URLs for free.

== Go-live path B — API / CLI (only if you want it automated or agent-driven)
== Historical Pages path B — API / CLI

Two equivalent options; both need a *Cloudflare API token* and the *account ID*.

Expand Down Expand Up @@ -106,8 +107,8 @@ tools to it. To let an agent inspect and change DNS / Pages directly, provide a

Plus the *Account ID* and the `boj-server.net` *Zone ID* (Dashboard -> domain ->
*Overview*, right sidebar). Export as `CLOUDFLARE_API_TOKEN` / `CLOUDFLARE_ACCOUNT_ID`.
*Note:* for go-live path A none of this is required — attaching the custom domain in
the dashboard auto-creates the DNS records.
*Note:* for historical Pages path A none of this is required — attaching the custom
domain in the dashboard auto-creates the DNS records.

== Verify

Expand Down
Loading