ABNCMS/Documentation Website GitHub 中文EN
Home/Documentation

ABNCMS Documentation#

A complete guide from getting started to production. ABNCMS is a free, open-source lightweight CMS built for Cloudflare Workers + D1 + an external image host — no server, no hosting fees, a single production dependency (Hono), and everything within Cloudflare's free tier.

This manual covers product overview, environment setup, local development, deployment, system architecture, admin usage, API and image hosting, caching, plus FAQs and troubleshooting. Current version v0.2.7, built on Cloudflare Workers.

Truly Zero Cost

Runs entirely on Cloudflare's free plan — no server, no credit card.

Global by Default

Pages cached at the edge, served close to visitors, with HTTPS and DDoS protection built in.

Admin, Always Editable

Write posts and upload images in a visual admin — changes go live instantly, no rebuild.

Lightning Edge Cache

Cache hits mean zero database queries; publishing bumps the cache generation for site-wide instant updates.

Core design goalAnonymous requests hitting the page cache perform 0 D1 queries and 0 KV reads/writes; cache misses use at most 5 D1 queries. Every optional cost has an admin toggle, so a small site can run on "HTML cache + a few reads" only.

Core Features#

A single Worker handles front-end SSR, the admin panel, APIs and scheduled jobs — broad coverage at a tiny footprint.

Front End#

  • Homepage banner, post stream (pretty URLs /p/{slug}.html), standalone pages (/page/{slug}.html)
  • Custom navigation, categories / tags / archive, full-text search, Markdown rendering
  • AI summaries, previous/next links, related posts, comments (built-in analytics off by default)
  • RSS (/feed.xml), Sitemap (/sitemap.xml), JSON-LD structured data
  • Two-column sidebar (popular posts, categories, tags, links), responsive layout

Admin Panel#

  • Login protection: PBKDF2 password + KV sessions + per-IP rate limiting + Turnstile CAPTCHA
  • Post CRUD, two-column Markdown editor, AI summary & tags
  • Visual image-host URL/token config, site logo upload, third-party analytics script
  • Standalone pages, navigation menu, friend links, media library, categories, comment moderation
  • Full export / import backup, site settings, password change, dashboard

Scheduled Jobs (Cron)#

Daily at 03:00 UTC, cleans page-view records older than 30 days and spam comments older than 90 days, and writes a heartbeat.

Requirements#

ItemRequirementNotes
Node.js20+ (22 LTS recommended)Runs Wrangler and local dev
Python3.8+Helper scripts and smoke tests only, standard library, no pip
Cloudflare accountFree plan is enoughNo credit card required
WranglerIncluded as devDependencyInvoke with npx wrangler
workers.dev subdomainRegister once in advanceOAuth login cannot create it via API; register manually in the dashboard
TipOnly one production dependency: hono. Strict-mode TypeScript, esbuild bundled by Wrangler — no extra build tooling needed.

Quick Start#

The shortest path from cloning the repo to seeing a live page.

1

Clone the project

git clone https://github.com/baiyirui/abncms.git && cd abncms

2

Install dependencies

npm install

3

Prepare configuration

Copy wrangler.example.jsonc to wrangler.jsonc and .dev.vars.example to .dev.vars, then fill in resource IDs and the admin password.

4

Init local DB and start

npm run db:local → npx wrangler d1 execute cf-press-db --local --file=./seed.sql → npm run dev

5

Open it

Visit http://127.0.0.1:8787; the admin is at /admin/login.

Full command sequence
# Clone and enter the project
git clone https://github.com/baiyirui/abncms.git && cd abncms
npm install
# Configure (fill in account_id / D1 / KV IDs)
cp wrangler.example.jsonc wrangler.jsonc
cp .dev.vars.example .dev.vars
# Initialize the local database
npm run db:local
npx wrangler d1 execute cf-press-db --local --file=./seed.sql
# Start the local dev server
npm run dev   # → http://127.0.0.1:8787

Local Development#

Wrangler provides a local environment matching production — D1, KV and cron jobs are all simulated locally.

Common commands#

CommandPurpose
npm run devStart local server (wrangler dev)
npm run typecheckTypeScript check (tsc --noEmit)
npm run buildDry-run build into dist/ without deploying
npm run db:localCreate local tables (schema.sql)
npm run smokeSmoke test for core pages and APIs
npx wrangler typesGenerate Worker type declarations from config

Initial admin#

Only when the users table is empty on first login does the system create the initial admin using ADMIN_PASSWORD from .dev.vars. Change the password in the admin settings immediately after logging in.

NoteIf local login fails with a previously used account (e.g. the sample baiyirui), delete the local D1 user data so ensureAdmin() recreates admin from .dev.vars. The local database lives under .wrangler/.

Smoke test#

SMOKE_ADMIN_USER=admin SMOKE_ADMIN_PASS='your-password' \
  python scripts/smoke_test.py http://127.0.0.1:8787

Deployment#

Use the helper script to create remote resources and write back IDs, then deploy to the global edge with one command.

1

Log in to Cloudflare

npx wrangler login

2

Create remote resources

python scripts/setup_remote.py creates D1 / KV / Vectorize and writes the returned IDs back to wrangler.jsonc.

3

Initialize database

New database: npm run db:remote. Upgrading an existing site: do not re-run schema — use npm run db:migrate instead.

4

Inject secrets

Set the admin password, encryption key, etc. (see next section).

5

Deploy

npm run deploy. Afterwards set SITE_URL in wrangler.jsonc to the real URL and deploy once more.

Deployment commands
npx wrangler login
python scripts/setup_remote.py
npm run db:remote          # create tables for a new DB
# for upgrades use: npm run db:migrate
npx wrangler secret put ADMIN_PASSWORD
npx wrangler secret put CONFIG_ENCRYPTION_KEY
npm run deploy
Upgrade noticeWhen production data already exists, do not re-run schema.sql and overwrite admin settings. Incremental migration only adds missing keys and never overwrites modified site name / password / tokens.

Custom domain#

After deployment, add a custom domain in the Cloudflare Workers dashboard and point DNS accordingly, or simply use the free *.workers.dev subdomain. HTTPS certificates are issued automatically.

Configuration & Secrets#

Configuration comes in three kinds: resource bindings in wrangler.jsonc, sensitive secrets via wrangler secret put, and site info maintained in the admin.

NameLocationPurpose
account_id / database_id / kv idwrangler.jsoncResource bindings, not stored in DB
SITE_NAME / SITE_DESCRIPTION / SITE_URLvarsSite info, editable in admin
TURNSTILE_SITE_KEYvarsPair-replaced with the admin secret
IMGBED_BASE_URL / IMGBED_TOKEN_NAMEvarsImage host in environment-variable mode
ADMIN_PASSWORDSecretOnly for initial admin creation
CONFIG_ENCRYPTION_KEYSecretEncrypts admin-written tokens (32-byte random string)
IMGBED_TOKENSecretImage host token in environment-variable mode
site_logo / imgbed_*D1 settingsAdmin-maintained (token stored encrypted)
Generate the config encryption key
openssl rand -hex 32
npx wrangler secret put CONFIG_ENCRYPTION_KEY

Turnstile CAPTCHA: three states#

  • off / empty: fully disabled — no component loaded, login passes through (useful where challenges.cloudflare.com is unreachable)
  • official test keys: always pass
  • real keys: Site Key (vars) and Secret (admin settings) must be replaced as a pair, then redeploy
Security notewrangler.jsonc, .dev.vars and temporary diagnostics are all in .gitignore. Never commit config containing secrets to a public repo.

System Architecture#

The system is designed around "let the edge cache handle almost all reads".

Browser ──► Cloudflare Worker (Hono SSR / admin / API / Cron)
              │  Anonymous visitors first check full HTML in edge Cache API
              │  (key includes the cache_gen generation)
              │  ├─ hit  → return directly, 0 D1 / 0 KV
              │  └─ miss → read D1, render, async-write edge cache (no KV quota)
          ├── D1        posts · pages · users · categories · tags · comments · settings
          ├── KV        sessions · settings · sidebar · rate limits
          ├── Workers AI + Vectorize   summaries / tags / semantic search (off by default)
          └── External image host   POST /upload (token injected server-side)

Tech stack#

Strict-mode TypeScript · Cloudflare Workers (V8 isolate, not Node) · Hono routing · Wrangler's built-in esbuild. Only hono in production dependencies.

Typical flows#

  • Publishing: POST /admin/post/* → same-origin check → Markdown render → upsert posts / post_tags → bumpCacheGen() increments the generation, instantly invalidating cached pages.
  • Uploading: POST /api/upload (FormData file + optional channel) → Worker injects Authorization: Bearer → image host /upload → external URL saved to media → URL returned into the editor.
  • Anonymous article read: read settings → look up "full URL + cache_gen" in Cache API → hit returns directly (0 D1, 0 KV); miss queries D1, renders, and waitUntil writes the edge cache.

Caching#

The heart of the design. Page HTML lives in Cloudflare Cache API (no KV write quota); the cache key = full URL (including ?page=) + cache_gen generation, TTL 7 days.

Instant updates on publish#

On publish, edit, delete, comment, category or settings change, only cache_gen is +1 (one D1 write). Old cache entries instantly stop matching, so the whole site shows new content within a second — no purge, no per-page deletion. Using the full URL as key also fixed a pagination cross-page bug.

Debug tipThe response header x-abn-cache: HIT / MISS tells you whether the edge cache was hit.

Request cost by scenario#

ScenarioWorkersD1KV
Anonymous front end, cache hit1 (very light)00
Anonymous front end, miss1a few reads1–2 reads
Page cache disabled1a few readsread settings/sidebar
Admin / search / logged in1read + writeread + write
  • Logged-in responses are always no-store: drafts and admin pages never enter the cache.
  • 404 pages carry a <!--nocache--> marker so errors aren't cached for 7 days.
  • New posts default to "published": visible on the homepage immediately; only an explicit "draft" selection hides them.
  • Settings/sidebar cache TTL is 6 hours: KV allows only 1,000 writes/day; 6 hours reduces this to 4/day, and saves actively invalidate the cache so nothing goes stale.

Page views#

Views are sampled at 25% on the client → POST /api/hit → aggregated with a ×4 weight and written to D1. This is an estimate, not an exact metric. /api/hit validates same-origin, an internal path whitelist and a weight cap. It is recommended to disable built-in analytics and use the admin "third-party analytics script" instead (Baidu Analytics / GA / Umami); the script is injected verbatim at the bottom of the front end, and turning off built-in analytics brings analytics cost on D1 / KV to zero.

Free Tier#

Verified against official docs (updated 2026-10-30); all daily quotas reset at 00:00 UTC.

ResourceFree quotaDesign implication
Workers100k requests/day, 10ms CPU/request, 50 subrequestsKeep each render light
D15M rows read / 100k rows written / 5 GBBilled by rows scanned; lists must use indexes
KV100k reads / 1,000 writes / 1 GBNo KV writes on front-end requests
Workers AI10k neurons / dayAI features can degrade gracefully
R210 GB / monthNot used by this project
"Is it static after publishing?"No static files are generated, but anonymous access behaves equivalently — on an edge-cache hit the Worker returns complete HTML directly with 0 D1 and 0 KV operations, while keeping an admin for anytime updates.

Admin Panel#

Visit /admin/login. The left navigation covers all management features.

ModuleFeatures
DashboardCounts of posts, drafts, comments, media, views
PostsCreate / edit / delete, two-column Markdown editor, AI summary & tags
PagesStandalone page management (/page/{slug}.html)
Categories / TagsCategory CRUD; one-click top menu generation from categories
CommentsModeration (approve / delete)
MediaList and delete uploaded images
Links / MenuFriend links and navigation menu
SettingsSite info, logo, image host, analytics script, feature toggles, password
BackupFull JSON export / import
Writing tipNew posts are "published" by default and visible immediately; choose "draft" explicitly to hide. Saving bumps the cache generation; if content still looks old it is usually browser caching — press Ctrl+F5 for a hard refresh.

Security#

  • Passwords hashed with salted PBKDF2-SHA256; session cookies HttpOnly + SameSite=Lax + Secure over HTTPS, valid 7 days
  • All admin writes verify login state and same-origin; login has per-IP failure rate limiting
  • Markdown output fully escaped; all SQL uses parameterized bindings
  • Image-host token: AES-GCM encrypted at rest, masked in UI, never logged, excluded from backup exports

Feature Toggles#

Settings → Feature Toggles independently controls each capability. When disabled, the corresponding D1 / KV query or write does not execute at all. Small sites should keep only page cache + popular posts.

SettingDefaultPurpose
enable_page_cacheOnEdge cache for page HTML
enable_hotOnPopular posts sidebar
enable_relatedOnRelated posts
enable_prevnextOnPrevious/next post
allow_commentsOnComments
enable_linksOffFriend links module
enable_semanticOffSemantic search (Vectorize)
enable_aiOffAI summary & tags (Workers AI)
analytics_enabledOffBuilt-in analytics (writes D1)
About view statsEach built-in analytics hit writes two D1 rows (update posts.views + insert page_views), consuming D1 writes but no KV. It is off by default; when disabled, the front end injects no beacon and the server discards /api/hit requests.

Image Host & Media#

Images are uploaded to any compatible image host and referenced by external URL. The Worker injects the token server-side so it never reaches the browser. R2 is not used.

Configuration priority#

Admin D1 (AES-GCM encrypted)  >  wrangler vars / Secret  >  unconfigured
  • The master key CONFIG_ENCRYPTION_KEY is injected via wrangler secret put; it is never stored in DB or echoed in the UI.
  • The admin settings page shows only the last 4 characters of the token; an empty input means "unchanged"; you can clear it and fall back to environment variables.
  • "Test connection" calls the host's GET /api/channels without uploading a test image.
  • Without the master key the system falls back to "environment-variable mode", where the admin can only change the URL.

Image host API contract#

POST /upload with header Authorization: Bearer <TOKEN> and field file; supports returnFormat=full, responseFormat=object, uploadChannel=s3|huggingface; delete via POST /api/manage/delete/{fileId}.

Site logo#

The logo reuses /api/upload through the image host. Recommended display height 32–40px, 2x source 64–80px, width ≤200px, SVG preferred. With no upload it defaults to an inline "icon + site name" style that updates automatically when the site name changes.

Build Your Own Image Host#

ABNCMS does not store images itself — every image is referenced by an external URL. The previous section covered connecting an existing image host. This section walks you through building a fully private, permanently free image host whose files live in your own repository, providing external links for your articles and logo.

About this guide & open-source referenceThis approach is based on the widely used community pattern of pairing Cloudflare with a code-hosting repository, rewritten here into a standard workflow tailored to ABNCMS.
The screenshots in this chapter come from the open-source project CloudFlare-ImgBed (MIT license) — for deployment-method reference only. You can also view the source repository or visit the official docs. Review the license and security of any third-party program before using it.

Overview#

The whole setup has three roles, each with one job: Cloudflare Pages hosts the image-host app for free (global acceleration, unmetered traffic), Workers KV stores channel configuration, and a HuggingFace repository acts as the file store. Files land in your own repository, not on anyone else's server.

Image host workflow: ABNCMS admin → image host service → storage repository, with KV holding channel config

Real interface screenshots captured during deployment (original watermarks removed).

  • Free to deploy: Pages and KV both fit within Cloudflare's free plan — no credit card required.
  • Unmetered traffic: images are served from Cloudflare's edge; reading them consumes no ABNCMS D1 / KV quota.
  • You own the files: images end up in your own repository — download or migrate them any time.
  • Generous capacity: free repository quotas are plenty for personal sites and small-to-medium content sites.
Real screenshot: image host frontend upload interface

Prerequisites#

  1. A Cloudflare account (for Pages and KV).
  2. A GitHub account (to fork the image-host source).
  3. A HuggingFace account (to store image files).
Terminology"Token" appears twice below with different roles: the HuggingFace Access Token lets the image host write to the repository; the image host's API Token lets ABNCMS upload images. Do not mix them up.

Step 1: Fork the image-host source#

Find an open-source image host that supports Cloudflare Pages deployment and a HuggingFace upload channel, then click Fork to copy it into your own account. Check three things:

Real screenshot: forking the open-source image host on GitHub
  • The repo includes the build scripts and wrangler / frontend directory structure needed by Pages.
  • The README states the build command and output directory (this guide uses npm install + /frontend-dist as an example — follow your chosen project's docs).
  • The admin panel supports multiple storage channels with customizable channel names and upload parameters — essential for ABNCMS integration.

Step 2: Deploy the image host on Cloudflare Pages#

In the Cloudflare dashboard go to Workers & Pages → Create application → Pages → Import from Git, pick your fork, and fill in the build settings as shown.

Real screenshot: Cloudflare Pages build config — project name, production branch main, npm install, /frontend-dist
Don't copy the build values blindlyBuild command and output directory vary by project. The image shows examples — always check the README of the repo you forked. Wrong values deploy "successfully" but yield a blank page or 404.

Step 3: Create and bind a Workers KV namespace#

The image host uses KV to store channel configuration. Create a namespace and bind it to the Pages project:

  1. Cloudflare dashboard → Workers & Pages → KV → Create a namespace; the name is arbitrary, e.g. img_url.
  2. Open the Pages project → Settings → Bindings → Add → select KV namespace.
  3. Set the "Variable name" to exactly img_url, choose the namespace you just created, and save.
  4. After binding, redeploy the project once for the change to take effect.
Real screenshot: KV namespace binding on the Pages project with variable name img_url
The variable name is fixedimg_url is hard-coded in the image host's source. Using IMG_URL, kv, or any other name means the app cannot read the configuration and the admin panel will misbehave.

Step 4: Create a HuggingFace write token#

The image host needs a token with write access to push images into your repository.

Real screenshot: HuggingFace console used to create a Write access token
  1. After signing in, click your avatar → Settings → Access Tokens → Create new token.
  2. Set Token type to Write (a Read-only token cannot upload).
  3. Give it a recognizable name and copy the token immediately — the full value is shown only once and cannot be retrieved later.

Step 5: Prepare the image repository#

Create a new repository on HuggingFace to hold your images and note its full name in the format username/repo-name (e.g. abncms/gallery). An empty repository is enough — the app writes files into it on first upload. For public external links without authentication, make the repository public; a private repository requires extra auth handling.

Real screenshot: HuggingFace image repository file list, images stored as LFS files

Step 6: Add the HuggingFace channel in the image host#

Open the Pages URL assigned to your image host and go to System Settings → Upload Settings → Add HuggingFace channel, then fill in the four fields as shown.

Real screenshot: HuggingFace channel and repository config in the image host upload settings
FieldValue
Channel nameA custom label such as hf-main; you'll pick this when setting the default channel
TokenThe HuggingFace Write Token copied in Step 4
Repository nameusername/repo-name, e.g. abncms/gallery
Private toggleMatch the repository's actual visibility; turn off for public repos

Save, then click "Test connection" to verify the channel (it checks connectivity only and does not upload a test image).

Step 7: Make the channel the default#

In Client Settings, set the default upload type to HuggingFace and the channel name to the one you created in Step 6. This step is the most commonly missed.

Skipping this breaks uploadsMany image hosts default to Telegram or another channel. If you add a HuggingFace channel but never switch the default, uploads go to the wrong channel and fail.

Step 8: Verify with a test upload#

  1. Back on the image host home page, drag in an image and copy the returned public URL.
  2. Real screenshot: image uploaded successfully with completed progress bar and file list
  3. Open the URL in a new tab — a 200 response showing the image means success.
  4. Check your HuggingFace repository to confirm the file was created automatically.

Using this image host in ABNCMS#

With the image host ready, go back to ABNCMS admin → Settings → Image Host:

  • Base URL: the Pages URL of your image host (e.g. https://your-host.pages.dev).
  • API Token: the upload token generated in the image host admin — not the HuggingFace token.
  • Click "Test connection", then save. From then on, inserting images in the editor or uploading a logo goes through /api/upload, with the Worker injecting the token server-side so the browser never sees the secret.
Two tokens, two jobsThe HuggingFace Token lets the image host write to its repository; the image host API Token lets ABNCMS call the image host. The former lives in the image host admin, the latter in ABNCMS settings — keep the direction straight.

Cost and quotas#

ComponentRoleOn the free plan
Cloudflare PagesHost the image host appNo server cost, global acceleration; image reads don't count toward ABNCMS
Workers KVStore channel configOnly a small config object — well below free read/write limits
HuggingFace repoStore image filesFree repository quota; you own the files and can export anytime

Free quotas change over time — check each provider's current terms before signing up. This setup has no server cost and does not consume your ABNCMS site's D1 write quota.

Troubleshooting#

SymptomWhere to look
"Channel not configured" or uploads hit the wrong channelCheck Step 7 — is the default channel switched to HuggingFace?
Config not read / disappears after savingConfirm the KV variable name is img_url and that you redeployed after binding
External link returns 403 / asks for loginRepository is private — make it public or configure auth per the project docs
Blank page after Pages deploymentWrong build command or output directory — fix using the forked repo's README
ABNCMS test connection failsUse the image host API Token (not the HuggingFace token) and ensure the host URL is publicly reachable

API Reference#

Main routes below; public front-end routes and admin routes are kept separate.

Public front-end routes#

PathDescription
/Homepage
/p/{slug}.htmlArticle (old /p/{slug} 301-redirects here)
/page/{slug}.htmlStandalone page
/c/{slug} / /t/{slug}Category / tag page
/tags / /archive / /searchTag cloud / archive / search
/feed.xml / /sitemap.xmlRSS / sitemap
/commentPost a comment (POST)
/media/*Legacy media file reads

Admin & system APIs#

PathDescription
/admin/login / /admin/logoutLogin / logout
/admin/post/* / /admin/page/*Post / page CRUD (auth required)
/admin/settingsSite settings (auth required)
/admin/backup/export|importBackup export / import
/api/uploadImage upload (auth required)
/api/previewMarkdown preview (auth required)
/api/ai/summary-tagsAI summary & tags (auth required)
/api/hitView beacon (public, same-origin check)
/api/healthHealth check

Directory Structure#

abncms/
├── src/
│   ├── index.ts              # all routes + Cron + cache strategy
│   ├── types.ts              # Env / SiteSettings / data types
│   ├── lib/
│   │   ├── db.ts             # D1 access layer, settings read/write
│   │   ├── auth.ts           # password hash, sessions, rate limit, Turnstile
│   │   ├── crypto.ts         # AES-GCM: encrypt/decrypt sensitive config
│   │   ├── imgbed.ts         # image host proxy: upload / delete / test
│   │   ├── markdown.ts       # zero-dep Markdown renderer (XSS-safe escaping)
│   │   ├── ai.ts             # Workers AI + Vectorize
│   │   └── util.ts           # slug / pagination / cookie / escaping
│   └── views/                # layout.ts / front.ts / admin.ts
├── public/                   # admin.js / favicon.svg / robots.txt
├── scripts/                  # setup_remote.py / migrate.py / smoke_test.py
├── migrations/               # incremental SQL migrations (idempotent)
├── schema.sql                # fresh install: idempotent tables + version baseline
├── seed.sql                  # neutral sample data
└── wrangler.example.jsonc    # configuration template

Data Model#

Data lives mainly in D1; the core tables are below.

TablePurpose
postsPosts (slug, status, views, cover)
pagesStandalone pages
categories / tags / post_tagsCategories, tags and their relations
usersAdmin accounts
commentsComments and moderation status
mediaUploaded media URLs
linksFriend links
settingsSite settings (key-value)
page_viewsView details (cleaned periodically by cron)

Backup export follows a fixed order: settings → categories → tags → posts → pages → links → comments → post_tags → media. Import handles relations likewise, excluding sensitive fields such as tokens.

FAQ#

Is it static after publishing?#

No static files are generated, but anonymous access behaves equivalently — an edge-cache hit returns complete HTML with 0 D1 and 0 KV operations, while the admin keeps content editable anytime.

Do I need a server or database host?#

No. Everything runs on Cloudflare Workers + D1 + KV, on the free plan with no credit card.

Do view stats consume quota?#

Each built-in hit writes two D1 rows, consuming D1 writes but no KV. It is off by default. Switching to a third-party analytics script brings analytics cost to zero.

How do I bind a custom domain?#

Add a custom domain in the Cloudflare Workers dashboard and set DNS accordingly; the platform issues the HTTPS certificate automatically.

Can it be accessed from mainland China?#

Actual reachability of workers.dev and custom domains depends on the local network. Binding your own domain is recommended for more stable access.

Troubleshooting#

SymptomFix
Turnstile says success but login failsSite Key and Secret must be replaced as a pair; if either side is a test key, the code lets it through
Can't change image-host token in adminCONFIG_ENCRYPTION_KEY is missing — currently "environment-variable mode"
"Image host not configured" on uploadSet URL and token in Settings → Image Host, or set the IMGBED_TOKEN secret
Site name reverts to defaultFallback when settings lacks the key or D1 fails; save once in the admin
Edited post not showing on front endEnsure v0.2.1+ is deployed; saving bumps cache_gen; if still stale it is browser cache — press Ctrl+F5
Logo / name / settings change not visibleSaving bumps the cache generation; if still stale run wrangler kv key delete settings:v1 --binding=KV --remote
View count stuck or jumpingStats are a 25% sample ×4 estimate; disable built-in stats and use a third-party script
Admin missing logo / image-host settings after upgradeRun python scripts/migrate.py on the old DB to add settings
Subdomain registration fails 10405Manually register the *.workers.dev subdomain in the Cloudflare dashboard

Community & Support#

ABNCMS is open source under the MIT license. Stars, issues and contributions are all welcome.

ChannelAddress / Method
GitHub sourcegithub.com/baiyirui/abncms
IssuesGitHub Issues
Websitecms.abn.cn
Live demoabncms.eu.cc
Emaila@abn.cn

License: MIT · See TRADEMARK.md in the repo for name and logo usage.