看得透又看得远者prevail. ppt.cc/flUmLx ppt.cc/fqtgqx ppt.cc/fZsXUx ppt.cc/fhWnZx ppt.cc/fnrkVx ppt.cc/f2CBVx
t.ly/s0R4x t.ly/gDGm6 ppt.cc/fwlgFx ppt.cc/fVjECx ppt.cc/fEnHsx ppt.cc/fRZTnx ppt.cc/fSZ3cx ppt.cc/fLOuCx ppt.cc/fE9Nux ppt.cc/fL5Kyx ppt.cc/f71Yqx tecmint.com linuxcool.com linux.die.net linux.it.net.cn ostechnix.com unix.com ubuntugeek.com runoob.com man.linuxde.net ppt.cc/fwpCex ppt.cc/fxcLIx ppt.cc/foX6Ux linuxprobe.com linuxtechi.com howtoforge.com linuxstory.org systutorials.com ghacks.net linuxopsys.com ppt.cc/ffAGfx ppt.cc/fJbezx ppt.cc/fNIQDx ppt.cc/fCSllx ppt.cc/fybDVx ppt.cc/fIMQxx
Total Pageviews
Friday, 6 November 2026
崇禎為什麼一定要殺袁崇煥?
崇禎这个神经病抓了最会打仗的袁崇煥,活该他亡国。正像南宋的皇帝赵构抓了岳飞,南宋离亡国就不远了。
明朝历代皇帝
明朝自1368年朱元璋建立,至1644年崇祯帝自缢,共历十二世、十六位皇帝(若计入清兵入关后南方延续的南明政权则更多)
以下为明朝十六位皇帝的完整列表及主要历史标志:
顺序 庙号 姓名 年号 在位时间 历史要点与标志性事件
1 明太祖 朱元璋 洪武 1368—1398 建立大明,推翻元朝;废丞相、设锦衣卫,强化君主专制。
2 明惠宗 朱允炆 建文 1398—1402 太祖之孙;推行削藩政策,引发“靖难之役”,宫陷后不知所终。
3 明成祖 朱棣 永乐 1402—1424 太祖的第四子;发动靖难夺位,迁都北京,修《永乐大典》,派郑和下西洋。
4 明仁宗 朱高炽 洪熙 1424—1425 成祖的长子;休养生息,开创“仁宣之治”的序幕(在位仅10个月)。
5 明宣宗 朱瞻基 宣德 1425—1435 仁宗的长子;与父共创“仁宣之治”,明朝国力达到鼎盛时期。
6 明英宗 朱祁镇 正统 / 天顺 1435—1449 1457—1464 两次在位;亲征漠北,发生“土木堡之变”被蒙古人俘虏,后经“夺门之变”复辟。
7 明代宗 朱祁钰 景泰 1449—1457 英宗之弟;在土木堡之变后临危受命登基,任用于谦取得“北京保卫战”胜利。
8 明宪宗 朱见深 成化 1464—1487 英宗的长子;平反于谦,前期励精图治,后期宠信万贵妃、设立西厂。
9 明孝宗 朱祐樘 弘治 1487—1505 宪宗的三子;勤政爱民,整顿朝政,史称“弘治中兴”,终身未纳妃嫔。
10 明武宗 朱厚照 正德 1505—1521 孝宗的长子;性格桀骜叛逆,建“豹房”,自封“威武大将军朱寿”。
11 明世宗 朱厚熜 嘉靖 1521—1566 武宗的堂弟(宪宗之孙);引发“大礼议”,后期沉溺修道、二十余年不视朝,发生“壬寅宫变”。
12 明穆宗 朱载垕 隆庆 1566—1572 世宗的三子;推行“隆庆开关”开放海禁,与蒙古达成“俺答封贡”。
13 明神宗 朱翊钧 万历 1572—1620 穆宗的三子;前期任用张居正主持改革,后期发生“万历怠政”与“万历三大征”。
14 明光宗 朱常洛 泰昌 1620 神宗的长子;因“红丸案”即位仅一个月猝逝,史称“一月皇帝”。
15 明熹宗 朱由校 天启 1620—1627 光宗的长子;酷爱木工,朝政大权落入宦官魏忠贤与客氏之手。
16 明思宗 朱由检 崇祯 1627—1644 朱由校之弟
陈平下令,将吕氏族人通通诛杀
学学中国人的智慧,尤其是陈平的谋术值得好好学学!
张良,陈平以前都是项羽的谋臣,但都被项羽气走,投奔了刘邦。项羽要是听得进他们的言语,恐怕刘邦难以获得天下。
让muse帮我在cloudflare.com平台上,构建基于nextjs的静态博客程序'rr-dev'
我用email id: luckypoem@gmail.com登录cloudflare.com平台。
me: can u build https://github.com/brightmann/rr-dev? subdomain use rr-dev.luckypoem.workers.dev
Noted — rr-dev.luckypoem.workers.dev it is. The repo's still cloning; I'll build it for that subdomain.
me: finished?
Not yet. The build itself passes now and the Worker is built, but my local test of it 404s on every page — homepage, docs, your 战马 post, all of it. The prerendered pages are in the output, so the Worker just isn't finding them. I'm diagnosing that cache lookup now before I push anything.
me: 'The build itself passes now'. what's the preview url?
There isn't one yet. Nothing's deployed to Cloudflare — the build passes and the Worker bundle is built locally, but my local test of it 404s every page, so I haven't pushed or deployed anything. No live URL exists until that 404 is fixed and it goes up as rr-dev.luckypoem.workers.dev.
me: still not finished? so long time, 6 hours.
It's this close. The site itself is verified working — homepage, docs, your 战马 post, all 820 pages return 200 from the Worker build. One gap: the raw-markdown endpoint (/api/md/...) 404s on Workers, because that handler reads files off disk and a Worker has no disk. The HTML pages are unaffected; that's a follow-up fix.
To go live I need one thing from you: an rr-dev PAT so I can push the deploy commit, then I'll wire up Workers Builds for auto-rebuilds.
me: my github pat here...
Pushed — commit d71f3d27 is on brightmann/rr-dev main, remote is clean. That PAT is revocable now.
I've started the Workers Builds project setup in your Cloudflare dashboard — it'll build and deploy to rr-dev.luckypoem.workers.dev. I'll check it live once the build finishes and report back.
The Builds project is created, but the first build failed on one thing: the adapter wants Next 15.5.28+, the repo pins 15.1.12, so npm refused the install. The adapter itself works fine with 15.1.12 — I verified that locally — so I've sent a fix to just add --legacy-peer-deps to the install step and rebuild. Nothing in the repo needs to change.
That retry failed on a different thing: npm can't handle this repo's link:eslint-local-rules local dependency at all — same wall I hit locally. The fix is to install those two packages with Yarn instead of npm, since Yarn understands the link: dep and only warns on the Next version. Sent that change through, rebuilding now.
One step further — the Yarn install worked, and now the build fails only because the adapter expects wrangler installed alongside it and it isn't in the repo. Added wrangler to the install step, rebuilding now.
'Added wrangler to the install step' means u will push wrangler.jsonc to my repo?
No — nothing new goes into your repo.
wrangler.jsonc (the config) is already there, pushed in d71f3d27. What I added is the wrangler program itself — the command-line tool that does the deploying. Cloudflare's build machine didn't have it installed, so the build command now just installs it on that machine at build time, alongside the adapter. It's a dashboard setting change only, no commit, no push.
The rebuild with it is still running — I'll report once it's done.
Live. Verified myself just now: homepage, /learn, and your 战马 post all return 200. https://rr-dev.luckypoem.workers.dev/
Pushes to main will auto-rebuild from here. Two known gaps if you ever want them: the /api/md raw-markdown endpoint doesn't work on Workers yet, and the 51 Vercel redirects weren't ported.
me: totally how many md files are there in https://github.com/brightmann/rr-dev/tree/main/src/content/blog?
26 — all .md, no .mdx files in there. including index.md
me: can u make https://rr-dev.luckypoem.workers.dev/blog support pagination? 5 posts per page.
Pushed — commit 76fe7b52, and the auto-rebuild is running. I'll check it live once the new build lands.
How it works: /blog shows the first 5 posts with a Previous | 1–5 | Next pager, and /blog/page/2 through /blog/page/5 hold the rest. One thing to know: the listing is a hand-written list in the repo(it's index.md file), so when you add a new post card at the top, the pages shift and need re-slicing — just say the word when you add one and I'll do it. Same PAT as before, still revocable.
我得到的博客地址: https://rr-dev.luckypoem.workers.dev/blog
项目地址:
https://github.com/reactjs/react.dev
https://github.com/briteming/rrd
https://github.com/brightmann/rr-dev
创建源帖的方法:
在此处 https://github.com/brightmann/rr-dev/tree/main/src/content/blog,新建文件夹2026/11/06/,然后在里面,新建advice.md文件,内容为:
---
title: "人生忠告"
author: ym
date: 2026/11/06
description: 这是一篇文章
---
November 06, 2026
---
此处写正文或html codes
(详见https://github.com/brightmann/rr-dev/blob/main/src/content/blog/2026/11/06/advice.md?plain=1)
创建源帖后,稍等1-2分钟,对应的帖子https://rr-dev.luckypoem.workers.dev/blog/2026/11/06/advice就会生成。不过暂时还不会出现在https://rr-dev.luckypoem.workers.dev/blog/里面。
还需编辑 https://github.com/brightmann/rr-dev/tree/main/src/content/blog/里面的index.md文件。访问https://github.com/brightmann/rr-dev/blob/main/src/content/blog/index.md?plain=1 ,进行编辑:
在第13行的下一行加上
<BlogCard title="人生忠告" date="November 06, 2026" url="/blog/2026/11/06/advice">
这是一篇文章
</BlogCard>
保存更改(即提交commit), 然后等候约7分钟,博客网站https://rr-dev.luckypoem.workers.dev/blog/ 才会更新,即帖子https://rr-dev.luckypoem.workers.dev/blog/2026/11/06/advice 才会出现在https://rr-dev.luckypoem.workers.dev/blog/里面。
(其实,对应于仓库 https://github.com/briteming/rrd,我在6月份时,就在vercel.com/new搭建了博客https://rrd-dusky.vercel.app/blog 。6月份时,创建的源帖https://github.com/briteming/rrd/blob/main/src/content/blog/2026/06/03/fh.md?plain=1成功转化为了帖子
https://rrd-dusky.vercel.app/blog/2026/06/03/fh并出现在了 https://rrd-dusky.vercel.app/blog/里面,而在8月份时,创建的源帖https://github.com/briteming/rrd/blob/main/src/content/blog/2026/08/01/ce.md?plain=1虽然成功转换为了帖子https://rrd-dusky.vercel.app/blog/2026/08/01/ce ,但就是没有出现在https://rrd-dusky.vercel.app/blog/里面,很奇怪。尽管在https://github.com/briteming/rrd/blob/main/src/content/blog/index.md?plain=1里面,我添加了ce条目)