我以email id: brightmann@gmail.com登录了https://app.notion.com/ 。(登录地址:
https://app.notion.com/login)。
以下是我跟muse的对话截图。共96张截图。从10月29号开聊,断断续续,搞到11月14号,才搞定。搞了17天。
(muse给我写的有关如何创建jb的一个源帖的答复,放到了其library里了,地址:
https://muse.ai/library/artifacts/how-to-publish-a-post-on-jb, 不过这并非public link, 只有我自己能访问。于是我要muse发表它的答复,获得了地址:
https://muse.ai/s/how-to-publish-a-post-on-jb-tw6ixlla6u8z/TwpQQ4AnmQvikdnOzqNWu4r9Zpc_oVWMEEz7cXab04o ,这个是public link,任何人都可以打开它。看了此答复后,我才彻底搞懂notion的数据库)






















































me: why on cloudflare workers, build the jb will fail but on github pages, build the jb will not fail?
Same code, different machine — and Notion judges the machine by its IP address.
The jb build pulls all your content from Notion at build time: the whole Blog Posts database plus the body of every post, in one burst of concurrent requests. Notion rate-limits by IP, and when it sees too many requests from one IP it answers 429 (Too Many Requests).
- Cloudflare Workers Builds runs on Cloudflare's shared build machines. Lots of users' builds share the same egress IPs, so Notion sees a flood from those addresses and throttles them hard. jb is hit especially hard because it fetches more than nnsk or ssm do in one burst — that's why jb is the exception and those two build fine on Workers.
- GitHub Actions runs on different IPs (Microsoft's Azure range) that aren't under that same shared load, so the exact same burst of requests goes through without tripping the limit.
The retry fix I pushed helps both, but on Cloudflare the throttling is so heavy that even retries can run out. That's why Pages builds reliably and Workers Builds doesn't, even though they're running the same build.
得到的博客地址:
https://jb.luckypoem.workers.dev/
https://brightmann.github.io/jb/
关于https://jb.luckypoem.workers.dev/的搭建:
在本地机器windows上。运行git-bash.exe, 在 git-bash.exe的窗口里,运行-
git clone https://github.com/brightmann/jb
cd jb
nvm use 24 (nodejs的版本最低要为20)
yarn
NODE_OPTIONS=--max-old-space-size=4096 yarn build
(磁盘的剩余空间要至少4096mb, 即4GB.否则build会遇错)
yarn export
CLOUDFLARE_API_TOKEN=CLOUDFLARE_API_TOKEN的值 CLOUDFLARE_ACCOUNT_ID=我的CLOUDFLARE_ACCOUNT_ID的值 npx wrangler deploy
等待部署(即上传)完成。部署(即上传)完成后,就会生成网址https://jb.luckypoem.workers.dev/。以后要更新网站,就运行上面的build, export, deploy命令即可。
关于 https://brightmann.github.io/jb/ 的更新:
手动更新一下你的repo https://github.com/brightmann/jb里面的文件,比如package.json,
把光标移到 package.json的最下面一行的下一行,按enter键,回一下车,然后保存更改。这样,仓库内容发生了变化,就会触发github pages平台的workflow,从而auto rebuild站点。2分钟后,网站https://brightmann.github.io/jb/就会更新。
或者访问 https://github.com/brightmann/jb/actions/workflows/deploy-pages.yml,点击右上角的run workflow按钮也行。
推荐搭建在 github pages平台,这种方式不受本地磁盘的剩余空间大小的限制,剩余空间即使在4 GB以下,也无所谓.
项目地址:
https://github.com/jkker/blog
https://github.com/brightmann/jb