Asset serving
Warning
This section is unfinished. The Rapid section is complete; the other
diagrams are up to date, but do not yet have textual explanations.
Legend
GitHub Cloudflare Google Cloud Virtual Machine Other
GitHub Cloudflare Google Cloud Virtual Machine Other
Overview
user Rapid Maps Metadata https://maps-metadata.beyondallreason.dev/
Cloudflare worker serving data from R2 bucket
https://github.com/beyond-all-reason/maps-metadata/tree/main/cloud/serving Error Logs https://log.beyondallreason.dev/
Source: https://github.com/beyond-all-reason/logs-upload Launcher Config https://launcher-config.beyondallreason.dev/config.json
Source: https://github.com/p2004a/spring-launcher-config-srv Files https://files-cdn.beyondallreason.dev/
Source: https://github.com/beyond-all-reason/maps-hosting Pool Hosts only https://pool-init.beyondallreason.dev/data.7z Rowy https://rowy.beyondallreason.dev/
Our own deployment of Rowy with custom patches as Firebase app on GCP.
There is also a bunch of small services there to support syncing, inside https://github.com/beyond-all-reason/maps-metadata/tree/main/cloud Maps Metadata Pool package build Chobby SPADS Config Google Drive Maps Main Website What is hosted on https://www.beyondallreason.info/maps
Build using Webflow worker worker worker R2 R2 Metadata R2 Images KV R2 read read Image transform read/write read/write sync single map save images read write Push commit Push commit Push metadata Sync maps Pull Push dist_cfg/config.json https://maps-metadata.beyondallreason.dev/
Cloudflare worker serving data from R2 bucket
https://github.com/beyond-all-reason/maps-metadata/tree/main/cloud/serving
https://log.beyondallreason.dev/
Source: https://github.com/beyond-all-reason/logs-upload
https://launcher-config.beyondallreason.dev/config.json
Source: https://github.com/p2004a/spring-launcher-config-srv
https://files-cdn.beyondallreason.dev/
Source: https://github.com/beyond-all-reason/maps-hosting
Hosts only https://pool-init.beyondallreason.dev/data.7z
https://rowy.beyondallreason.dev/
Our own deployment of Rowy with custom patches as Firebase app on GCP.
There is also a bunch of small services there to support syncing, inside https://github.com/beyond-all-reason/maps-metadata/tree/main/cloud
What is hosted on https://www.beyondallreason.info/maps
Build using Webflow
user Rapid Maps Metadata https://maps-metadata.beyondallreason.dev/
Cloudflare worker serving data from R2 bucket
https://github.com/beyond-all-reason/maps-metadata/tree/main/cloud/serving Error Logs https://log.beyondallreason.dev/
Source: https://github.com/beyond-all-reason/logs-upload Launcher Config https://launcher-config.beyondallreason.dev/config.json
Source: https://github.com/p2004a/spring-launcher-config-srv Files https://files-cdn.beyondallreason.dev/
Source: https://github.com/beyond-all-reason/maps-hosting Pool Hosts only https://pool-init.beyondallreason.dev/data.7z Rowy https://rowy.beyondallreason.dev/
Our own deployment of Rowy with custom patches as Firebase app on GCP.
There is also a bunch of small services there to support syncing, inside https://github.com/beyond-all-reason/maps-metadata/tree/main/cloud Maps Metadata Pool package build Chobby SPADS Config Google Drive Maps Main Website What is hosted on https://www.beyondallreason.info/maps
Build using Webflow worker worker worker R2 R2 Metadata R2 Images KV R2 read read Image transform read/write read/write sync single map save images read write Push commit Push commit Push metadata Sync maps Pull Push dist_cfg/config.json https://maps-metadata.beyondallreason.dev/
Cloudflare worker serving data from R2 bucket
https://github.com/beyond-all-reason/maps-metadata/tree/main/cloud/serving
https://log.beyondallreason.dev/
Source: https://github.com/beyond-all-reason/logs-upload
https://launcher-config.beyondallreason.dev/config.json
Source: https://github.com/p2004a/spring-launcher-config-srv
https://files-cdn.beyondallreason.dev/
Source: https://github.com/beyond-all-reason/maps-hosting
Hosts only https://pool-init.beyondallreason.dev/data.7z
https://rowy.beyondallreason.dev/
Our own deployment of Rowy with custom patches as Firebase app on GCP.
There is also a bunch of small services there to support syncing, inside https://github.com/beyond-all-reason/maps-metadata/tree/main/cloud
What is hosted on https://www.beyondallreason.info/maps
Build using Webflow
Files
user Files https://files-cdn.beyondallreason.dev/
Source: https://github.com/beyond-all-reason/maps-hosting SpringFiles Files Recoil Engine worker R2 Assets 3 buckets geographically distributes across North America, Europe, and Asia. KV Cache PubSub Cacher Maps Upload Bucket Mappers have permission to directly put new map files there via web interface to upload them to CDN.
https://console.cloud.google.com/storage/browser/bar-springfiles-syncer_assets-upload read read sync fallback lookup PubSub Upload trigger trigger write write read download release read New release https://files-cdn.beyondallreason.dev/
Source: https://github.com/beyond-all-reason/maps-hosting
3 buckets geographically distributes across North America, Europe, and Asia.
Mappers have permission to directly put new map files there via web interface to upload them to CDN.
https://console.cloud.google.com/storage/browser/bar-springfiles-syncer_assets-upload
user Files https://files-cdn.beyondallreason.dev/
Source: https://github.com/beyond-all-reason/maps-hosting SpringFiles Files Recoil Engine worker R2 Assets 3 buckets geographically distributes across North America, Europe, and Asia. KV Cache PubSub Cacher Maps Upload Bucket Mappers have permission to directly put new map files there via web interface to upload them to CDN.
https://console.cloud.google.com/storage/browser/bar-springfiles-syncer_assets-upload read read sync fallback lookup PubSub Upload trigger trigger write write read download release read New release https://files-cdn.beyondallreason.dev/
Source: https://github.com/beyond-all-reason/maps-hosting
3 buckets geographically distributes across North America, Europe, and Asia.
Mappers have permission to directly put new map files there via web interface to upload them to CDN.
https://console.cloud.google.com/storage/browser/bar-springfiles-syncer_assets-upload
Rapid
Rapid is the format and protocol that the
client uses to download game versions. A repo contains content-addressed files,
packages that list the files in each version, and a versions.gz file that maps
tags such as byar:test to those packages. Clients (pr-downloader ) start
with the repos.gz master list of repos and then fetch only the files they do
not already have.
user Bunny Rapid repos are served to players from
https://repos-cdn.beyondallreason.dev/.
The CDN is provided by https://bunny.net/. Rapid Hosting Server Debian host managed with the Ansible playbook at
https://github.com/beyond-all-reason/rapid-hosting.
The host is shared with the SPADS setup. All services run as Podman
quadlets. GitHub Actions A workflow in the game repo calls the composite action to request a build
and stream its log. The action retries transient failures.
Source: https://github.com/beyond-all-reason/rapid-hosting/tree/main/action GitHub OIDC Provider https://token.actions.githubusercontent.com
The workflow's token is the only credential. GitHub and the builder do not
share any secrets. BYAR-Chobby Beyond-All-Reason Pull Zone https://repos-cdn.beyondallreason.dev/
The repos.gz master list is maintained directly in the storage zone. The
builder does not write it. Storage Zone Holds the pool, packages, versions.gz, and fresh copies for every repo.
It is the origin for the pull zone. Caddy Terminates TLS for https://repos.beyondallreason.dev/, serves the store as
the origin for the repos, and reverse-proxies /build to the builder
without buffering the response. rapid-builder HTTP service that builds Rapid packages on request and publishes them to
Bunny. It verifies the OIDC token, evaluates the repo's CEL policy, and
serializes builds for each repo.
Source: https://github.com/beyond-all-reason/rapid-hosting/tree/main/rapid-builder rapid-buildgit Tool that converts a Git checkout to Rapid format and incrementally
updates the local store.
Part of https://github.com/beyond-all-reason/RapidTools Rapid Store Git Checkouts Edge Rule Redirects a repo's versions.gz to the unique fresh copy uploaded by the
last build.
This works around Bunny storage replication lag. Edge rule changes
propagate globally within a minute, but newly uploaded files do not. Download packages origin POST /build read fetch commit invoke read read write Upload pool, packages, and versions.gz (rclone) Upload a fresh copy and update the rule Trigger workflow Trigger workflow Mint token POST /build (OIDC token) Verify token Fetch commit Fetch commit Rapid repos are served to players from
https://repos-cdn.beyondallreason.dev/.
The CDN is provided by https://bunny.net/.
Debian host managed with the Ansible playbook at
https://github.com/beyond-all-reason/rapid-hosting.
The host is shared with the SPADS setup. All services run as Podman
quadlets.
A workflow in the game repo calls the composite action to request a build
and stream its log. The action retries transient failures.
Source: https://github.com/beyond-all-reason/rapid-hosting/tree/main/action
https://token.actions.githubusercontent.com
The workflow's token is the only credential. GitHub and the builder do not
share any secrets.
https://repos-cdn.beyondallreason.dev/
The repos.gz master list is maintained directly in the storage zone. The
builder does not write it.
Holds the pool, packages, versions.gz, and fresh copies for every repo.
It is the origin for the pull zone.
Terminates TLS for https://repos.beyondallreason.dev/, serves the store as
the origin for the repos, and reverse-proxies /build to the builder
without buffering the response.
HTTP service that builds Rapid packages on request and publishes them to
Bunny. It verifies the OIDC token, evaluates the repo's CEL policy, and
serializes builds for each repo.
Source: https://github.com/beyond-all-reason/rapid-hosting/tree/main/rapid-builder
Tool that converts a Git checkout to Rapid format and incrementally
updates the local store.
Part of https://github.com/beyond-all-reason/RapidTools
Redirects a repo's versions.gz to the unique fresh copy uploaded by the
last build.
This works around Bunny storage replication lag. Edge rule changes
propagate globally within a minute, but newly uploaded files do not.
user Bunny Rapid repos are served to players from
https://repos-cdn.beyondallreason.dev/.
The CDN is provided by https://bunny.net/. Rapid Hosting Server Debian host managed with the Ansible playbook at
https://github.com/beyond-all-reason/rapid-hosting.
The host is shared with the SPADS setup. All services run as Podman
quadlets. GitHub Actions A workflow in the game repo calls the composite action to request a build
and stream its log. The action retries transient failures.
Source: https://github.com/beyond-all-reason/rapid-hosting/tree/main/action GitHub OIDC Provider https://token.actions.githubusercontent.com
The workflow's token is the only credential. GitHub and the builder do not
share any secrets. BYAR-Chobby Beyond-All-Reason Pull Zone https://repos-cdn.beyondallreason.dev/
The repos.gz master list is maintained directly in the storage zone. The
builder does not write it. Storage Zone Holds the pool, packages, versions.gz, and fresh copies for every repo.
It is the origin for the pull zone. Caddy Terminates TLS for https://repos.beyondallreason.dev/, serves the store as
the origin for the repos, and reverse-proxies /build to the builder
without buffering the response. rapid-builder HTTP service that builds Rapid packages on request and publishes them to
Bunny. It verifies the OIDC token, evaluates the repo's CEL policy, and
serializes builds for each repo.
Source: https://github.com/beyond-all-reason/rapid-hosting/tree/main/rapid-builder rapid-buildgit Tool that converts a Git checkout to Rapid format and incrementally
updates the local store.
Part of https://github.com/beyond-all-reason/RapidTools Rapid Store Git Checkouts Edge Rule Redirects a repo's versions.gz to the unique fresh copy uploaded by the
last build.
This works around Bunny storage replication lag. Edge rule changes
propagate globally within a minute, but newly uploaded files do not. Download packages origin POST /build read fetch commit invoke read read write Upload pool, packages, and versions.gz (rclone) Upload a fresh copy and update the rule Trigger workflow Trigger workflow Mint token POST /build (OIDC token) Verify token Fetch commit Fetch commit Rapid repos are served to players from
https://repos-cdn.beyondallreason.dev/.
The CDN is provided by https://bunny.net/.
Debian host managed with the Ansible playbook at
https://github.com/beyond-all-reason/rapid-hosting.
The host is shared with the SPADS setup. All services run as Podman
quadlets.
A workflow in the game repo calls the composite action to request a build
and stream its log. The action retries transient failures.
Source: https://github.com/beyond-all-reason/rapid-hosting/tree/main/action
https://token.actions.githubusercontent.com
The workflow's token is the only credential. GitHub and the builder do not
share any secrets.
https://repos-cdn.beyondallreason.dev/
The repos.gz master list is maintained directly in the storage zone. The
builder does not write it.
Holds the pool, packages, versions.gz, and fresh copies for every repo.
It is the origin for the pull zone.
Terminates TLS for https://repos.beyondallreason.dev/, serves the store as
the origin for the repos, and reverse-proxies /build to the builder
without buffering the response.
HTTP service that builds Rapid packages on request and publishes them to
Bunny. It verifies the OIDC token, evaluates the repo's CEL policy, and
serializes builds for each repo.
Source: https://github.com/beyond-all-reason/rapid-hosting/tree/main/rapid-builder
Tool that converts a Git checkout to Rapid format and incrementally
updates the local store.
Part of https://github.com/beyond-all-reason/RapidTools
Redirects a repo's versions.gz to the unique fresh copy uploaded by the
last build.
This works around Bunny storage replication lag. Edge rule changes
propagate globally within a minute, but newly uploaded files do not.
Serving
Players download repos from https://repos-cdn.beyondallreason.dev/ , a
Bunny pull zone backed by a Bunny storage zone. The
builder writes <repo>/pool, <repo>/packages, and <repo>/versions.gz to the
storage zone. Players communicate only with the CDN. The repos.gz master list
is maintained manually in the storage zone, not by the builder, so it can list
repos that are no longer built.
Replication from the storage zone to the edge regions lags behind writes.
Immediately after a build, the CDN can therefore serve a stale versions.gz,
causing clients to fetch a version that is no longer current. To avoid this,
each build uploads the same file under a unique name,
<repo>/fresh/versions_<stamp>.gz, because new files are visible in edge
locations immediately. It waits until the CDN serves that copy and then updates
an edge rule to redirect
<repo>/versions.gz to it. Edge rule changes propagate globally within a
minute.
Building
Builds run on a single server managed by the rapid-hosting Ansible playbook.
The server also hosts one of the SPADS instances, and all services run as
Podman quadlets. Two services are involved:
Caddy terminates TLS, serves the builder's store as the origin for the
repos at https://repos.beyondallreason.dev/ , and reverse-proxies /build to
the builder without buffering as required by the build
API .rapid-builder rapid-buildgit from RapidTools and uploads the result to
Bunny. It keeps a Git clone and a Rapid store for each repo, so a build
processes only changed content. See its README for a single
build step by step.
A GitHub Actions workflow in the game repository triggers a build by calling the
composite action from the same repo. The action sends the
workflow's OIDC token to /build, so GitHub and the server do not share a
secret. What a repo may publish is decided by a CEL policy
defined in the playbook's group variables, see the authorization
docs . Currently, a push to stable in
Beyond-All-Reason publishes byar:test; a manual run on master publishes
byar:pr-<number> or byar:br-<name>; and a push to master in BYAR-Chobby
publishes byar-chobby:test.
The builder sends its metrics and logs to the monitoring
server .
Rowy
user Maps Metadata https://maps-metadata.beyondallreason.dev/
Cloudflare worker serving data from R2 bucket
https://github.com/beyond-all-reason/maps-metadata/tree/main/cloud/serving Rowy https://rowy.beyondallreason.dev/
Our own deployment of Rowy with custom patches as Firebase app on GCP.
There is also a bunch of small services there to support syncing, inside https://github.com/beyond-all-reason/maps-metadata/tree/main/cloud Maps Metadata worker R2 Metadata R2 Images Imagor Frontend Firebase frontend, https://rowy.beyondallreason.dev/ Firestore Map Parser Github Trigger Uploaded Assets Bucket Parsed Maps Bucket read read Image transform read/write read read/write invoke invoke write read read write sync single map Push metadata Pull https://maps-metadata.beyondallreason.dev/
Cloudflare worker serving data from R2 bucket
https://github.com/beyond-all-reason/maps-metadata/tree/main/cloud/serving
https://rowy.beyondallreason.dev/
Our own deployment of Rowy with custom patches as Firebase app on GCP.
There is also a bunch of small services there to support syncing, inside https://github.com/beyond-all-reason/maps-metadata/tree/main/cloud
Firebase frontend, https://rowy.beyondallreason.dev/
user Maps Metadata https://maps-metadata.beyondallreason.dev/
Cloudflare worker serving data from R2 bucket
https://github.com/beyond-all-reason/maps-metadata/tree/main/cloud/serving Rowy https://rowy.beyondallreason.dev/
Our own deployment of Rowy with custom patches as Firebase app on GCP.
There is also a bunch of small services there to support syncing, inside https://github.com/beyond-all-reason/maps-metadata/tree/main/cloud Maps Metadata worker R2 Metadata R2 Images Imagor Frontend Firebase frontend, https://rowy.beyondallreason.dev/ Firestore Map Parser Github Trigger Uploaded Assets Bucket Parsed Maps Bucket read read Image transform read/write read read/write invoke invoke write read read write sync single map Push metadata Pull https://maps-metadata.beyondallreason.dev/
Cloudflare worker serving data from R2 bucket
https://github.com/beyond-all-reason/maps-metadata/tree/main/cloud/serving
https://rowy.beyondallreason.dev/
Our own deployment of Rowy with custom patches as Firebase app on GCP.
There is also a bunch of small services there to support syncing, inside https://github.com/beyond-all-reason/maps-metadata/tree/main/cloud
Firebase frontend, https://rowy.beyondallreason.dev/
September 16, 2026
February 28, 2025