[U] Update channel content
This commit is contained in:
@@ -2,7 +2,7 @@
|
||||
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="zh-cn">
|
||||
<id>https://aza.moe/life</id>
|
||||
<title>小桂桂的回忆录 📒</title>
|
||||
<updated>2024-11-03T10:10:16.028976+00:00</updated>
|
||||
<updated>2024-11-03T12:11:20.184901+00:00</updated>
|
||||
<link href="https://aza.moe/life" rel="alternate"/>
|
||||
<generator uri="https://lkiesow.github.io/python-feedgen" version="0.9.0">python-feedgen</generator>
|
||||
<logo>https://aza.moe/meru_256px.png</logo>
|
||||
|
||||
File diff suppressed because one or more lines are too long
@@ -63256,7 +63256,7 @@
|
||||
"id": 4613,
|
||||
"date": "2024-11-03T02:01:28",
|
||||
"text": "今天晚上醒来看到凌莞反馈说服务器宕了,赶快起床看一看,发现 nginx 没起来,原因是其中一个 http 反代的上游死了配置文件检查没过...\n\n啊啊,真的是好蠢的设计,其中一个站点的反代挂了的话,服务起来剩下的站点还能用啊... 为什么要设计成一个连不上就不启动服务了?原本可以是 5% down 的现在变成了 100% down...\n\n感觉这已经是第无数次被 nginx 背刺了,之前还有发现 autoindex 在 ls 的时候会阻塞所有线程,然后之前我服务器上有一个几百万文件的文件夹,有人访问这个目录的时候就会让所有服务卡死不响应,而且去搜了解决方案似乎 2024 年都无解...\n\n真的不想再用 nginx 了,等这学期结束就全都换到 caddy",
|
||||
"views": 61,
|
||||
"views": 62,
|
||||
"forwards": 2,
|
||||
"images": [
|
||||
{
|
||||
|
||||
@@ -12,7 +12,7 @@
|
||||
<link>https://aza.moe/life</link>
|
||||
</image>
|
||||
<language>zh-cn</language>
|
||||
<lastBuildDate>Sun, 03 Nov 2024 10:10:16 +0000</lastBuildDate>
|
||||
<lastBuildDate>Sun, 03 Nov 2024 12:11:20 +0000</lastBuildDate>
|
||||
<item>
|
||||
<title>小桂桂的回忆录 📒 #4613</title>
|
||||
<link>https://aza.moe/life?post=4613</link>
|
||||
|
||||
Reference in New Issue
Block a user