Arkylin的小屋

主页标签栏留白修复:min-width 与溢出收缩的冲突

2026-08-10T12:37:26.000Z

前阵子折腾主题(ark)的编辑器标签栏,发现固定在最左边的”主页”标签格外宽,右侧拖着一串空白,跟旁边的文章标签放一起很突兀。这篇记录定位与修改过程,以及为什么最后又回滚了。

现象:主页标签太长,一串空白

标签栏(.editor-tabline)长这样:左边贴着一个固定不动的”主页”标签,后面是当前打开的文章标签。主页标签只有一个小图标加”主页”两个字,却占了整整 132px,右边一大片空白。

上排是修改前,下排是修改后(宽度贴着内容走)。视觉上就是”太长,有一堆空白” vs “刚好贴合”。

定位:132px 来自基础规则的 min-width

.editor-tab 的基础规则给所有标签设了一个统一的最小宽度,这是为了多标签时观感整齐:

.editor-tab {
  ...
  max-width: min(260px, 70vw);
  min-width: 132px;
  ...
}

对普通文章标签来说 132px 没什么问题——标题长,本来就要占位。但”主页”标签固定贴左、只有俩字,132px 就明显偏宽了。

有意思的是,标签栏溢出时(打开的标签太多,一行放不下)其实有一套收缩规则,会把主页标签从 132px 缩成一个 40px 的纯图标:

.editor-tabline.is-overflowing .editor-tab.is-pinned {
  min-width: 40px;
  max-width: 40px;
  justify-content: center;
  padding: 0 7px;
  gap: 0;
}

所以问题只出在没溢出的时候——一切正常,主页标签就是 132px 宽,空白常驻。

修改:给 .is-pinned 加 min-width: 0

让主页标签不再被 132px 的最小宽度撑开,宽度改由内容决定:

.editor-tab.is-pinned {
  position: sticky;
  left: 0;
  z-index: 2;
  min-width: 0;   /* 新增:允许收缩到内容宽度 */
  gap: 7px;
}

.editor-tab.is-pinned 本身没有覆盖 min-width,所以基础规则的 132px 一直压在它头上;补上 min-width: 0 后,标签宽度 = 图标 + 文字 + padding,约 68px,空白消失。

副作用:左右留白不对称

改完立刻暴露了另一个问题——标签的左右 padding 本来就不对称:

.editor-tab {
  padding: 0 9px 0 13px;   /* 左 13px,右 9px */
}

左 13px 右 9px 的 4px 差,在 132px 宽时被大留白盖住根本看不出来;一旦缩到 68px,左右明显不一样齐,视觉上反而更难受。

回滚与取舍

考虑到左右不对称比”有点空”更扎眼,最终把 min-width: 0 撤掉,恢复了原来的样子。真正要落地,得把两个值一起改:

min-width: 0(收窄标签)+ padding 改成左右对称,比如 padding: 0 11px;
或者干脆接受 132px 的既有设计。

这次折腾的教训:缩小一个元素之前,先想清楚它的 padding/margin 是不是为原来的尺寸服务的。132px 的宽度恰好掩盖了不对称的内边距,一收缩就原形毕露。改宽度不是孤立的一行代码,得把”邻居”一起看。

构建与部署的增量双双失灵:9 张图片和 1915 个文件背后的三个坑

2026-08-06T14:30:00.000Z

连续跑两次 npm run deploy,输出几乎一模一样:

[postbuild] 图片: 处理 9 张, 缓存跳过 359 张
[postbuild] 完成 (8.4s): ... 水印 0 张
[deploy-oss] 完成: 上传 1915, 跳过 0, 删除 11

两个”增量”全失灵了:postbuild 的图片缓存每次都有 9 张要重处理,OSS 部署则 1915 个文件一个不少全部重传。逐个排查,最后发现是三个互不相干的坑叠在一起:一个被静默吞掉的 Windows 文件锁错误、一个恒为假的 if 条件、一个非确定性的混淆器。完整记录一下。

坑 1:那 9 张图片为什么永远处理不完

postbuild 的图片缓存是内容寻址的:先算文件 md5,拿 md5_版本号.扩展名 去 node_modules/.astro/postbuild-images/ 里找处理好的成品,命中就 copyFileSync 回 dist,否则重新压图加水印并存缓存。设计上,只要某张图成功处理过一次,下次 astro build 重建出原始文件后必然命中缓存。

所以”每次都有 9 张被处理”只有一种解释:这 9 张从来没成功过,永远写不进缓存。用诊断脚本把 368 张图全部过一遍,找出没有缓存命中的 9 个:

images\2021\01\1706928628.png        0B    ← 零字节
images\2023\05\2397264479.png        0B    ← 零字节
images\2024\04\img_20240413_...-300x225.jpg
images\2025\03\B4572CD5...-135x300.jpg
images\2025\03\B4572CD5...-150x150.jpg
posts\happy-new-year2022\images\1641018313861.jpeg
posts\loom\images\3064128888.jpg
posts\start\images\963228996.jpg
_astro\image_editor_output_...CYf17VBA.jpg

两个现象立刻对上:7 张 jpg + 2 张零字节 png,而构建日志里”水印 0 张”——水印计数只在处理成功时 +1,0 说明这 9 张全军覆没。再往 optimizeImage 的 catch 里补一行日志,真相浮出水面:

PROCESS ERR: 3064128888.jpg -> UNKNOWN: unknown error, open 'D:\...\dist\posts\loom\images\3064128888.jpg'

7 张 jpg 全是同一个错误:按文件路径打开失败。 而奇怪的是,同样这几张图,先读进内存再喂给 sharp 就完全正常;同一张图换个时机再按路径打开也偶尔能成功。这是 Windows 上典型的瞬时文件锁问题(防病毒实时扫描、句柄竞争都会触发),原代码 catch { return null } 把错误静默吞掉,不写缓存,于是每次构建都重新踩一遍。

另外 2 张是 public/ 里的零字节 png,处理函数里有 size < 512 直接 return 的保护,同样不写缓存,每次构建都进”处理”计数。这两个文件在线上会返回空文件,属于源数据问题,顺手把它们单独列出来警告。

修法:全程改用内存 buffer 处理(读一次、哈希一次、sharp 吃 buffer,不再反复按路径开文件),加 3 次重试,失败时打印真实错误而不是吞掉。改完连续构建两次,输出变成:

[postbuild] 图片: 处理 0 张, 缓存跳过 366 张
[postbuild] 跳过过小图片 0B: images\2021\01\1706928628.png
[postbuild] 跳过过小图片 0B: images\2023\05\2397264479.png

9 → 0。之前没修好的 7 张 jpg 也一次性补上了缓存。

坑 2:deploy-oss 的跳过条件恒为假

再看部署脚本,跳过 0 直接指向这一行:

const full = path.join(distDir, rel);          // ← 路径字符串,永远为真
if (!full && remote && remote.size === size) { // ← !full 永远为假!

变量名 full 把本地文件的完整路径和 --full 全量上传的标志位搞混了。路径字符串非空,!full 恒为 false,整个”大小相同再比 etag、相同就跳过”的分支永远不会执行——所以每次部署都把 1915 个文件原样重传一遍。etag 比对逻辑本身是好的(简单上传的 OSS etag 就是内容 md5,比它和本地 md5 相等即可跳过)。

修法:条件改成 absPath && remote && remote.size === size && !fullFlag,路径存在、远端大小一致、md5 一致才跳过;--full 时强制不跳过,语义也终于落实了。

坑 3:混淆器是非确定性的,这才是增量失效的真凶

修完前两个坑,做了个更严格的验证:连续构建两次,逐文件对比 md5。结果仍然有 1200+ 个 HTML 在变。增量部署直接不可能——因为 HTML 每次都在变。

顺着 HTML 的引用链找,资源重命名 21 个 每次都把 theme JS 改成带新 hash 的名字。JS 每次字节都不同,是谁在写?是 obfuscate。javascript-obfuscator 没设 seed 时,标识符生成用的是真随机数:

输出1: 6416  输出2: 6423  完全一致: false

同一份输入,两次输出不一样。于是:混淆输出变 → 文件名 hash 变 → 所有 HTML 里的引用变 → 全站 HTML 重传。增量部署是”文件没变就不传”,而它每次都在变,部署自然只能全量。

修法一行:混淆选项里加固定 seed(seed: 20240806),输出变为确定:

输出1: 6421  输出2: 6421  完全一致: true

验证:字节级稳定 + 增量生效

修完三个坑,连续构建两次,逐文件比对:

两次构建文件差异数: 2
=> dist\posts\test-astro-encrypted\index.html|38433732...
<= dist\posts\test-astro-encrypted\index.html|D4BF80F3...

1915 个文件,只剩 1 个不同——test-astro-encrypted 那篇加密文章,它的内容本身带动态成分,每次构建真的在变,属于正确行为。其余 1914 个文件字节级一致,远程 etag 比对会全部跳过。

经验总结

“每次都在重试的活” = 永远没成功过的活。内容寻址缓存下,只要成功一次就不可能反复处理;反复处理必然意味着每次都在失败,而且失败被吞了。水印 0、跳过 0 这类”结果计数器”,是判断是不是白干的第一信号;
静默 catch 是调试黑洞。catch { return null } 省一时日志,欠下的是每次构建 8 秒的隐性重试和事后 40 分钟的排查。生产脚本里处理失败至少要打一行;
变量名别用业务标志位。full 同时指”完整路径”和”—full 全量标志”,一个笔误让跳过分支 6 个月没执行过。absPath vs fullFlag 这类命名不是洁癖,是防呆;
任何带随机数的处理都不配谈增量。混淆、压缩、图片编码……只要输出不确定,下游的”内容没变就不传”就全部失效。要确定性,给随机源加 seed,并在 CI 里用”两次构建字节级 diff”兜底;
Windows 上 sharp 按路径打开文件会偶发失败,读进内存再处理更稳,还能顺手省掉多次打开同一文件的 IO。

Astro 构建再提速:把侧边栏从组件改成字符串生成器,13.4s → 6.9s

2026-08-06T13:13:00.000Z

上一篇把构建从 31s 干到 13.4s 之后,剩余的大头就很明显了:每页都要重新渲染一遍 ~195KB 的侧边栏。这篇记录把侧边栏从 Astro 组件改成纯字符串生成器的过程——包括中途踩的两个坑(日期格式化居然要 14ms/页、Astro 的属性转义和文本转义规则不一样),以及如何用字节级 diff 保证输出零变化。最终 13.4s → 6.9s,侧边栏输出与改前逐字节一致。

现状:侧边栏是最后的成本大头

先量化。临时把 BaseLayout 里的 <Sidebar data={sidebar} /> 注释掉,对比构建:

指标	优化前(13.4s)	去掉侧边栏后
文章页平均耗时	23ms	3.2ms
列表页平均耗时	7.6ms	2.1ms
整站构建	13.4s	6.0s

侧边栏占了 ~7.4s。原因很直白:侧边栏要在 4 个视图(文件树/搜索/时间线/分类标签)里输出 220 篇文章 × 1000+ 个链接,数据层虽然做了构建期缓存,但 Astro 模板机制每页都要完整执行一遍。

方案选择:为什么不用 AstroContainer

理想方案是在构建时把侧边栏渲染一次存缓存,跨页复用。三条路:

字符串生成器:用 TS 函数拼 HTML 替换组件——无容器依赖,dev/prod 行为一致,数据现成(每页 frontmatter 里已有 SidebarData);
AstroContainer 预渲染:集成 hook 里 renderToString 一次——模板零改动,但集成 hook 里拿不到 astro:content 数据(getCollection 只能在页面渲染上下文调用),dev/prod 还要双路径;
客户端补高亮:渲染一次 + inline JS 加 is-current——改动最小,但无 JS 时高亮丢失,而且同样卡在方案 2 的数据访问问题。

选 1。侧边栏 HTML 只依赖 SidebarData + currentPath(唯一差异是当前链接的 is-current class),完全确定性输出,字符串生成器天然合适。

实现:照抄模板,然后被两个坑教做人

写了 themes/ark/src/lib/sidebar-html.ts,把 Sidebar.astro 的 4 个视图逐行翻译成字符串拼接。第一版跑起来,构建……还是 13s,文章页还是 22ms?!

给生成器加分段计时,真相大白:

[DEBUG sb] search: 0.3ms    ← 文件树 + 搜索区,飞快
[DEBUG sb] timeline: 6.1ms
[DEBUG sb] taxonomy: 17.9ms
[DEBUG sidebar] buildMs=25.1  ← 整个生成器

坑 1:partsInTZ 的 6 次 .find()。 搜索视图 220 次 + 时间线 440 次 fmtDate 调用,每次都要对 formatToParts() 的结果数组做 6 次线性查找,实测 21µs/次,660 次 ≈ 14ms。esc() 反而只要 0.03µs,字符串拼接 2600 段只要 0.27ms——之前给 esc 加快速路径纯属白忙。

修法分两层:

partsInTZ 改成单遍 switch 解析(21µs → ~4µs);
更狠的一招:日期字符串在构建期缓存里预计算。buildSidebarBase 本来就是每个构建算一次,顺手把每篇文章的 ymd/year/md 三个字符串存进去,生成器直接读,每页 660 次 fmtDate → 0 次。

生成器从 21ms 掉到 ~1ms,构建 6.9s。

坑 2:Astro 的序列化细节。 想要字节级一致,还得复刻三个细节,都是我靠 diff 逐个揪出来的:

元素间无空白——组件输出里 </section><section> 之间没有任何换行缩进,Astro 会剥离模板里的空白文本节点;
空字符串属性渲染为裸属性——data-admin-page(不是 ="");
属性转义 ≠ 文本转义——属性值只转义 & < > "(双引号内 ' 安全),文本才转义全部 5 个字符。所以生成器拆成 escAttr / escText 两个函数。

验证:字节级 diff

由于输出完全确定,验证可以做得非常硬:把改前构建的 6 个代表页面(文章页/首页/标签页/404/设置/归档)存下来,提取侧边栏块,与改后逐字节对比:

old len: 263860 new len: 263860
IDENTICAL

全部 6 个页面(包括整页,不止侧边栏)完全一致。dev 模式冒烟:文件树展开、搜索、时间线、is-current 高亮定位、导航脚本、data-admin-page 全部正常。

结果

指标	优化前	优化后
侧边栏生成耗时	21ms/页	~1ms/页
文章页平均耗时	23ms	~3ms
列表页平均耗时	7.6ms	~2ms
整站构建	13.4s	6.9s

从最初的 31s 到 6.9s,共 4.5 倍提速。侧边栏输出 263860 字节与改前逐字节一致,Sidebar.astro 组件已删除(单实现,无漂移风险)。

经验总结

预计算要下放到缓存层,而不是渲染层。数据层缓存(Astro 模板)救不了模板层的重复执行;但把格式化结果塞进数据缓存,渲染层就能归零;
别信直觉,给代码分段计时。esc 快速路径、数组 join 这些”明显该优化”的点全是无关紧要的,真正的大头是藏在 partsInTZ 里 6 次 .find() 的 14ms;
字节级 diff 是重构安全网。字符串生成器的最大风险是标记复刻不精确,而确定性的输出让”逐字节一致”从口号变成可执行的验证脚本;
Astro 的转义是分场景的。属性只转 & < > ",文本转 5 个字符,空字符串属性输出裸属性——做这类等价重写前,先翻一遍目标 HTML 确认序列化规则。

静态站点文章加密实现详解:PBKDF2 + AES-256-GCM 全流程

2026-08-06T13:00:00.000Z

本站最近上线了文章加密功能——给文章 frontmatter 加一个 password 字段,正文就会以密文形式发布,访客输入密码才能阅读。这篇把整个实现过程完整记录下来:加密算法的选择、构建期如何加密、浏览器端如何解密、以及配套的防泄露处理。

先说明一个重要前提:本站是纯静态站点(Astro 构建产物直接丢 OSS),没有任何服务端。所以加密只能在”构建时”做、解密只能在”浏览器端”做。这意味着它本质上是”防君子不防小人”的伪装加密——后面会专门讨论这个问题。

整体架构

写文章(index.md,含 password 字段)
        │
        ▼
Astro 构建期 ──► LockedContent.astro 加密正文(PBKDF2 + AES-256-GCM)
        │                密文 bundle 写入 HTML
        ▼
静态 HTML(正文以密文形式存在,页面只有锁表单)
        │
        ▼
浏览器加载页面 ──► 访客输入密码 ──► Web Crypto API 解密 ──► innerHTML 注入正文

关键点:dist 产物里永远没有明文。搜索引擎爬虫、RSS 订阅器、直接看源码的人,拿到的都是密文。

为什么不用 MD5 + AES-CBC

参考过不少静态站加密方案(比如某博客的 Pelican 加密插件),常见做法是:

var key = CryptoJS.MD5(password);           // 密码直接 MD5 当密钥
CryptoJS.AES.decrypt(bundle, key, { iv: iv, padding: CryptoJS.pad.NoPadding });

这个方案有两个明显弱点:

MD5 无 KDF。密码空间有多大,暴力尝试的成本就有多低。现代 GPU 算 MD5 每秒能跑几十亿次,六位数字密码瞬间被扫完;
AES-CBC 不认证。密码错了也能”解出”一堆乱码,没法区分是密码错了还是内容坏了,交互上只能靠”解出的不是合法 UTF-8”来猜。

所以本站换成了 PBKDF2 + AES-256-GCM:

环节	选型	理由
密钥派生	PBKDF2(21 万次迭代, SHA-256, 随机 16 字节 salt)	把单次尝试成本抬高到几十毫秒级,暴力破解需要 21 万倍算力
加密算法	AES-256-GCM	带认证标签,密码错误直接解密失败,不会吐乱码
随机数	每次构建重新生成 salt + IV	同一篇文章每次构建的密文都不同,防止重放与字典比对

为什么不直接用 scrypt/Argon2?因为解密必须跑在浏览器端,Web Crypto API 原生支持 PBKDF2,而 scrypt/Argon2 要么没有原生实现、要么需要引入 WASM 依赖。PBKDF2 + 高迭代已经是”零依赖且够用”的平衡点。

构建期加密:LockedContent.astro

加密逻辑写在一个 Astro 组件里,文章页检测到 password 字段就渲染它。组件的 frontmatter(构建时在 Node 里执行)负责加密:

import { createCipheriv, pbkdf2Sync, randomBytes } from 'node:crypto';

const { password = '', content = '' } = Astro.props;

// 1. 随机 salt + IV,每次构建都不同
const salt = randomBytes(16);
const iv = randomBytes(12);

// 2. PBKDF2 派生 256-bit 密钥(21 万次迭代)
const key = pbkdf2Sync(password, salt, 210_000, 32, 'sha256');

// 3. AES-256-GCM 加密
const cipher = createCipheriv('aes-256-gcm', key, iv);
const ct = Buffer.concat([cipher.update(content, 'utf8'), cipher.final()]);
const tag = cipher.getAuthTag();   // 16 字节认证标签

// 4. bundle = base64(salt) . base64(iv) . base64(密文 || tag)
const bundle = [
  salt.toString('base64'),
  iv.toString('base64'),
  Buffer.concat([ct, tag]).toString('base64'),
].join('.');

组件模板里渲染一个锁表单,并把 bundle 放在隐藏 div 里(供客户端脚本读取),同时注入解密脚本:

<div class="locked-post" data-locked-post>
  <div data-locked-bundle hidden>{bundle}</div>
  <p>内容已加密,输入密码解锁查看</p>
  <form data-locked-form>
    <input type="password" data-locked-input placeholder="密码" />
    <button type="submit">解锁</button>
  </form>
  <p data-locked-error hidden>密码错误,请重试</p>
</div>

注意 tag 是拼接在密文末尾一起交给浏览器的——Web Crypto 的 AES-GCM.decrypt 默认按”密文尾部 128 位是标签”解析,和 Node 侧”先密文后 tag”的存储格式正好对上,两端都零配置。

浏览器端解密:Web Crypto API

解密脚本用浏览器原生 crypto.subtle,零外部依赖,不引 crypto-js,也不怕 CDN 挂掉:

const [saltB64, ivB64, dataB64] = bundle.split('.');

const toBuf = (b64) => {           // base64 → Uint8Array
  const bin = atob(b64);
  const buf = new Uint8Array(bin.length);
  for (let i = 0; i < bin.length; i++) buf[i] = bin.charCodeAt(i);
  return buf;
};

form.addEventListener('submit', async (e) => {
  e.preventDefault();
  try {
    // 1. 同样的 PBKDF2 派生流程,参数必须与构建期完全一致
    const keyMaterial = await crypto.subtle.importKey(
      'raw', new TextEncoder().encode(password), 'PBKDF2', false, ['deriveKey']
    );
    const key = await crypto.subtle.deriveKey(
      { name: 'PBKDF2', salt: toBuf(saltB64), iterations: 210000, hash: 'SHA-256' },
      keyMaterial,
      { name: 'AES-GCM', length: 256 },
      false, ['decrypt']
    );

    // 2. 解密。密码错误时认证失败会直接抛异常
    const plain = await crypto.subtle.decrypt(
      { name: 'AES-GCM', iv: toBuf(ivB64) }, key, toBuf(dataB64)
    );

    // 3. 注入正文,并让 Prism 重新高亮代码块
    const host = document.createElement('div');
    host.innerHTML = new TextDecoder().decode(plain);
    root.replaceWith(host);
    // Prism.highlightElement(...) 处理 pre code
  } catch (err) {
    error.hidden = false;          // 密码错误
    input.value = '';
    input.focus();
  }
});

解密流程和构建期加密严格对称,只有一处不需要对称:密码。解密只拿 bundle + 用户输入的密码,salt/IV/迭代次数全部来自页面本身。

接入文章页与防泄露处理

加密不只是”把正文换掉”那么简单——如果其他页面还带着正文摘要,等于没加密。所以配套处理了所有可能泄露正文的地方:

位置	处理
`posts/[slug].astro`	有 `password` 时正文渲染为锁组件,跳过 TOC 提取,meta description 换成”🔒 本文内容已加密”
RSS(`index.xml.ts`)	加密文章的 description 替换为通用提示,不再输出完整正文
列表/归档/终端摘要(`postSummary`)	返回”🔒 内容已加密,输入密码查看”,不读取正文
`sitemap`	保留 URL(让文章可以被找到),正文本就不在页面里

文章页的判断逻辑很简单:

const isLocked = !!entry.data.password;
const toc = isLocked ? null : extractToc(entry.rendered?.html ?? '');
// ...
{isLocked ? (
  <LockedContent password={entry.data.password} content={entry.rendered?.html ?? ''} />
) : (
  <Content />
)}

其中 entry.rendered.html 是 Astro 已经把 Markdown 渲染成 HTML、处理完相对路径后的成品,加密的是这个最终 HTML,而不是原始 Markdown——所以图片链接、代码高亮等行为和解密前完全一致。

使用方式

在文章 frontmatter 加一行即可,不需要任何其他操作:

---
title: "测试Astro加密文章"
password: "你的密码"
date: "2026-08-06T10:00:00+08:00"
---

构建后正文以密文进入 dist,页面只有锁表单;
删除 password 字段即恢复公开;
已经可以正常配合 RSS/归档/侧边栏使用(摘要自动替换)。

安全性讨论:它到底能防什么

必须诚实地说清楚边界。静态站 + 客户端解密 = 无法做到真正的保密,原因很直接:

密文、算法、盐、迭代次数全部公开。攻击者拿到页面源码就能离线暴力破解,唯一的成本就是 PBKDF2 那 21 万次迭代;
密钥最终在浏览器里。只要攻破任意一个访客的浏览器,就能看到解密后的明文,无法做到”只有指定的人能看”;
明文仍在 git 仓库里。仓库是私有的没问题;如果仓库公开,加不加密码都一样。

所以它实际提供的是:

防护对象	效果
搜索引擎/爬虫索引正文	✅ 有效(爬虫不跑 JS,拿不到密文内容)
RSS 订阅器看到正文	✅ 有效(description 已替换)
直接翻源码的人	✅ 有效(只有密文)
拿到 HTML 离线爆破的”有心人”	⚠️ 取决于密码强度,21 万次 PBKDF2 把单次尝试抬到几十毫秒级,弱密码仍可能被字典击穿
被社工/被攻破浏览器	❌ 无效

给使用者的建议:密码务必用长随机字符串(比如 16 位以上),不要用生日、手机号这类可枚举的值。密码强度足够时,PBKDF2 已经能挡住绝大多数”顺手看看”级别的尝试。

验证:构建产物检查

最后一步是在构建后确认真的没有明文残留,这一步建议写进发布流程:

# 以测试文章为例,全站 HTML 里搜正文特征短语,应当零命中
grep -r "正文特征短语" dist/ --include="*.html"
# 加密文章页应当存在锁表单与密文 bundle
grep -o 'data-locked-bundle' dist/posts/<slug>/index.html

本站实测:构建后全站 HTML、RSS、_astro 资源里都搜不到正文特征串,浏览器端用正确密码可以完整还原(含代码高亮),错误密码被 GCM 认证拒绝。

经验总结

静态站加密的定位是”防君子不防小人”,别指望它做身份鉴别。要做真正的权限控制,必须有服务端;
KDF 比加密算法本身更值得花心思。MD5 当密钥的 AES-CBC 方案被秒破不是 AES 的问题,是 KDF 的问题;
GCM 的认证特性是 UX 加分项——错误密码直接报错,不用靠”乱码检测”猜;
加密要配套处理所有出口。正文换了密文,meta description、RSS、摘要、TOC 这些”隐形的正文副本”也得一起处理,否则白加密;
构建期加密 + 浏览器原生 Web Crypto 解密,整个链路零 npm 依赖,这是静态站方案里比较省心的组合。

Astro 构建提速 2.3 倍:从构建日志里揪出 Intl.DateTimeFormat 的隐形开销

2026-08-06T12:18:00.000Z

这两天给博客加了不少新文章,发现 npm run build 越来越慢(31 秒)。盯着构建日志看,有个现象很蹊跷:带 /published/ 前缀的跳转页生成飞快(+1ms),而 /posts/ 下一堆页面却要 50~130ms。本来以为是 aliases 跳转页拖慢的,查到最后发现——慢的根本不是 aliases,而是一个藏在日期格式化里的隐形开销。完整记录一下排查过程,顺便把 Intl.DateTimeFormat 这个坑分享出来。

起因:先量化”慢”

站点结构大致是:

astro.config.mjs 里把 842 条旧链接别名配进 redirects,构建时生成静态跳转页;
文章页由 src/pages/posts/[slug].astro 生成;
首页、分类、标签、归档、设置页等是常规列表页。

直接把构建输出抓下来,按 URL 形态分组统计每页耗时:

页面形态	数量	平均耗时
`/published/年份/slug/` 跳转页	424	1.3ms
`/posts/年份/月/slug/` 别名跳转页	209	1.7ms
`/posts/slug.html` 别名跳转页	209	1.2ms
`/posts/slug/` 真实文章页	212	~70ms
`/settings`、`/tags/*`、首页等列表页	~90	~70ms

结论很清楚:所有别名/跳转页都是 1~3ms,慢的全是真实页面。212 篇文章页 × 70ms ≈ 15s,再加列表页,基本吃掉了 “generating static routes” 阶段的 27 秒。之前直觉上”aliases 慢”其实是看走眼了——日志里 /posts/slug/ 长得和别名很像,但它们是正经文章页。

深挖:70ms 到底花在哪

给 node_modules/astro/dist/core/build/generate.js 里的 renderPath 临时加了几段计时,把一次页面生成拆成”渲染”和”写文件”两步:

DEBUG [/posts/test-astro-encrypted]  total=74.9ms  render=72.9  fs=1.5
DEBUG [/posts/scrollbar-butterfly-style] total=52.1ms render=49.8 fs=1.9
DEBUG [/posts/windows-setting-priority-ipv4]  total=50.2ms  render=48.6  fs=1.3

写文件只有 ~1.5ms,render 占了 95%。再在 routing/handler.js 里打一行日志,看到更关键的信息:

DEBUG2 [/posts/[slug]] handleTotal=74.6 pre=0.0 render=74.6

渲染的 routeData 是 /posts/[slug](type=page),也就是说每个文章页都是完整走了一遍 Astro 模板渲染,这不是 bug,是页面本身的成本。

为什么一页要 70ms:侧边栏比正文还重

量了一下输出文件构成,一篇正文只有 9.8KB 的小文章,整页 HTML 却有 270KB:

<article> 正文:9.8KB;
头部到正文之前(侧边栏 + 顶栏 + 脚本):~195KB;
正文之后(底部栏等):~60KB。

侧边栏 Sidebar.astro 里,220 篇文章在”文件树/搜索/时间线”三个视图各出现一次,加上分类、标签、终端数据,每页要输出 1000+ 个链接。这些数据虽然已经做了构建期缓存,但模板每页都要重新执行一遍。

而在这些模板执行里,有一个非常可疑的调用:侧边栏每页要调 fmtDate 约 660 次。看看它的实现:

function partsInTZ(date: Date) {
  const fmt = new Intl.DateTimeFormat('zh-CN', { timeZone: TZ, /* ... */ }); // ← 每次调用都 new!
  const get = (type) => fmt.formatToParts(date).find(...)?.value ?? '00';
  ...
}

每次格式化都新建一个 Intl.DateTimeFormat 实例。实测:

每次新建:43.6µs/次(Windows + Node 24)
复用同一个实例:3.1µs/次

660 次 × 43.6µs ≈ 29ms/页,而文章页总共才 70ms——这个毫不起眼的函数占了大头。列表页更夸张,一页要格式化几十篇文章的日期,所以它们也从 ~70ms 掉到个位数。

修复:把 formatter 提升到模块级

const TZ = 'Asia/Shanghai';

const tzDateFmt = new Intl.DateTimeFormat('zh-CN', {
  timeZone: TZ,
  year: 'numeric',
  month: '2-digit',
  day: '2-digit',
  hour: '2-digit',
  minute: '2-digit',
  second: '2-digit',
  hourCycle: 'h23',
});

function partsInTZ(date: Date) {
  const get = (type: string) =>
    tzDateFmt.formatToParts(date).find((p) => p.type === type)?.value ?? '00';
  // ...
}

formatToParts 是无状态的纯函数(对同一个实例并发调用也安全),改完后输出完全一致——文章日期、时区、跳转页 location 逐项对比过,没有任何变化。

结果

指标	优化前	优化后
文章页平均耗时	~70ms	23ms
列表页平均耗时	~70ms	7.6ms
跳转页平均耗时	~1.5ms	~1.5ms(不变)
整站构建	31.0s	13.4s

2.3 倍提速,只改了一个文件的一小段。构建日志里 842 个跳转页依旧飞快,/published/ 依旧 1ms,但全站生成时间直接腰斩。

顺带验证:`build.concurrency` 没用

Astro 7 支持 build: { concurrency: N } 并行生成页面,顺手测了一下(6 并发、32 核机器):

单页平均耗时从 70ms 涨到 ~380ms(并发互相挤占);
总耗时几乎没变,甚至略慢(28.6s vs 27.7s)。

原因:页面渲染是单线程 CPU 密集任务,Node 一个进程内并发只是时间片切换,不产生并行收益。所以这个方向可以直接排除。

经验总结

先量化,再优化。凭日志印象判断”哪个页面慢”很容易被误导——我把耗时按 URL 形态分组统计后,才发现慢的跟 aliases 没关系;
别小看”每次调用都 new”的模式。Intl.DateTimeFormat、正则字面量以外的 new RegExp、Date 解析……在循环/模板里被高频调用时,对象构造开销会被放大成秒级差距;
侧边栏等共享 UI 是隐形成本大头。每页重渲染 ~~195KB 的侧边栏,数据层缓存救不了模板层的重复执行。如果要再进一步,可以把侧边栏 HTML 在构建期预渲染一次、跨页复用,预计还能再省 5~~8s,但需要和模板保持同步,属于”按需再做”的优化;
排查时给 node_modules 里打日志是快准狠的办法,记得改完还原(这次全程只改了 generate.js 和 handler.js,最后 git checkout 恢复)。

测试Astro加密文章

2026-08-06T02:00:00.000Z

🔒 内容已加密，输入密码查看

全站滚动条改版:Butterfly 风格 5px 主题色细条

2026-08-05T16:34:00.000Z

前阵子把文章按状态重组成 content/published|draft|trash|hidden 后,顺手整理主题(ark)的滚动条。这篇记录改版思路与最终方案。

问题:滚动条要么没有,要么很丑

改版前全站的滚动条状态其实很乱:

文章页正文完全没有滚动条。正文的滚动容器 .editor-surface 被设了 scrollbar-width: none,滚轮能用,但右边光秃秃的,完全没有视觉反馈;
其他地方都是系统原生滚动条。侧边栏、代码块、终端、弹窗各自为政,Windows 上 Chrome 的原生灰条既粗又丑,和暗色主题格格不入;
tabline 的横向滚动条只有 3px、16% 透明度,几乎看不见。

需求很朴素:全站滚动条统一,藏进页面里的细条,横向纵向都要管。

参考:Butterfly 主题的方案

Butterfly是 Hexo 的知名主题,它的滚动条观感一直是”轻、贴、不抢眼”。扒了它的 CSS,核心就三条:

::-webkit-scrollbar {
  width: 5px;
  height: 5px;
}
::-webkit-scrollbar-thumb {
  background: var(--scrollbar-color); /* 主题色 */
}
::-webkit-scrollbar-track {
  background-color: transparent; /* 轨道全透明,滚动条"沉"进页面 */
}
/* Firefox 用标准的 scrollbar 属性 */
* {
  scrollbar-width: thin;
  scrollbar-color: var(--scrollbar-color) transparent;
}

几个要点:

5px 宽高都有,横向滚动条(代码块、tabline)同样适用;
thumb 用主题色实心填充、不加圆角不加阴影,极简;
轨道透明,不占视觉面积,滚动条像是画在页面上的细线;
暗色模式下 Butterfly 把 --scrollbar-color 换成中性灰(它用 #525252),不用亮蓝,避免刺眼。

实现

1. 颜色变量

在 assets/css/ark-vars.css 的亮/暗两套变量里各加一个 --scrollbar-color:

:root {
  --scrollbar-color: #0969da; /* 亮色:主题蓝 */
}
:root[data-mode="dark"] {
  --scrollbar-color: #3d4450; /* 暗色:中性灰 */
}

亮色直接用主题蓝 --accent 同款 #0969da,和站内强调色一致;暗色不用亮蓝而是低调的 #3d4450,参考 Butterfly 的做法。

2. 全局规则

同样放在 ark-vars.css 末尾(变量和基础样式的落点),和上面 Butterfly 的方案一致:5px 宽高、主题色 thumb、透明轨道,外加 @-moz-document url-prefix() 给 Firefox 套 scrollbar-width: thin + scrollbar-color。

写在全局(而不是某个容器上),所有滚动容器自动生效:文章正文、侧边栏、代码块、终端、tabline、弹窗列表,横向纵向全覆盖,不用逐个容器去配。

3. 删掉局部覆盖

之前的局部样式全部移除,避免和全局规则打架:

.editor-surface(文章正文):删掉 scrollbar-width: none 和它的 ::-webkit-scrollbar 隐藏规则 —— 这是”文章页没有滚动条”的元凶,删掉后全局规则接管,5px 主题色细条立刻出现;
.editor-tabline(标签栏):删掉 3px 灰条那套自定义滚动条,横向滚动交给全局的 5px 高度规则。

保留的例外有两个:

.article-toc(文章目录浮层):有意隐藏滚动条,滚动靠滚轮/触控板,视觉更干净;
.editor-tabline(标签栏)的横向滚动条:像 VS Code、Sublime 这类软件一样,标签太多时滚动条直接隐藏,靠滚轮左右滚动(见下),5px 全局横条只留给代码块等横向溢出的内容区。

标签栏滚轮横滚

隐藏滚动条后得保证标签能滚动。在 assets/js/ark-editor.js 里给 .editor-tabline 挂了一个 wheel 监听:

editorTabline.addEventListener("wheel", function (event) {
  if (editorTabline.scrollWidth <= editorTabline.clientWidth) return; // 没溢出不拦截
  if (Math.abs(event.deltaY) <= Math.abs(event.deltaX)) return;      // 横向滚轮事件放行
  event.preventDefault();
  editorTabline.scrollLeft += event.deltaY + event.deltaX;
}, { passive: false });

只有标签真正溢出时才拦截滚轮,否则不影响页面竖向滚动;
触控板/鼠标横滚(deltaX)原样放行;
鼠标滚轮(deltaY)转成 scrollLeft,实现”滚轮左右滚标签”的软件惯例。

效果

文章页右侧出现 5px 主题蓝竖条,滚动位置一目了然;
代码块横向溢出时是 5px 主题色横条;
标签栏横向滚动条隐藏,溢出时滚轮可直接左右滚动;
暗色模式下是中性灰,不刺眼;
轨道透明,滚动条”浮”在页面内容上,正是 Butterfly 那种藏在网页里的感觉。

资源管理器引导线与缩进布局:对齐、等比网格与紧凑/宽松开关

2026-08-05T15:30:00.000Z

侧边栏资源管理器(文件树)的引导线一直有几处视觉问题:层级一变深引导线就断、线出现在目录行本身上、缩进层级忽宽忽窄。这篇记录这几轮的排查、修复思路与最终方案,以及新加的”紧凑/宽松资源管理器布局”设置开关。

问题清单

从用户视角看,引导线的问题可以归纳为五类:

引导线被子目录中断。原本每行只画自己那一层深度的竖线,子目录一展开,父层级的竖线就在子目录行处断掉,树形连接不连续。
引导线出现在目录行上。云端(带 🔒 的工作区根行)的下拉符号正下方多了一条线:没对准 chevron 的尖端,还压在了锁图标所在的行容器上;分类、记录等目录行的 chevron 前面也各有一条多余的线。
文件行缩进不统一。记录里的文件行缩进要么太少(和父目录图标挤在一起),要么改完又太多(比同层文件夹多出一大步)。
层级缩进尺寸不一致。云端→分类这一步是”宽松”(23px),分类→子目录→文件却是”紧凑”(12px),同一个树里两套步距。
引导线间距与左边框距离不一致。线间距统一了,但最左侧边框到第一条引导线的距离和线间距对不上。

修复思路

1. 祖先层级线:一行画 N-1 条线

把引导线从”每行只画自己层级的线”改成”每行画全部祖先层级的线”:深度为 N 的行显示第 1~N-1 层的竖线,自己层级不画。这样:

子目录展开后,父级竖线从分类一路贯通到文件,不再中断;
目录行(包括云端根行)自身不再有任何引导线,🔒 容器干净了;
每条线都从上一级目录的 chevron 方向垂直延伸下来。

实现上利用 CSS 自定义属性 + 多层 linear-gradient 背景拼出多条竖线,深度 1~5 分别声明 --tree-guide,行内 ::after 统一铺满整行绘制。

2. 等比网格:级别尺寸以引导线为准

最终定下的几何规则只有一条:整个树是一个以 step 为单位的等比网格:

引导线位置:L_N = N × step(第 N 条线距行左边缘 N×step);
行缩进:padding_N = N × step − 8(8px 是 chevron 盒子中心到行左边缘的固定偏移);
于是每层目录的 ▾ 尖端恰好落在自己层级的引导线上,且左边框→第一条线 = 相邻线间距 = 每级缩进。

全部由 CSS 变量 --tree-step 驱动,不用硬编码像素:

.file-tree {
  --tree-step: 16px; /* 宽松默认 */
}

:root[data-tree-indent-layout="compact"] .file-tree {
  --tree-step: 12px; /* 紧凑覆盖 */
}

.file-tree summary,
.file-tree .file-item {
  padding: 0 8px 0 calc((var(--tree-depth, 0) * var(--tree-step, 16px)) - 8px);
}

引导线位置用加法拼出来(calc(var(--tree-step) + var(--tree-step) + …)),避免在 calc 里做乘法,兼容性更稳。

3. 紧凑 / 宽松布局开关

设置页新增”紧凑资源管理器布局”复选框(compactTreeIndent,沿用 data-workbench-setting 机制):

模式	step	行缩进(chevron 尖端)	引导线
宽松(默认)	16px	8 / 24 / 40 / 56	16 / 32 / 48 / 64
紧凑	12px	4 / 16 / 28 / 40	12 / 24 / 36 / 48

默认宽松;勾选后立即切换紧凑并写入 localStorage(ark-workbench-settings);
applyWorkbenchSettings() 把模式写到 <html data-tree-indent-layout="compact|loose">,CSS 按属性覆盖 --tree-step;
云端/本地等工作区根行不再特殊处理,同样落在网格上,层级步距全程一致。

验证

用无头 Chrome 逐项量了实际渲染值,两种模式下均满足:

引导线间距:紧凑 12/12/12、宽松 16/16/16;
每级缩进:紧凑 4→16→28→40、宽松 8→24→40→56;
每层 chevron 尖端与对应引导线像素级重合;
设置开关勾选后即时生效并持久化。

涉及文件

assets/css/ark-sidebar.css — 引导线、缩进网格、--tree-step 变量
assets/js/ark-core.js — 设置默认值与 data-tree-indent-layout 应用
assets/js/ark-sync.js — 开关读写与重置
layouts/_default/settings.html + i18n/zh.yml / i18n/en.yml — 设置项 UI 与文案

侧边栏云端文件树改造记录:中文目录、分类树与 SPA 导航

2026-08-05T13:30:00.000Z

WordPress 迁移到 Hugo 后,顺手把主题(ark)的侧边栏云端文件树整体重构了一遍。这篇记录改造的思路、结构与踩坑,方便日后维护。

需求来源

原本的侧边栏云端树只有”按分类分组的文章 + 散落的页面链接”,分类和文件都是英文 slug,页面路径直接裸暴露(如 pages/friends/index.md),既不美观也不符合中文站点的使用习惯。改造目标是:

目录全部中文化,文件树里显示文章标题而不是英文 slug
结构分层:页面 / 归档 / 分类 / 标签 / 管理五个一级目录
分类、标签做成文件树,可配置显示哪些分类
点击目录时:展开文件树 + 打开对应列表页,且不刷新浏览器(SPA)

最终结构

☁ 云端
├─ 📁 页面
│  ├─ Arkylin的小屋        ← 主页(显示网站名,点击回首页)
│  ├─ 示例页面.md(紫色)     ← pages 目录的页面,标题显示
│  └─ 友情链接.md ...
├─ 📁 归档                ← 链接到 /archives/
│  ├─ 📁 2019 (35)        ← 按年份分组,带文章计数
│  ├─ 📁 2020 (72)
│  └─ ...
├─ 📁 分类                ← 链接到 /categories/
│  ├─ 📁 学习(带链接)       ← 点击跳转 /categories/学习/
│  │  └─ 文章标题.md
│  └─ ...
├─ 📁 标签                ← 链接到 /tags/
│  ├─ Aliyun (1)
│  └─ ...(70 个,默认折叠)
└─ 📁 管理
   ├─ admin.md / settings.md / account.md

关键实现

1. 分类按配置显示

hugo.toml 里通过 [params.sidebar] 控制:

[params.sidebar]
  # 允许显示的分类文件夹(留空 = 全部显示)
  show_categories = ['学习', '开发', '日记', '代码', 'VPS测评', '记录', '测评', '未分类']

模板里用 in $showCats . 过滤分类文件夹;一篇文章有多个分类时,按分类分组(Go 模板 dict 累加),自然在多个分类文件夹里同时出现。

2. 点击目录:展开树 + SPA 打开页面

文件树的文件夹 label 用 <span data-tree-link="/categories/">,点击时由 JS 处理:

document.addEventListener('click', function (e) {
  var el = e.target.closest('[data-tree-link]');
  if (!el) return;
  var href = el.getAttribute('data-tree-link');
  if (!href) return;
  var d = el.closest('details');
  if (d) d.open = true;                 // 展开文件树
  if (typeof navigateTo === 'function') {
    navigateTo(href);                   // 主题自带 SPA 导航,不刷新
  } else {
    window.location.href = href;
  }
});

关键点:不要直接 window.location.href = href——主题(ark)有完整的 SPA 路由(navigateTo,fetch 页面 + DOMParser 替换内容),直接赋值会整页刷新,丢失编辑器 tab、树高亮等状态。点击后新页面树默认展开(<details open>)。

3. 层级引导线

云端树原本没有层级竖线,本地虚拟树有,视觉不一致。用伪元素 + 重复渐变实现连续列线(每行按深度画所有祖先列,避免”线被二级目录截断”):

.file-tree .tree-depth-1 > summary::after,
.file-tree .file-item.tree-depth-2::after,
/* ...depth 1-5 */
{
  content: "";
  position: absolute;
  top: 0;
  bottom: 0;
  left: 0;
  width: calc(13px + ((var(--tree-depth) - 1) * 12px) + 12px);
  background: repeating-linear-gradient(
    to right,
    transparent 0 12px,
    color-mix(in srgb, var(--line) 68%, transparent) 12px 13px
  );
}

4. 目录行高统一(踩坑)

文件夹的 summary 是 3 列网格 grid-template-columns: 16px 18px minmax(0, 1fr)。给”年份文件夹”加文章计数后变成 4 个元素,第 4 个被挤到下一行,行高直接翻倍(22px → 44px),看起来”有的目录大有的小”:

.file-tree .tree-folder.is-year > summary {
  grid-template-columns: 16px 18px minmax(0, 1fr) auto;
}

另外,文件夹 label 用 <a> 和 <span> 渲染观感不同(链接有默认交互样式),统一用 <span> + JS 跳转,目录大小/颜色才完全一致。分类文件夹原有的蓝色图标也一并改回灰色,与标签/归档文件夹统一。

遗留

本地虚拟树(浏览器本地文件)和云端树结构不同,云端已中文化,本地保持原样
extra_dirs 配置项已废弃(归档固定为一级目录),如需在页面文件夹下追加自定义目录可恢复该逻辑

WordPress 迁移 Hugo 全记录:Plan、工具、代码与流程

2026-08-05T12:10:00.000Z

2026 年 8 月,我把自己的 WordPress 博客完整迁移到了 Hugo。这篇文章记录整个迁移的计划、工具、核心代码和流程,给以后做同类迁移留个参考。

背景与数据盘点

旧站是 1Panel 面板部署的 Docker WordPress,备份包里有:

wordpress.sql(2.7MB,MySQL 全量导出,内容都在这里)
wp-content/uploads/(370 个媒体文件)

先摸清家底(用 Python 解析 SQL 统计):

类型	数量
文章 post(已发布)	211
文章 post(草稿)	12
文章 post(回收站)	9
文章 post(私密)	2
页面 page(已发布 / 草稿)	6 / 1
附件 attachment	291
修订版本 revision	87(忽略)
分类 / 标签	9 / 69

内容形态:196 篇经典编辑器 HTML + 4 篇 Gutenberg 块,还有少量 Handsome 主题短代码([collapse]、[post cid=]、[hplayer])。

方案设计(关键决策)

状态映射:WP 的 post_status 还原为 5 种语义,写入 front matter 的 status 字段: publish→published、draft→draft、trash→trash、private→hidden、publish+密码→encrypted(本数据无)。非 published 状态全部加 draft: true——Hugo 原生的”导入但不渲染”,hugo server -D 可预览。
目录结构:文章按发布时间存 content/posts/YYYY/MM/<slug>/(人好找好改),每个 bundle 内 index.md + images/;页面单独放 content/pages/<slug>/。这是 Hugo 官方推荐的 Page Bundle 模式。
URL 与旧链接兼容:Hugo 目录结构自动生成规范链接 /posts/YYYY/MM/<slug>/,同时每篇 front matter 写两个 alias:
```
aliases:
  - /posts/<slug>.html    # 旧 WordPress 链接
  - /posts/<slug>         # 短链接
```
Hugo 自动为 alias 生成 301 重定向页,新旧站同域名 www.ioioi.cn,老地址全部不 404。
图片处理:文章引用的图片复制进文章 bundle 的 images/ 子目录,引用改为相对路径;没有被任何文章引用的孤儿图片,保留 YYYY/MM 年月结构放到 static/images/。全程不保留 wp-content/uploads 这种 WordPress 痕迹。

工具

工具	版本	用途
Python	3.13	解析 SQL、转换、生成
markdownify	1.2.3	HTML → Markdown(代码块/表格/图片都处理得很好)
Hugo	v0.162.1 extended	构建验证

核心代码

1. SQL 解析器(兼容 mysqldump 转义)

def parse_values(block):
    """把一个 SQL 行拆成字段列表,处理 '' 和 \\ 转义"""
    vals, cur = [], []
    i, n = 0, len(block)
    def flush():
        nonlocal cur
        vals.append(''.join(cur)); cur = []
    while i < n:
        c = block[i]
        if c == "'":
            j = i + 1
            buf = []
            while j < n:
                if block[j] == "\\" and j + 1 < n:
                    buf.append('\\' + block[j+1]); j += 2
                elif block[j:j+2] == "''":
                    buf.append("'"); j += 2
                elif block[j] == "'":
                    j += 1; break
                else:
                    buf.append(block[j]); j += 1
            cur.append(''.join(buf)); i = j
        elif c == ',':
            flush(); i += 1
        else:
            cur.append(c); i += 1
    if cur:
        flush()
    return vals

行切分的关键是引号感知:内容里可能包含 ),( 或转义引号,必须用状态机在引号外才切行:

def extract_insert(table):
    """解析该表的所有 INSERT 区块, mysqldump 可能拆成多条 INSERT 语句"""
    all_rows = []
    for m in re.finditer(r'INSERT INTO `' + table + r'` VALUES(.*?);\n', sql, re.S):
        block = m.group(1)
        rows, start, i, in_str = [], 0, 0, False
        while i < len(block):
            if block[i] == "\\":          # 转义字符,跳过
                i += 2; continue
            if block[i] == "'":
                if in_str and block[i+1:i+2] == "'":   # '' 转义
                    i += 2; continue
                in_str = not in_str
            elif not in_str and block[i:i+3] == '),(':
                rows.append(block[start:i+1]); start = i + 2; i += 3; continue
            i += 1
        ...
    return all_rows

2. HTML → Markdown + 图片归集

from markdownify import markdownify as md

# 清理 Gutenberg 注释
html = re.sub(r'<!--\s*/?wp:[^>]*?-->', '', html)

# 提取文章引用的所有上传文件
ABS_RE = re.compile(r'https?://(?:www\.)?ioioi\.cn/wp-content/uploads/([^\s"\'<>)]+)')
for m in ABS_RE.finditer(html):
    rel = unquote(m.group(1))
    # 找到磁盘上的原文件,复制到 bundle/images/,引用改为相对路径
    target = safe_name(os.path.basename(rel))
    shutil.copy2(src, os.path.join(bundle, 'images', target))
    ref_map[orig] = 'images/' + target

markdown = md(html, heading_style='ATX', bullets='-')
for orig, target in ref_map.items():
    markdown = markdown.replace(orig, target)

3. front matter 生成

fm.append('---')
fm.append(fm_value('title', it['title'] or f'未命名-{pid}'))
fm.append(fm_value('date', fmt_dt(date_dt)))          # YYYY-MM-DDTHH:MM:SS+08:00
fm.append(fm_value('status', it['status']))
fm.append(fm_value('draft', it['status'] != 'published'))
fm.append(fm_value('aliases', [alias_base + '.html', alias_base]))
fm.append('---')

流程(5 阶段)

阶段1 解析   wordpress.sql → 结构化数据(文章/页面/分类/标签/图片引用)
阶段2 转换   HTML→Markdown, 清 Gutenberg 注释, 解析 <img> 清单
阶段3 资源   文章引用图片 → bundle images/; 孤儿 → static/images/YYYY/MM/
阶段4 生成   content/posts/YYYY/MM/<slug>/index.md + content/pages/<slug>/index.md
阶段5 验证   hugo build + 数量核对 + 渲染抽查 + 迁移报告

踩过的坑

.html 附件不能放 content 里:Hugo 把 bundle 内任何 .html/.md 文件当页面源,触发 security.allowContent 拦截。非图片附件(html/zip/mp4)统一放 static/media/YYYY/MM/,用绝对路径 /media/... 引用。
PowerShell 跑 python -c 传中文/引号脚本容易炸,改成写 .py 文件执行。
SQL 内容里的 \r\n 是转义序列不是字面量,sql_unescape() 要按 \\→\、\n→换行的顺序处理,否则代码块里出现真 \n 文本。
控制台 GBK 乱码 ≠ 文件乱码,验证文件内容用 -Encoding UTF8 读取。
mysqldump 会按表拆成多条 INSERT 语句:wp_posts 数据被拆成两个 INSERT INTO 区块,如果只 re.search 第一个区块,第二个区块里的 2025 年文章会全部丢失。解析器必须用 re.finditer 扫描所有 INSERT INTO ... VALUES 区块再合并。这是本次迁移最大的坑,第一版差点丢掉 11 篇文章(2025 年的 Win11 核显、SQL 连接规范、绿联 NAS、Windows IPv4 优先级等)。

最终结果

234 篇文章 + 7 个页面全部导入(逐篇核对无遗漏),hugo build 零错误
211 篇已发布正常渲染,草稿/回收站/私密 23 篇以 draft: true 保留
511 个旧链接重定向,123 篇带图文章图片全部本地化,无缺失
迁移报告自动生成(缺失图片、短代码清单、孤儿图片清单)

遗留:[collapse](8 篇)、[post cid=](9 处)、[hplayer](1 篇)等 Handsome 主题短代码目前以纯文本保留,后续可改成 Hugo shortcode(<details> 折叠、文章互链等)。

数据文件

迁移脚本和中间数据留在本地 C:\Users\i\AppData\Local\Temp\opencode\(migrate.py / generate.py / wp_items.json),报告在 migration-report.md。

Windows 设置优先 IPv4

2025-06-26T07:38:06.000Z

(base) PS C:\Users\i> netsh interface ipv6 show prefixpolicies 查询活动状态… 优先顺序标签前缀

50 0 ::1/128 40 1 ::/0 35 4 ::ffff:0:0/96 30 2 2002::/16 5 5 2001::/32 3 13 fc00::/7 1 11 fec0::/10 1 12 3ffe::/16 1 3 ::/96 (base) PS C:\Users\i> netsh interface ipv6 set prefixpolicy ::ffff:0:0/96 100 4 请求的操作需要提升(作为管理员运行)。 (base) PS C:\Users\i> netsh interface ipv6 show prefixpolicies 查询活动状态… 优先顺序标签前缀

100 4 ::ffff:0:0/96 50 0 ::1/128 40 1 ::/0 30 2 2002::/16 5 5 2001::/32 3 13 fc00::/7 1 11 fec0::/10 1 12 3ffe::/16 1 3 ::/96

解决Netbird和Tailscale不能在Linux共存Ping不通的问题

2025-05-01T12:26:42.000Z

braginini commented on Nov 7, 2022

braginini

on Nov 7, 2022

Contributor

You can use --netfilter-mode=off when running Tailscale. This will prevent aggressive packets take over by Tailscale daemon.

It doesn’t exclude the possibility of conflict but chances are low.

https://github.com/netbirdio/netbird/issues/544 --netfilter-mode (Linux only) Advanced feature for controlling the degree of automatic firewall configuration. Values are either “off”, “nodivert”, or “on”. Defaults to “on”, except for Synology which defaults to “off”. Setting this flag to “off” disables all management of netfilter. Setting to “nodivert” creates and manages Tailscale sub-chains, but leaves the calling of those chains up to the administrator. Setting to “on” means using full management of Tailscale’s rules. Note that if you set --netfilter-mode to “off” or “nodivert”, it is your responsibility to configure the firewall securely for Tailscale traffic. We recommend using the rules installed by --netfilter-mode=on as a starting point. https://tailscale.com/kb/1241/tailscale-up

绿联NAS虚拟机MacVTap网络虚拟机和宿主机无法相互访问

2025-03-22T09:47:17.000Z

因为他们之间没有通信的渠道，所以无法通信，添加一个NAT网卡就行了。

参考：A.19.4. Guest Can Reach Outside Network，但在使用 macvtap 界面时可能会重新访问主机

绿联docker无法ping通主机

2025-03-13T13:39:30.000Z

关闭“启用多网关就行了”

miniconda安装电脑上装了Python环境的版本记录会安装到Python版本目录下

2025-03-11T08:02:16.000Z

miniconda安装电脑上装了Python环境的版本记录会安装到Python版本目录下 miniconda版本3.12 Python版本3.13，然后使用miniconda 创建3.13的环境会安装到Python里面去 (ultralytics) PS C:\Users\i> pip3 install torch torchvision torchaudio —index-url https://download.pytorch.org/whl/cu126 Defaulting to user installation because normal site-packages is not writeable Looking in indexes: https://download.pytorch.org/whl/cu126 Collecting torch Using cached https://download.pytorch.org/whl/cu126/torch-2.6.0%2Bcu126-cp313-cp313-win_amd64.whl.metadata (28 kB) Collecting torchvision Using cached https://download.pytorch.org/whl/cu126/torchvision-0.21.0%2Bcu126-cp313-cp313-win_amd64.whl.metadata (6.3 kB) Collecting torchaudio Using cached https://download.pytorch.org/whl/cu126/torchaudio-2.6.0%2Bcu126-cp313-cp313-win_amd64.whl.metadata (6.8 kB) Collecting filelock (from torch) Using cached https://download.pytorch.org/whl/filelock-3.13.1-py3-none-any.whl.metadata (2.8 kB) Collecting typing-extensions>=4.10.0 (from torch) Using cached https://download.pytorch.org/whl/typing_extensions-4.12.2-py3-none-any.whl.metadata (3.0 kB) Collecting networkx (from torch) Using cached https://download.pytorch.org/whl/networkx-3.3-py3-none-any.whl.metadata (5.1 kB) Collecting jinja2 (from torch) Using cached https://download.pytorch.org/whl/Jinja2-3.1.4-py3-none-any.whl.metadata (2.6 kB) Collecting fsspec (from torch) Using cached https://download.pytorch.org/whl/fsspec-2024.6.1-py3-none-any.whl.metadata (11 kB) Collecting setuptools (from torch) Using cached https://download.pytorch.org/whl/setuptools-70.2.0-py3-none-any.whl.metadata (5.8 kB) Collecting sympy==1.13.1 (from torch) Using cached https://download.pytorch.org/whl/sympy-1.13.1-py3-none-any.whl (6.2 MB) Collecting mpmath<1.4,>=1.1.0 (from sympy==1.13.1->torch) Using cached https://download.pytorch.org/whl/mpmath-1.3.0-py3-none-any.whl (536 kB) Collecting numpy (from torchvision) Using cached https://download.pytorch.org/whl/numpy-2.1.2-cp313-cp313-win_amd64.whl.metadata (59 kB) Collecting pillow!=8.3.*,>=5.3.0 (from torchvision) Using cached https://download.pytorch.org/whl/pillow-11.0.0-cp313-cp313-win_amd64.whl.metadata (9.3 kB) Collecting MarkupSafe>=2.0 (from jinja2->torch) Using cached https://download.pytorch.org/whl/MarkupSafe-2.1.5.tar.gz (19 kB) Installing build dependencies … done Getting requirements to build wheel … done Preparing metadata (pyproject.toml) … done Downloading https://download.pytorch.org/whl/cu126/torch-2.6.0%2Bcu126-cp313-cp313-win_amd64.whl (2496.1 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.5/2.5 GB 10.2 MB/s eta 0:00:00 Downloading https://download.pytorch.org/whl/cu126/torchvision-0.21.0%2Bcu126-cp313-cp313-win_amd64.whl (6.1 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 6.1/6.1 MB 10.3 MB/s eta 0:00:00 Downloading https://download.pytorch.org/whl/cu126/torchaudio-2.6.0%2Bcu126-cp313-cp313-win_amd64.whl (4.2 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 4.2/4.2 MB 10.5 MB/s eta 0:00:00 Downloading https://download.pytorch.org/whl/pillow-11.0.0-cp313-cp313-win_amd64.whl (2.6 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.6/2.6 MB 8.5 MB/s eta 0:00:00 Downloading https://download.pytorch.org/whl/typing_extensions-4.12.2-py3-none-any.whl (37 kB) Downloading https://download.pytorch.org/whl/filelock-3.13.1-py3-none-any.whl (11 kB) Downloading https://download.pytorch.org/whl/fsspec-2024.6.1-py3-none-any.whl (177 kB) Downloading https://download.pytorch.org/whl/Jinja2-3.1.4-py3-none-any.whl (133 kB) Downloading https://download.pytorch.org/whl/networkx-3.3-py3-none-any.whl (1.7 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.7/1.7 MB 10.1 MB/s eta 0:00:00 Downloading https://download.pytorch.org/whl/numpy-2.1.2-cp313-cp313-win_amd64.whl (12.6 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 12.6/12.6 MB 11.2 MB/s eta 0:00:00 Using cached https://download.pytorch.org/whl/setuptools-70.2.0-py3-none-any.whl (930 kB) Building wheels for collected packages: MarkupSafe Building wheel for MarkupSafe (pyproject.toml) … done Created wheel for MarkupSafe: filename=MarkupSafe-2.1.5-cp313-cp313-win_amd64.whl size=17236 sha256=1920967b46a08327667bfa28ddea3492b28c1a3051fda774f6ff64374ba13139 Stored in directory: c:\users\i\appdata\local\pip\cache\wheels\84\b6\28\95b8e298901ee19b488797095efb5fbed28637ed83215b13b1 Successfully built MarkupSafe Installing collected packages: mpmath, typing-extensions, sympy, setuptools, pillow, numpy, networkx, MarkupSafe, fsspec, filelock, jinja2, torch, torchvision, torchaudio WARNING: The script isympy.exe is installed in ‘C:\Users\i\AppData\Roaming\Python\Python313\Scripts’ which is not on PATH. Consider adding this directory to PATH or, if you prefer to suppress this warning, use —no-warn-script-location. WARNING: The scripts f2py.exe and numpy-config.exe are installed in ‘C:\Users\i\AppData\Roaming\Python\Python313\Scripts’ which is not on PATH. Consider adding this directory to PATH or, if you prefer to suppress this warning, use —no-warn-script-location. WARNING: The scripts torchfrtrace.exe and torchrun.exe are installed in ‘C:\Users\i\AppData\Roaming\Python\Python313\Scripts’ which is not on PATH. Consider adding this directory to PATH or, if you prefer to suppress this warning, use —no-warn-script-location. Successfully installed MarkupSafe-2.1.5 filelock-3.13.1 fsspec-2024.6.1 jinja2-3.1.4 mpmath-1.3.0 networkx-3.3 numpy-2.1.2 pillow-11.0.0 setuptools-70.2.0 sympy-1.13.1 torch-2.6.0+cu126 torchaudio-2.6.0+cu126 torchvision-0.21.0+cu126 typing-extensions-4.12.2 (ultralytics) PS C:\Users\i> pip install ultralytics Defaulting to user installation because normal site-packages is not writeable Collecting ultralytics Using cached ultralytics-8.3.87-py3-none-any.whl.metadata (35 kB) Collecting numpy<=2.1.1,>=1.23.0 (from ultralytics) Downloading numpy-2.1.1-cp313-cp313-win_amd64.whl.metadata (59 kB) Collecting matplotlib>=3.3.0 (from ultralytics) Downloading matplotlib-3.10.1-cp313-cp313-win_amd64.whl.metadata (11 kB) Collecting opencv-python>=4.6.0 (from ultralytics) Using cached opencv_python-4.11.0.86-cp37-abi3-win_amd64.whl.metadata (20 kB) Requirement already satisfied: pillow>=7.1.2 in c:\users\i\appdata\roaming\python\python313\site-packages (from ultralytics) (11.0.0) Collecting pyyaml>=5.3.1 (from ultralytics) Downloading PyYAML-6.0.2-cp313-cp313-win_amd64.whl.metadata (2.1 kB) Collecting requests>=2.23.0 (from ultralytics) Using cached requests-2.32.3-py3-none-any.whl.metadata (4.6 kB) Collecting scipy>=1.4.1 (from ultralytics) Downloading scipy-1.15.2-cp313-cp313-win_amd64.whl.metadata (60 kB) Requirement already satisfied: torch>=1.8.0 in c:\users\i\appdata\roaming\python\python313\site-packages (from ultralytics) (2.6.0+cu126) Requirement already satisfied: torchvision>=0.9.0 in c:\users\i\appdata\roaming\python\python313\site-packages (from ultralytics) (0.21.0+cu126) Collecting tqdm>=4.64.0 (from ultralytics) Using cached tqdm-4.67.1-py3-none-any.whl.metadata (57 kB) Collecting psutil (from ultralytics) Using cached psutil-7.0.0-cp37-abi3-win_amd64.whl.metadata (23 kB) Collecting py-cpuinfo (from ultralytics) Using cached py_cpuinfo-9.0.0-py3-none-any.whl.metadata (794 bytes) Collecting pandas>=1.1.4 (from ultralytics) Downloading pandas-2.2.3-cp313-cp313-win_amd64.whl.metadata (19 kB) Collecting seaborn>=0.11.0 (from ultralytics) Using cached seaborn-0.13.2-py3-none-any.whl.metadata (5.4 kB) Collecting ultralytics-thop>=2.0.0 (from ultralytics) Using cached ultralytics_thop-2.0.14-py3-none-any.whl.metadata (9.4 kB) Collecting contourpy>=1.0.1 (from matplotlib>=3.3.0->ultralytics) Downloading contourpy-1.3.1-cp313-cp313-win_amd64.whl.metadata (5.4 kB) Collecting cycler>=0.10 (from matplotlib>=3.3.0->ultralytics) Using cached cycler-0.12.1-py3-none-any.whl.metadata (3.8 kB) Collecting fonttools>=4.22.0 (from matplotlib>=3.3.0->ultralytics) Downloading fonttools-4.56.0-cp313-cp313-win_amd64.whl.metadata (103 kB) Collecting kiwisolver>=1.3.1 (from matplotlib>=3.3.0->ultralytics) Downloading kiwisolver-1.4.8-cp313-cp313-win_amd64.whl.metadata (6.3 kB) Collecting packaging>=20.0 (from matplotlib>=3.3.0->ultralytics) Using cached packaging-24.2-py3-none-any.whl.metadata (3.2 kB) Collecting pyparsing>=2.3.1 (from matplotlib>=3.3.0->ultralytics) Downloading pyparsing-3.2.1-py3-none-any.whl.metadata (5.0 kB) Collecting python-dateutil>=2.7 (from matplotlib>=3.3.0->ultralytics) Using cached python_dateutil-2.9.0.post0-py2.py3-none-any.whl.metadata (8.4 kB) Collecting pytz>=2020.1 (from pandas>=1.1.4->ultralytics) Using cached pytz-2025.1-py2.py3-none-any.whl.metadata (22 kB) Collecting tzdata>=2022.7 (from pandas>=1.1.4->ultralytics) Using cached tzdata-2025.1-py2.py3-none-any.whl.metadata (1.4 kB) Collecting charset-normalizer<4,>=2 (from requests>=2.23.0->ultralytics) Downloading charset_normalizer-3.4.1-cp313-cp313-win_amd64.whl.metadata (36 kB) Collecting idna<4,>=2.5 (from requests>=2.23.0->ultralytics) Using cached idna-3.10-py3-none-any.whl.metadata (10 kB) Collecting urllib3<3,>=1.21.1 (from requests>=2.23.0->ultralytics) Downloading urllib3-2.3.0-py3-none-any.whl.metadata (6.5 kB) Collecting certifi>=2017.4.17 (from requests>=2.23.0->ultralytics) Using cached certifi-2025.1.31-py3-none-any.whl.metadata (2.5 kB) Requirement already satisfied: filelock in c:\users\i\appdata\roaming\python\python313\site-packages (from torch>=1.8.0->ultralytics) (3.13.1) Requirement already satisfied: typing-extensions>=4.10.0 in c:\users\i\appdata\roaming\python\python313\site-packages (from torch>=1.8.0->ultralytics) (4.12.2) Requirement already satisfied: networkx in c:\users\i\appdata\roaming\python\python313\site-packages (from torch>=1.8.0->ultralytics) (3.3) Requirement already satisfied: jinja2 in c:\users\i\appdata\roaming\python\python313\site-packages (from torch>=1.8.0->ultralytics) (3.1.4) Requirement already satisfied: fsspec in c:\users\i\appdata\roaming\python\python313\site-packages (from torch>=1.8.0->ultralytics) (2024.6.1) Requirement already satisfied: setuptools in c:\users\i\appdata\roaming\python\python313\site-packages (from torch>=1.8.0->ultralytics) (70.2.0) Requirement already satisfied: sympy==1.13.1 in c:\users\i\appdata\roaming\python\python313\site-packages (from torch>=1.8.0->ultralytics) (1.13.1) Requirement already satisfied: mpmath<1.4,>=1.1.0 in c:\users\i\appdata\roaming\python\python313\site-packages (from sympy==1.13.1->torch>=1.8.0->ultralytics) (1.3.0) Collecting colorama (from tqdm>=4.64.0->ultralytics) Using cached colorama-0.4.6-py2.py3-none-any.whl.metadata (17 kB) Collecting six>=1.5 (from python-dateutil>=2.7->matplotlib>=3.3.0->ultralytics) Using cached six-1.17.0-py2.py3-none-any.whl.metadata (1.7 kB) Requirement already satisfied: MarkupSafe>=2.0 in c:\users\i\appdata\roaming\python\python313\site-packages (from jinja2->torch>=1.8.0->ultralytics) (2.1.5) Using cached ultralytics-8.3.87-py3-none-any.whl (923 kB) Downloading matplotlib-3.10.1-cp313-cp313-win_amd64.whl (8.1 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 8.1/8.1 MB 10.5 MB/s eta 0:00:00 Downloading numpy-2.1.1-cp313-cp313-win_amd64.whl (12.6 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 12.6/12.6 MB 11.4 MB/s eta 0:00:00 Using cached opencv_python-4.11.0.86-cp37-abi3-win_amd64.whl (39.5 MB) Downloading pandas-2.2.3-cp313-cp313-win_amd64.whl (11.5 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 11.5/11.5 MB 11.3 MB/s eta 0:00:00 Downloading PyYAML-6.0.2-cp313-cp313-win_amd64.whl (156 kB) Using cached requests-2.32.3-py3-none-any.whl (64 kB) Downloading scipy-1.15.2-cp313-cp313-win_amd64.whl (41.0 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 41.0/41.0 MB 11.0 MB/s eta 0:00:00 Using cached seaborn-0.13.2-py3-none-any.whl (294 kB) Using cached tqdm-4.67.1-py3-none-any.whl (78 kB) Using cached ultralytics_thop-2.0.14-py3-none-any.whl (26 kB) Using cached psutil-7.0.0-cp37-abi3-win_amd64.whl (244 kB) Using cached py_cpuinfo-9.0.0-py3-none-any.whl (22 kB) Using cached certifi-2025.1.31-py3-none-any.whl (166 kB) Downloading charset_normalizer-3.4.1-cp313-cp313-win_amd64.whl (102 kB) Downloading contourpy-1.3.1-cp313-cp313-win_amd64.whl (220 kB) Using cached cycler-0.12.1-py3-none-any.whl (8.3 kB) Downloading fonttools-4.56.0-cp313-cp313-win_amd64.whl (2.2 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.2/2.2 MB 10.5 MB/s eta 0:00:00 Using cached idna-3.10-py3-none-any.whl (70 kB) Downloading kiwisolver-1.4.8-cp313-cp313-win_amd64.whl (71 kB) Using cached packaging-24.2-py3-none-any.whl (65 kB) Downloading pyparsing-3.2.1-py3-none-any.whl (107 kB) Using cached python_dateutil-2.9.0.post0-py2.py3-none-any.whl (229 kB) Using cached pytz-2025.1-py2.py3-none-any.whl (507 kB) Using cached tzdata-2025.1-py2.py3-none-any.whl (346 kB) Downloading urllib3-2.3.0-py3-none-any.whl (128 kB) Using cached colorama-0.4.6-py2.py3-none-any.whl (25 kB) Using cached six-1.17.0-py2.py3-none-any.whl (11 kB) Installing collected packages: pytz, py-cpuinfo, urllib3, tzdata, six, pyyaml, pyparsing, psutil, packaging, numpy, kiwisolver, idna, fonttools, cycler, colorama, charset-normalizer, certifi, tqdm, scipy, requests, python-dateutil, opencv-python, contourpy, ultralytics-thop, pandas, matplotlib, seaborn, ultralytics WARNING: The script cpuinfo.exe is installed in ‘C:\Users\i\AppData\Roaming\Python\Python313\Scripts’ which is not on PATH. Consider adding this directory to PATH or, if you prefer to suppress this warning, use —no-warn-script-location. Attempting uninstall: numpy Found existing installation: numpy 2.1.2 Uninstalling numpy-2.1.2: Successfully uninstalled numpy-2.1.2 WARNING: The scripts f2py.exe and numpy-config.exe are installed in ‘C:\Users\i\AppData\Roaming\Python\Python313\Scripts’ which is not on PATH. Consider adding this directory to PATH or, if you prefer to suppress this warning, use —no-warn-script-location. WARNING: The scripts fonttools.exe, pyftmerge.exe, pyftsubset.exe and ttx.exe are installed in ‘C:\Users\i\AppData\Roaming\Python\Python313\Scripts’ which is not on PATH. Consider adding this directory to PATH or, if you prefer to suppress this warning, use —no-warn-script-location. WARNING: The script normalizer.exe is installed in ‘C:\Users\i\AppData\Roaming\Python\Python313\Scripts’ which is not on PATH. Consider adding this directory to PATH or, if you prefer to suppress this warning, use —no-warn-script-location. WARNING: The script tqdm.exe is installed in ‘C:\Users\i\AppData\Roaming\Python\Python313\Scripts’ which is not on PATH. Consider adding this directory to PATH or, if you prefer to suppress this warning, use —no-warn-script-location. WARNING: The scripts ultralytics.exe and yolo.exe are installed in ‘C:\Users\i\AppData\Roaming\Python\Python313\Scripts’ which is not on PATH. Consider adding this directory to PATH or, if you prefer to suppress this warning, use —no-warn-script-location. Successfully installed certifi-2025.1.31 charset-normalizer-3.4.1 colorama-0.4.6 contourpy-1.3.1 cycler-0.12.1 fonttools-4.56.0 idna-3.10 kiwisolver-1.4.8 matplotlib-3.10.1 numpy-2.1.1 opencv-python-4.11.0.86 packaging-24.2 pandas-2.2.3 psutil-7.0.0 py-cpuinfo-9.0.0 pyparsing-3.2.1 python-dateutil-2.9.0.post0 pytz-2025.1 pyyaml-6.0.2 requests-2.32.3 scipy-1.15.2 seaborn-0.13.2 six-1.17.0 tqdm-4.67.1 tzdata-2025.1 ultralytics-8.3.87 ultralytics-thop-2.0.14 urllib3-2.3.0 [notice] A new release of pip is available: 24.3.1 -> 25.0.1 [notice] To update, run: python.exe -m pip install —upgrade pip (ultralytics) PS C:\Users\i> python.exe -m pip install —upgrade pip Defaulting to user installation because normal site-packages is not writeable Requirement already satisfied: pip in c:\python313\lib\site-packages (24.3.1) Collecting pip Downloading pip-25.0.1-py3-none-any.whl.metadata (3.7 kB) Downloading pip-25.0.1-py3-none-any.whl (1.8 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.8/1.8 MB 8.0 MB/s eta 0:00:00 Installing collected packages: pip WARNING: The scripts pip.exe, pip3.13.exe and pip3.exe are installed in ‘C:\Users\i\AppData\Roaming\Python\Python313\Scripts’ which is not on PATH. Consider adding this directory to PATH or, if you prefer to suppress this warning, use —no-warn-script-location. Successfully installed pip-25.0.1 (ultralytics) PS C:\Users\i> conda^C (ultralytics) PS C:\Users\i> pip list Package Version

certifi 2025.1.31 charset-normalizer 3.4.1 colorama 0.4.6 contourpy 1.3.1 cycler 0.12.1 filelock 3.13.1 fonttools 4.56.0 fsspec 2024.6.1 idna 3.10 Jinja2 3.1.4 kiwisolver 1.4.8 MarkupSafe 2.1.5 matplotlib 3.10.1 mpmath 1.3.0 networkx 3.3 numpy 2.1.1 opencv-python 4.11.0.86 packaging 24.2 pandas 2.2.3 pillow 11.0.0 pip 25.0.1 psutil 7.0.0 py-cpuinfo 9.0.0 pyparsing 3.2.1 python-dateutil 2.9.0.post0 pytz 2025.1 PyYAML 6.0.2 requests 2.32.3 scipy 1.15.2 seaborn 0.13.2 setuptools 70.2.0 six 1.17.0 sympy 1.13.1 torch 2.6.0+cu126 torchaudio 2.6.0+cu126 torchvision 0.21.0+cu126 tqdm 4.67.1 typing_extensions 4.12.2 tzdata 2025.1 ultralytics 8.3.87 ultralytics-thop 2.0.14 urllib3 2.3.0 (ultralytics) PS C:\Users\i>

SQL数据库连接链接规范

2025-02-18T01:44:16.000Z

https://docs.sqlalchemy.org/en/20/core/engines.html#database-urls

Win11 在有独显时如何默认使用核显

2025-02-15T13:00:24.000Z

正在跑深度学习，发现服务器有其他软件占用了独立显卡，但是按照网上的资料说设置NVIDIA控制面板里的首选图形处理器，发现Win11没有这个东西，https://www.zhihu.com/question/577660104 按照dvdedios的回答：

Thanks for replying. I didn’t use NVIDIA Control Panel, as NVCP says that “Windows OS now manages selection of the graphics processor”. 谢谢你的回复。我没有使用 NVIDIA 控制面板，因为 NVCP 说“Windows作系统现在管理图形处理器的选择”。

I have since solved my issue, as the ‘[HKEY_CURRENT_USER\SOFTWARE\Microsoft\DirectX\UserGpuPreferences]’ registry key holds the settings for GUI Windows Graphics Settings Menu, and setting the “(Default)” string to “GpuPreference=1;” seems to have done the trick. 从那以后，我解决了我的问题，因为“[HKEY_CURRENT_USER\SOFTWARE\Microsoft\DirectX\UserGpuPreferences]”注册表键保存了 GUI Windows 图形设置菜单的设置，并且将“（默认）”字符串设置为“GpuPreference=1;”似乎已经奏效了。

https://answers.microsoft.com/en-us/windows/forum/all/how-to-change-default-graphics-universal-default/b23d0e3b-da70-4227-a015-7d4bb6fe2fe6

OpenWRT中WAN6已经有/64地址，但不下发

2024-12-02T08:43:05.000Z

https://www.right.com.cn/FORUM/thread-8309440-1-1.html

Vmware共享文件夹自动挂载

2024-11-22T12:46:17.000Z

自动挂载

修改/etc/fstab，加入如下内容

.host:/ /mnt/hgfs fuse.vmhgfs-fuse allow_other,defaults 0 0

手动挂载

sudo vmhgfs-fuse .host:/ /mnt/hgfs -o allow_other

参考

使用selenium库出现Retrying问题

2024-10-08T01:14:49.000Z

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘NewConnectionError(‘<urllib3.connection.HTTPConnection object at 0x7ffeea688d30>: Failed to establish a new connection: [Errno 111] Connection refused’)’: /session/6adad5df-62b9-4032-99bb-b1c7848a7075/element/dfcda924-f4a0-42c1-8bd8-faf732ca18db/text 这里主要错误是 Max retries exceeded with url: 记一个bug，使用selenium.webdriver.Chrome().find_XX_XXX()获得的元素，必须在brower.close()或者brower.quit()使用，因为此时的元素是要依赖brower连接的所以解决办法是把获取的元素的text获取出来，然后再关闭brower 转发学习 ———————————————— 版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。原文链接：https://blog.csdn.net/API_demo/article/details/112323533

设置Mailcow自动跳转使用HTTPS

2024-09-30T12:17:11.000Z

官方给的教程会使容器跳警告，所以我自己编写了一个

if ($scheme = http) {
  return 302 https://$host$request_uri; 
}

将上面的代码插入到 /opt/mailcow-dockerized/data/conf/nginx/includes/site-defaults.conf

PVE容器无网络连接（Packet filtered）解决方案

2024-09-06T09:14:22.000Z

root@ams ~ # firewall-cmd —get-default-zone
public
root@ams ~ # firewall-cmd —list-all
You’re performing an operation over default zone (‘public’),
but your connections/interfaces are in zone ‘docker’ (see —get-active-zones)
You most likely need to use —zone=docker option.

public
target: default
icmp-block-inversion: no
interfaces:
sources:
services: dhcpv6-client ssh
ports: 37466/tcp 80/tcp 443/tcp 45767/tcp
protocols:
forward: yes
masquerade: yes
forward-ports:
source-ports:
icmp-blocks:
rich rules:
root@ams ~ # sudo firewall-cmd —permanent —new-zone=vmbr0zone
success
root@ams ~ # sudo firewall-cmd —permanent —zone=vmbr0zone —add-interface=vmbr0
success
root@ams ~ # sudo firewall-cmd —list-all —zone=vmbr0zone
Error: INVALID_ZONE: vmbr0zone
root@ams ~ # sudo firewall-cmd —permanent —zone=vmbr0zone —add-masquerade
success
root@ams ~ # sudo firewall-cmd —reload
success
root@ams ~ # sudo firewall-cmd —list-all —zone=vmbr0zone
vmbr0zone (active)
target: default
icmp-block-inversion: no
interfaces: vmbr0
sources:
services:
ports:
protocols:
forward: no
masquerade: yes
forward-ports:
source-ports:
icmp-blocks:
rich rules:
root@ams ~ # sudo firewall-cmd —permanent —zone=vmbr0zone —set-target=ACCEPT
success
root@ams ~ # sudo firewall-cmd —reload
success
root@ams ~ # sudo firewall-cmd —list-all —zone=vmbr0zone
vmbr0zone (active)
target: ACCEPT
icmp-block-inversion: no
interfaces: vmbr0
sources:
services:
ports:
protocols:
forward: no
masquerade: yes
forward-ports:
source-ports:
icmp-blocks:
rich rules:
root@ams ~ # sudo firewall-cmd —permanent —zone=vmbr0zone —add-rich-rule=‘rule family=“ipv4” source address=“10.10.10.0/24” accept’
sudo firewall-cmd —permanent —zone=vmbr0zone —add-rich-rule=‘rule family=“ipv6” source address=“fd80::/64” accept’
success
success
root@ams ~ # sudo firewall-cmd —reload
success

Debian 12 ARM 安装 PVE

2024-09-06T09:13:58.000Z

先安装好Debian12

然后检查配置，暂时不要使用NetworkManager，配置好之后再安装即可

/etc/network/interfaces

网络是否配置正确

之后检查hosts文件是否添加了本主机名，不然会启动不了

添加ARM PVE 源

echo "deb https://mirrors.apqa.cn/proxmox/debian/pve bookworm port">/etc/apt/sources.list.d/pveport.list

添加GPG密钥

curl -L https://mirrors.apqa.cn/proxmox/debian/pveport.gpg -o /etc/apt/trusted.gpg.d/pveport.gpg

更新源仓库之后安装基本软件

apt update && apt install -y chrony ksmtuned rsyslog ifupdown2

之后安装PVE

apt install -y proxmox-ve

PVE 指针(鼠标)漂移

2024-04-21T10:23:08.000Z

有时候会漂移，在 /etc/pve/qemu-server/xxx.conf 中加入：

xxx为你的虚拟机id

tablet: true

然后重新启动即可。

引用：https://www.mereith.com/post/146

HomeAssistant 修改历史记录保留天数

2024-04-08T13:54:37.000Z

修改配置文件

文件一般位于 /config/configuration.yaml，添加下面的配置：

recorder:
  purge_keep_days: 365
  commit_interval: 10

主要参数是 purge_keep_days ，上面保留天数修改为 365 天，默认值为 10 天。提交时间间隔 commit_interval 看自己需求修改，默认值为 5 秒。

参考资料

Recorder - Home Assistant [ HomeAssistant ] 修改历史记录保留天数 - YEUNGCHIE - 博客园 (cnblogs.com)

HE IPv6 考试通过攻略

2024-04-05T15:20:54.000Z

最近因为需要使用He Tunnel Broker，来获取IPv6，并且开启25端口，因为开启25端口需要HE IPv6考试得考到最高Sage等级，所以在网上搜索了一下教程

这个是我的证书(*・ω・)👉

证书

https://www.taterli.com/8500/

HE IPv6 考试通过攻略

下面的内容摘自上面的博客：

要取得HE的IPv6 Sage认证,就需要准备好域名+IPv6机器,以及RDNS部署好,看不懂英文和没耐心的请绕路.

登录认证网址:https://ipv6.he.net/certification/login.php (HE账户是处处通用的!)

考试中除了题目,还有提问,考试就简单了,懂得就直接过了,提问是怎么过的,要根据实际:

准备材料:

双栈VPS (IPv4 + IPv6) + RDNS 支持
域名 + DNS IPv6 支持
SSL - 可由Certbot配置
Nginx Web 或者同类软件
给域名设置好解释:

进行第一个测试:

接着填写你托管在Google Workspace等的邮箱地址,当然免费邮箱和国内大多数邮箱都过不了,然后把得到的代码填进去就行.

如果你托管在谷歌,接下来的测试就直接过了.

接下来网站解释也是送分,和上面图差不多,直接过.

问题答案参考:

问题:How many bits are in an IPv6 address?
答案:128

问题:Which of the following choices is a valid IPv6 address?
答案:2001:0db8:0:ff2e::1

问题:How many /64 subnets are available in a /48 prefix?
答案:65536

问题:How many available IPv6 addresses are there in a /64 allocation?
答案:18,446,744,073,709,551,616

问题:What operating systems currently support IPv6?
答案:All of the these support IPv6

问题:What features of IPv6 do you see yourself using?
答案:Larger Address Space

问题:If you were setting up a network of 12 million hosts that all needed their own unique globally routable addresses, which protocol would you use?
答案:IPv6
Question 3

问题:Do you plan on making sure your workplace is IPv6 ready before IPv4 exhaustion?
答案:Yes

问题:Do you think that any of your co-workers or friends would find Hurricane Electric’s IPv6 certification useful?
答案:Very much

问题:Do you think you would benefit from using Hurricane Electric’s free IPv6 certification process at work?
答案:Very much

问题:Are you enjoying the Hurricane Electric IPv6 certification process?
答案:Very much

问题:Did you like this level in the Hurricane Electric IPv6 certification process?
答案:Yes

问题:Is the price right for the Hurricane Electric free IPv6 certification process?
答案:A great bargain

问题:Does the network equipment you currently use support IPv6?
答案:All

问题:With regards to the server configuration portion, what level of difficulty would you rate it?
答案:Trivial

问题:Hurricane Electric would like to make sure you are completely happy with our free IPv6 certification process. Please rate your satisfaction on a scale of 1 to 5; 5 being completely satisfied, 1 being completely unsatisfied.
答案:5 - Completely Satisfied

问题:Have you asked your provider about when they plan on supporting IPv6?
答案:Yes

问题:Do you think that Internet oriented companies (software, hardware, or service providers) need to be IPv6 ready before IPv4 exhaustion?
答案:Yes

问题:Do you feel like you learned (or refreshed) your knowledge by completing the Hurricane Electric IPv6 certification process?
答案:Very much

问题:Are you able to understand the material?
答案:Yes

问题:Do you feel good about the Hurricane Electric free IPv6 certification process?
答案:Yes

问题:Have you asked your domain name registrar if they support IPv6?
答案:Yes

问题:You request IPv6 glue for your nameservers through:
答案:The registrar of the domain used by your name servers

问题:IPv6 glue for nameservers resides on which nameservers?
答案:The TLD/ccTLDs’

问题:Which of the following queries proves working IPv6 glue?
答案:dig AAAA ns1.exampledomain.tld @tld.server

问题:Which TLD listed below is authoritative for .com & .net IPv6 Glue?
答案:A.GTLD-SERVERS.net

问题:What is another name sometimes used for A or AAAA nameserver glue records found in the top level domain zone files?
答案:host records

问题:What is a registrar?
答案:An organization that is able to register domains

问题:What is a registry?
答案:An organization responsible for operating the authorative nameservers and database for a top level domain

问题:Why does getting AAAA records for your nameservers in the corresponding TLD (top level domain) zone matter?
答案:It enables entirely native IPv6 DNS queries and makes it possible for IPv6 only hosts to reach the nameservers for your domain, since they can’t use glue that is just an A record.

问题:IPv6 AAAA records have been added for several of the root nameservers.
答案:True

===========
问题:What command do you use to ping an IPv6 address on Free Open Source UNIX platforms such as Linux, FreeBSD, etc?
答案:ping6

问题:What command do you use to traceroute to an IPv6 address on Free Open Source UNIX platforms such as Linux, FreeBSD, etc?
答案:traceroute6

问题:What command do you use to ping an IPv6 address on a Microsoft Windows platform?
答案:ping

问题:What command do you use to traceroute to an IPv6 address on a Microsoft Windows platform?
答案:tracert

问题:IPv6 addresses are written using what number base?
答案:hexadecimal (base 16)

问题:Hexadecimal digits are represented by:
答案:0 to 9 and A to F

问题:On Redhat, CentOS, and Fedora Core systems that don’t accept ::/0 as the IPv6 default route, which of the following should you use instead?
答案:2000::/3

问题:When configuring forward DNS entries for use with an IPv6 address, what record type do you use?
答案:AAAA

问题:When configuring reverse DNS with BIND for addresses in the IPv6 allocation 2001:A:B:C::/64, what is the correct format for the zone?
答案:C.0.0.0.B.0.0.0.A.0.0.0.1.0.0.2.ip6.arpa

问题:What is the IPv6 default route?
答案:::/0

问题:What is the IPv6 localhost address?
答案:::1/128

问题:Which of the following is a link-local address?
答案:fe80::20c:dbff:fefb:232b

问题:Which of the following URLs specifies a literal IPv6 address correctly?
答案:http://[2001:470:0:64::2]

问题:Which of the following URLs specifies a literal IPv6 address and port number correctly?
答案:https://[2001:0db8:85a3:08d3:1319:8a2e:0370:7344]:443

问题:If you run native IPv4 and IPv6 at the same time this is called:
答案:Dual stack

问题:How do you use the dig command to get the IPv6 address record for domain he.net?
答案:dig he.net AAAA

问题:How do you use the dig command to get the PTR record for the IPv6 address 2001:470:0:76::2?
答案:dig -x 2001:470:0:76::2

问题:What command shows IPv6 addresses configured on ethernet interfaces under UNIX (Linux, FreeBSD, etc.)?
答案:ifconfig

问题:What command shows IPv6 addresses configured on ethernet interfaces under Microsoft Windows?
答案:ipconfig

问题:Under FreeBSD, what does the generic tunneling interface start with?
答案:gif

问题:Under Linux, what kernel module needs to be loaded to support IPv6 networking?
答案:ipv6

问题:Are routers allowed to fragment IPv6 packets?
答案:No

问题:How many bytes are in an IPv6 address?
答案:16

问题:How many /48 subnets are available in a /32 prefix?
答案:65536

问题:Which protocol is used for manually configured tunnels?
答案:6in4

问题:Which of the following is the IPv6 documentation prefix?
答案:2001:db8::/32

问题:Which of the following is the IPv6 link-local prefix?
答案:fe80::/10

问题:Which of the following is the IPv6 multicast prefix?
答案:ff00::/8

问题:Which of the following is the IPv6 ULA (unique local addresses) prefix?
答案:fc00::/7

问题:Which of the following is a subnet of 2001:db8::/32?
答案:2001:db8:7fa5::/48

问题:On Linux, how would you traceroute to the IPv6 address of he.net?
答案:traceroute6 he.net

问题:On Windows Vista, how would you traceroute to the IPv6 address of he.net?
答案:tracert he.net

问题:On Linux, what is the IPv6 ping command?
答案:ping6

问题:Which command forces the UNIX command ssh to use IPv6 to connect to example.com (useful for domains with both A and AAAA records)?
答案:ssh -6 example.com

问题:You would force the UNIX command ssh to use IPv4 (useful if it had both A and AAAA records) to connect to example.com using which command?
答案:ssh -4 example.com

问题:Which command forces the UNIX command wget to use IPv6 to make a HTTP GET request to he.net (useful for domains with both A and AAAA records)?
答案:wget -6 he.net

问题:Which command forces the UNIX command wget to use IPv4 to make a HTTP GET request to he.net (useful for domains with both A and AAAA records)?
答案:wget -4 he.net

问题:Which command forces the UNIX command mtr to use IPv6 to traceroute to he.net (useful for domains with both A and AAAA records)?
答案:mtr -6 he.net

问题:Which command forces the UNIX command mtr to use IPv4 to traceroute to he.net (useful for domains with both A and AAAA records)?
答案:mtr -4 he.net

问题:When using basic auto-configuration, what is used from the host to configure the last 64bits of the IPv6 address?
答案:The MAC address of the ethernet interface

问题:A MAC address is only 48bits. So when using basic auto-configuration, what is used to fill in the missing 16bits?
答案:FFFE

问题:On many routers, which one of the following commands is used to configure an IPv6 address on an interface?
答案:ipv6 address 2001:A:B:C::1/64

问题:What is the length of an IPv6 packet header?
答案:40 bytes

问题:Which of the following organizations assigns IPv6 addresses?
答案:All of the above

问题:What protocol number is used for 6in4 IPv4 packets?
答案:41

问题:Which of the following is the 6to4 IPv6 prefix?
答案:2002::/16

问题:Which of the following well-known prefixes is used for Teredo?
答案:2001:0000::/32

问题:Which of the following is an IPv4-mapped IPv6 address?
答案:::ffff:10.10.10.2

问题:On operating systems that support it, IPv4-mapped IPv6 addresses are used to:
答案:map IPv4 addresses to an IPv6 address to make it so that IPv6 socket system calls can be used with both IPv4 or IPv6 addresses

问题:Which of the following is an IPv4-compatible IPv6 address?
答案:::10.10.10.2

问题:IPv4-compatible IPv6 addresses are deprecated in RFC 4291.
答案:True

问题:Should you ever see packets with IPv4-mapped IPv6 addresses on the wire (outside of a host)?
答案:No

问题:Which version of OSPF supports IPv6?
答案:OSPFv3

问题:Which of the following can be used by an IPv6 host to learn the address of a default gateway?
答案:neighbor discovery protocol

问题:Which of the following can be used by a host to learn its own IPv6 address?
答案:stateless autoconfiguration

问题:If you translate IPv4 packets to IPv6 or IPv6 packets to IPv4, this is called:
答案:NAT64/DNS64/DS-Lite

问题:On many routers, what command shows IPv6 routes?
答案:show ipv6 route

问题:On many routers, what command shows IPv6 BGP sessions?
答案:show ipv6 bgp summary

问题:On many routers, what command shows IPv6 BGP routes?
答案:sh ipv6 bgp

360 T7路由器刷入小米WR30u固件修改MAC后获取终端密码

2024-04-03T10:13:38.000Z

备份一下论坛的代码 360 T7成功刷入小米WR30u的固件很稳可组网适合养老（0607已传512内存版）

#!/usr/bin/env php
<?php //路由器固件解包后，从 /bin/mkxqimage 中提取的盐 $salt = array( 'r1d' => 'A2E371B0-B34B-48A5-8C40-A7133F3B5D88',
    'others' => 'd44fb0960aa0-a5e6-4a30-250f-6d2df50a'
);

isset($argv[1]) or die('Usage: ' . $argv[0] . " SN\n");
print_line(get_passwd($argv[1]));

function print_line($message) {
    echo $message . "\n";
}

//密码算法：
//原始 SN 拼接反转后的盐，做 md5 运算取前 8 个字符
function get_passwd($sn) {
    return substr(md5($sn . get_salt($sn)), 0, 8);
}

// SN 中不含 '/' 则为 r1d
#function get_salt($sn) {
#    global $salt;
#    if (false === strpos($sn, '/')) {
#        return $salt['r1d'];
#    } else {
#        return swap_salt($salt['others']);
#    }
#}

// SN 中不含 '/' 则为 r1d
function get_salt($sn) {
    global $salt;
    //if (false === strpos($sn, '/')) {
    //    return $salt['r1d'];
    //} else {
    //    return swap_salt($salt['others']);
    //}
    return swap_salt($salt['others']);
}

//非 R1D 盐要反转后才能使用
function swap_salt($salt) {
    return implode('-', array_reverse(explode('-', $salt)));
}

香橙派 5 Plus CPU RK3588 测试

2024-04-03T09:56:47.000Z


root@op ~# bash ./sbc-bench.sh -c

Average load and/or CPU utilization too high (too much background activity). Waiting...

Too busy for benchmarking: 23:04:28 up 39 min, 3 users, load average: 1.39, 1.27, 1.11, cpu: 1%
Too busy for benchmarking: 23:04:33 up 39 min, 3 users, load average: 1.35, 1.27, 1.11, cpu: 0%
Too busy for benchmarking: 23:04:38 up 39 min, 3 users, load average: 1.33, 1.26, 1.11, cpu: 0%
Too busy for benchmarking: 23:04:43 up 39 min, 3 users, load average: 1.30, 1.26, 1.11, cpu: 0%
Too busy for benchmarking: 23:04:48 up 39 min, 3 users, load average: 1.28, 1.26, 1.11, cpu: 0%
Too busy for benchmarking: 23:04:53 up 39 min, 3 users, load average: 1.25, 1.25, 1.11, cpu: 0%

Status of performance related governors found below /sys (w/o cpufreq):
dmc: performance / 2112 MHz (rknpu_ondemand dmc_ondemand userspace powersave performance simple_ondemand / 528 1068 1560 2112)
fb000000.gpu: performance / 1000 MHz (rknpu_ondemand dmc_ondemand userspace powersave performance simple_ondemand / 300 400 500 600 700 800 900 1000)
fdab0000.npu: performance / 1000 MHz (rknpu_ondemand dmc_ondemand userspace powersave performance simple_ondemand / 300 400 500 600 700 800 900 1000)

sbc-bench v0.9.60

Installing needed tools: Done.
Checking cpufreq OPP. Done (results will be available in 21-32 minutes).
Executing tinymembench. Done.
Executing RAM latency tester. Done.
Executing OpenSSL benchmark. Done.
Executing 7-zip benchmark. Done.
Executing cpuminer. 5 more minutes to wait. Done.
Checking cpufreq OPP again. Done (21 minutes elapsed).

Results validation:

* Advertised vs. measured max CPU clockspeed: -3.0% before, -4.0% after -> https://tinyurl.com/32w9rr94
* No swapping
* Background activity (%system) OK
* No throttling

Memory performance (all 3 CPU clusters measured individually):
memcpy: 6709.4 MB/s (Cortex-A55)
memset: 21654.4 MB/s (Cortex-A55)
memcpy: 12247.3 MB/s (Cortex-A76)
memset: 29740.2 MB/s (Cortex-A76)
memcpy: 12553.5 MB/s (Cortex-A76)
memset: 29569.5 MB/s (Cortex-A76)

Cpuminer total scores (5 minutes execution): 23.96,23.95,23.94,23.93,23.92,23.91,23.90,23.89,23.88,23.85,23.83 kH/s

7-zip total scores (3 consecutive runs): 16279,16400,16489, single-threaded: 3117

OpenSSL results (all 3 CPU clusters measured individually):
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes
aes-128-cbc 158023.79k 468676.91k 915873.62k 1210427.05k 1336194.39k 1346655.57k (Cortex-A55)
aes-128-cbc 644442.67k 1273380.20k 1642038.02k 1762216.28k 1809047.55k 1813861.72k (Cortex-A76)
aes-128-cbc 630312.15k 1242141.21k 1602185.81k 1717907.46k 1763661.14k 1768308.74k (Cortex-A76)
aes-192-cbc 150778.60k 417122.11k 745103.62k 933005.99k 1006034.94k 1011919.53k (Cortex-A55)
aes-192-cbc 601137.05k 1123098.86k 1393824.68k 1468218.71k 1509064.70k 1512172.20k (Cortex-A76)
aes-192-cbc 585598.94k 1094835.78k 1357408.60k 1431271.08k 1470950.06k 1473937.41k (Cortex-A76)
aes-256-cbc 146126.97k 383489.64k 645938.01k 780054.53k 830193.66k 834251.43k (Cortex-A55)
aes-256-cbc 580311.18k 998646.87k 1208005.89k 1270018.39k 1294180.35k 1296405.85k (Cortex-A76)
aes-256-cbc 568428.99k 973770.22k 1177625.43k 1238337.88k 1261497.00k 1263736.15k (Cortex-A76)

Unable to upload full test results. Please copy&paste the below stuff to pastebin.com and
provide the URL. Check the output for throttling and swapping please.

sbc-bench v0.9.60 Orange Pi 5 Plus (Tue, 16 Jan 2024 23:05:00 +0800)

Distributor ID: Ubuntu
Description: Ubuntu 22.04.3 LTS
Release: 22.04
Codename: jammy

/usr/bin/gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Uptime: 23:05:00 up 39 min, 3 users, load average: 1.31, 1.26, 1.11, 37.9°C, 81978082

Linux 5.10.160-rockchip (op) 2024年01月16日 _aarch64_ (8 CPU)

avg-cpu: %user %nice %system %iowait %steal %idle
0.92 0.06 0.57 0.03 0.00 98.41

Device tps kB_read/s kB_wrtn/s kB_dscd/s kB_read kB_wrtn kB_dscd
mmcblk0 13.86 383.18 367.48 0.00 918145 880510 0
nvme0n1 0.10 2.40 0.00 0.00 5760 0 0

total used free shared buff/cache available
Mem: 15Gi 920Mi 14Gi 8.0Mi 328Mi 14Gi
Swap: 11Gi 0B 11Gi

Filename Type Size Used Priority
/swapfile file 12582908 0 -2

##########################################################################

Checking cpufreq OPP for cpu0-cpu3 (Cortex-A55):

Cpufreq OPP: 1800 Measured: 1785 (1785.631/1785.251/1784.783)
Cpufreq OPP: 1608 Measured: 1599 (1599.723/1599.583/1599.543)
Cpufreq OPP: 1416 Measured: 1400 (1400.325/1400.255/1400.027) (-1.1%)
Cpufreq OPP: 1200 Measured: 1223 (1223.353/1223.215/1223.124) (+1.9%)
Cpufreq OPP: 1008 Measured: 999 (999.630/999.580/999.518)
Cpufreq OPP: 816 Measured: 798 (798.695/798.635/798.605) (-2.2%)
Cpufreq OPP: 600 Measured: 590 (590.988/590.892/590.818) (-1.7%)
Cpufreq OPP: 408 Measured: 392 (392.876/392.812/392.782) (-3.9%)

Checking cpufreq OPP for cpu4-cpu5 (Cortex-A76):

Cpufreq OPP: 2352 Measured: 2281 (2281.632/2281.574/2281.457) (-3.0%)
Cpufreq OPP: 2208 Measured: 2193 (2193.471/2193.198/2192.624)
Cpufreq OPP: 2016 Measured: 1981 (1982.086/1981.584/1981.459) (-1.7%)
Cpufreq OPP: 1800 Measured: 1812 (1812.707/1812.391/1812.211)
Cpufreq OPP: 1608 Measured: 1612 (1613.109/1612.587/1612.066)
Cpufreq OPP: 1416 Measured: 1396 (1396.162/1396.023/1395.953) (-1.4%)
Cpufreq OPP: 1200 Measured: 1159 (1159.867/1159.651/1159.579) (-3.4%)
Cpufreq OPP: 1008 Measured: 970 (970.556/970.471/970.170) (-3.8%)
Cpufreq OPP: 816 Measured: 777 (777.185/777.165/776.914) (-4.8%)
Cpufreq OPP: 600 Measured: 579 (579.454/579.203/579.160) (-3.5%)
Cpufreq OPP: 408 Measured: 381 (381.920/381.906/381.872) (-6.6%)

Checking cpufreq OPP for cpu6-cpu7 (Cortex-A76):

Cpufreq OPP: 2256 Measured: 2222 (2222.384/2222.190/2222.134) (-1.5%)
Cpufreq OPP: 2208 Measured: 2160 (2160.416/2160.335/2160.146) (-2.2%)
Cpufreq OPP: 2016 Measured: 1992 (1992.752/1992.678/1992.603) (-1.2%)
Cpufreq OPP: 1800 Measured: 1819 (1819.628/1819.582/1819.355) (+1.1%)
Cpufreq OPP: 1608 Measured: 1614 (1614.403/1614.302/1614.282)
Cpufreq OPP: 1416 Measured: 1429 (1429.785/1429.785/1429.731)
Cpufreq OPP: 1200 Measured: 1180 (1180.324/1180.206/1180.132) (-1.7%)
Cpufreq OPP: 1008 Measured: 994 (994.395/994.345/994.295) (-1.4%)
Cpufreq OPP: 816 Measured: 797 (797.797/797.777/797.728) (-2.3%)
Cpufreq OPP: 600 Measured: 592 (592.843/592.836/592.806) (-1.3%)
Cpufreq OPP: 408 Measured: 394 (394.884/394.855/394.850) (-3.4%)

##########################################################################

Hardware sensors:

nvme-pci-0100
Composite: +35.9 C (low = -0.1 C, high = +82.8 C)
(crit = +83.8 C)
Sensor 1: +27.9 C (low = -273.1 C, high = +65261.8 C)
Sensor 2: +31.9 C (low = -273.1 C, high = +65261.8 C)

npu_thermal-virtual-0
temp1: +36.1 C

center_thermal-virtual-0
temp1: +36.1 C

bigcore1_thermal-virtual-0
temp1: +37.0 C

soc_thermal-virtual-0
temp1: +37.0 C (crit = +115.0 C)

tcpm_source_psy_6_0022-i2c-6-22
in0: 0.00 V (min = +0.00 V, max = +0.00 V)
curr1: 0.00 A (max = +0.00 A)

gpu_thermal-virtual-0
temp1: +36.1 C

littlecore_thermal-virtual-0
temp1: +37.0 C

bigcore0_thermal-virtual-0
temp1: +37.0 C

/dev/nvme0: 36°C

##########################################################################

Executing benchmark on cpu0 (Cortex-A55):

tinymembench v0.4.9-nuumio (simple benchmark for memory throughput and latency)

CFLAGS:
bandwidth test min repeats (-b): 2
bandwidth test max repeats (-B): 3
bandwidth test mem realloc (-M): no (-m for realloc)
latency test repeats (-l): 3
latency test count (-c): 1000000

==========================================================================
== Memory bandwidth tests ==
== ==
== Note 1: 1MB = 1000000 bytes ==
== Note 2: Test result is the best of repeated runs. Number of repeats ==
== is shown in brackets ==
== Note 3: Results for 'copy' tests show how many bytes can be ==
== copied per second (adding together read and writen ==
== bytes would have provided twice higher numbers) ==
== Note 4: 2-pass copy means that we are using a small temporary buffer ==
== to first fetch data into it, and only then write it to the ==
== destination (source -> L1 cache, L1 cache -> destination) ==
== Note 5: If sample standard deviation exceeds 0.1%, it is shown in ==
== brackets ==
==========================================================================

C copy backwards : 3530.3 MB/s (3, 9.8%)
C copy backwards (32 byte blocks) : 3505.3 MB/s (2)
C copy backwards (64 byte blocks) : 3541.4 MB/s (3, 0.1%)
C copy : 6182.8 MB/s (2)
C copy prefetched (32 bytes step) : 2455.4 MB/s (2)
C copy prefetched (64 bytes step) : 6369.9 MB/s (2)
C 2-pass copy : 2862.1 MB/s (3, 1.0%)
C 2-pass copy prefetched (32 bytes step) : 1651.3 MB/s (3, 0.1%)
C 2-pass copy prefetched (64 bytes step) : 3126.9 MB/s (2)
C scan 8 : 442.9 MB/s (2)
C scan 16 : 880.6 MB/s (2)
C scan 32 : 1746.8 MB/s (2)
C scan 64 : 3442.5 MB/s (2)
C fill : 12301.6 MB/s (2)
C fill (shuffle within 16 byte blocks) : 12302.0 MB/s (2)
C fill (shuffle within 32 byte blocks) : 12299.6 MB/s (2)
C fill (shuffle within 64 byte blocks) : 12010.0 MB/s (2)
---
libc memcpy copy : 6709.4 MB/s (2)
libc memchr scan : 2765.3 MB/s (2)
libc memset fill : 21654.4 MB/s (2)
---
NEON LDP/STP copy : 5671.8 MB/s (2)
NEON LDP/STP copy pldl2strm (32 bytes step) : 1923.3 MB/s (2)
NEON LDP/STP copy pldl2strm (64 bytes step) : 3762.7 MB/s (2)
NEON LDP/STP copy pldl1keep (32 bytes step) : 2787.6 MB/s (2)
NEON LDP/STP copy pldl1keep (64 bytes step) : 5418.6 MB/s (2)
NEON LD1/ST1 copy : 5454.1 MB/s (2)
NEON LDP load : 6970.9 MB/s (2)
NEON LDNP load : 7161.4 MB/s (3, 0.2%)
NEON STP fill : 21574.4 MB/s (2)
NEON STNP fill : 15231.2 MB/s (3, 0.8%)
ARM LDP/STP copy : 5673.8 MB/s (2)
ARM LDP load : 6968.3 MB/s (2)
ARM LDNP load : 7147.6 MB/s (2)
ARM STP fill : 21573.5 MB/s (2)
ARM STNP fill : 15225.8 MB/s (3, 0.9%)

==========================================================================
== Memory latency test ==
== ==
== Average time is measured for random memory accesses in the buffers ==
== of different sizes. The larger is the buffer, the more significant ==
== are relative contributions of TLB, L1/L2 cache misses and SDRAM ==
== accesses. For extremely large buffer sizes we are expecting to see ==
== page table walk with several requests to SDRAM for almost every ==
== memory access (though 64MiB is not nearly large enough to experience ==
== this effect to its fullest). ==
== ==
== Note 1: All the numbers are representing extra time, which needs to ==
== be added to L1 cache latency. The cycle timings for L1 cache ==
== latency can be usually found in the processor documentation. ==
== Note 2: Dual random read means that we are simultaneously performing ==
== two independent memory accesses at a time. In the case if ==
== the memory subsystem can't handle multiple outstanding ==
== requests, dual random read has the same timings as two ==
== single reads performed one after another. ==
==========================================================================

block size : single random read / dual random read
1024 : 0.0 ns / 0.0 ns
2048 : 0.0 ns / 0.0 ns
4096 : 0.0 ns / 0.0 ns
8192 : 0.0 ns / 0.0 ns
16384 : 0.1 ns / 0.2 ns
32768 : 1.0 ns / 1.0 ns
65536 : 1.6 ns / 2.7 ns
131072 : 3.9 ns / 6.1 ns
262144 : 8.6 ns / 12.2 ns
524288 : 12.8 ns / 15.4 ns
1048576 : 15.5 ns / 16.5 ns
2097152 : 20.0 ns / 19.5 ns
4194304 : 42.9 ns / 63.0 ns
8388608 : 82.6 ns / 110.2 ns
16777216 : 102.9 ns / 126.4 ns
33554432 : 115.0 ns / 136.3 ns
67108864 : 121.2 ns / 144.2 ns

Executing benchmark on cpu4 (Cortex-A76):

tinymembench v0.4.9-nuumio (simple benchmark for memory throughput and latency)

CFLAGS:
bandwidth test min repeats (-b): 2
bandwidth test max repeats (-B): 3
bandwidth test mem realloc (-M): no (-m for realloc)
latency test repeats (-l): 3
latency test count (-c): 1000000

==========================================================================
== Memory bandwidth tests ==
== ==
== Note 1: 1MB = 1000000 bytes ==
== Note 2: Test result is the best of repeated runs. Number of repeats ==
== is shown in brackets ==
== Note 3: Results for 'copy' tests show how many bytes can be ==
== copied per second (adding together read and writen ==
== bytes would have provided twice higher numbers) ==
== Note 4: 2-pass copy means that we are using a small temporary buffer ==
== to first fetch data into it, and only then write it to the ==
== destination (source -> L1 cache, L1 cache -> destination) ==
== Note 5: If sample standard deviation exceeds 0.1%, it is shown in ==
== brackets ==
==========================================================================

C copy backwards : 11830.3 MB/s (2)
C copy backwards (32 byte blocks) : 11819.9 MB/s (2)
C copy backwards (64 byte blocks) : 11816.1 MB/s (3, 0.2%)
C copy : 12012.6 MB/s (2)
C copy prefetched (32 bytes step) : 12249.3 MB/s (2)
C copy prefetched (64 bytes step) : 12273.9 MB/s (2)
C 2-pass copy : 4715.7 MB/s (2)
C 2-pass copy prefetched (32 bytes step) : 7129.1 MB/s (2)
C 2-pass copy prefetched (64 bytes step) : 6626.4 MB/s (2)
C scan 8 : 1130.6 MB/s (2)
C scan 16 : 2259.8 MB/s (2)
C scan 32 : 4512.8 MB/s (2)
C scan 64 : 8989.9 MB/s (2)
C fill : 29740.5 MB/s (3, 0.5%)
C fill (shuffle within 16 byte blocks) : 29727.1 MB/s (2)
C fill (shuffle within 32 byte blocks) : 29702.3 MB/s (3, 0.2%)
C fill (shuffle within 64 byte blocks) : 29646.1 MB/s (2)
---
libc memcpy copy : 12247.3 MB/s (2)
libc memchr scan : 16291.3 MB/s (2)
libc memset fill : 29740.2 MB/s (3, 0.6%)
---
NEON LDP/STP copy : 12278.6 MB/s (2)
NEON LDP/STP copy pldl2strm (32 bytes step) : 12296.5 MB/s (3, 0.3%)
NEON LDP/STP copy pldl2strm (64 bytes step) : 12315.3 MB/s (2)
NEON LDP/STP copy pldl1keep (32 bytes step) : 12306.4 MB/s (2)
NEON LDP/STP copy pldl1keep (64 bytes step) : 12302.4 MB/s (2)
NEON LD1/ST1 copy : 12227.7 MB/s (2)
NEON LDP load : 18802.3 MB/s (2)
NEON LDNP load : 17943.9 MB/s (2)
NEON STP fill : 29727.9 MB/s (3, 0.9%)
NEON STNP fill : 29706.6 MB/s (2)
ARM LDP/STP copy : 12342.3 MB/s (2)
ARM LDP load : 18379.6 MB/s (3)
ARM LDNP load : 17379.1 MB/s (2)
ARM STP fill : 29727.0 MB/s (3, 0.7%)
ARM STNP fill : 29704.7 MB/s (3, 0.9%)

==========================================================================
== Memory latency test ==
== ==
== Average time is measured for random memory accesses in the buffers ==
== of different sizes. The larger is the buffer, the more significant ==
== are relative contributions of TLB, L1/L2 cache misses and SDRAM ==
== accesses. For extremely large buffer sizes we are expecting to see ==
== page table walk with several requests to SDRAM for almost every ==
== memory access (though 64MiB is not nearly large enough to experience ==
== this effect to its fullest). ==
== ==
== Note 1: All the numbers are representing extra time, which needs to ==
== be added to L1 cache latency. The cycle timings for L1 cache ==
== latency can be usually found in the processor documentation. ==
== Note 2: Dual random read means that we are simultaneously performing ==
== two independent memory accesses at a time. In the case if ==
== the memory subsystem can't handle multiple outstanding ==
== requests, dual random read has the same timings as two ==
== single reads performed one after another. ==
==========================================================================

block size : single random read / dual random read
1024 : 0.0 ns / 0.0 ns
2048 : 0.0 ns / 0.0 ns
4096 : 0.0 ns / 0.0 ns
8192 : 0.0 ns / 0.0 ns
16384 : 0.0 ns / 0.0 ns
32768 : 0.1 ns / 0.0 ns
65536 : 0.1 ns / 0.0 ns
131072 : 1.3 ns / 1.5 ns
262144 : 2.6 ns / 2.9 ns
524288 : 5.6 ns / 6.5 ns
1048576 : 11.7 ns / 13.4 ns
2097152 : 20.8 ns / 17.3 ns
4194304 : 41.3 ns / 55.3 ns
8388608 : 77.6 ns / 101.4 ns
16777216 : 98.6 ns / 117.6 ns
33554432 : 109.4 ns / 123.7 ns
67108864 : 115.5 ns / 127.2 ns

Executing benchmark on cpu6 (Cortex-A76):

tinymembench v0.4.9-nuumio (simple benchmark for memory throughput and latency)

CFLAGS:
bandwidth test min repeats (-b): 2
bandwidth test max repeats (-B): 3
bandwidth test mem realloc (-M): no (-m for realloc)
latency test repeats (-l): 3
latency test count (-c): 1000000

==========================================================================
== Memory bandwidth tests ==
== ==
== Note 1: 1MB = 1000000 bytes ==
== Note 2: Test result is the best of repeated runs. Number of repeats ==
== is shown in brackets ==
== Note 3: Results for 'copy' tests show how many bytes can be ==
== copied per second (adding together read and writen ==
== bytes would have provided twice higher numbers) ==
== Note 4: 2-pass copy means that we are using a small temporary buffer ==
== to first fetch data into it, and only then write it to the ==
== destination (source -> L1 cache, L1 cache -> destination) ==
== Note 5: If sample standard deviation exceeds 0.1%, it is shown in ==
== brackets ==
==========================================================================

C copy backwards : 12208.1 MB/s (2)
C copy backwards (32 byte blocks) : 12193.4 MB/s (2)
C copy backwards (64 byte blocks) : 12187.7 MB/s (3, 0.3%)
C copy : 12311.4 MB/s (2)
C copy prefetched (32 bytes step) : 12487.3 MB/s (2)
C copy prefetched (64 bytes step) : 12532.2 MB/s (2)
C 2-pass copy : 4963.4 MB/s (3, 0.2%)
C 2-pass copy prefetched (32 bytes step) : 7180.5 MB/s (2)
C 2-pass copy prefetched (64 bytes step) : 6598.2 MB/s (3, 0.2%)
C scan 8 : 1102.7 MB/s (2)
C scan 16 : 2204.2 MB/s (2)
C scan 32 : 4405.8 MB/s (2)
C scan 64 : 8784.3 MB/s (2)
C fill : 29692.8 MB/s (3, 1.0%)
C fill (shuffle within 16 byte blocks) : 29710.4 MB/s (3, 0.3%)
C fill (shuffle within 32 byte blocks) : 29527.6 MB/s (2)
C fill (shuffle within 64 byte blocks) : 29769.8 MB/s (3, 0.4%)
---
libc memcpy copy : 12553.5 MB/s (2)
libc memchr scan : 16547.1 MB/s (2)
libc memset fill : 29569.5 MB/s (3, 0.9%)
---
NEON LDP/STP copy : 12564.3 MB/s (3, 0.2%)
NEON LDP/STP copy pldl2strm (32 bytes step) : 12565.8 MB/s (2)
NEON LDP/STP copy pldl2strm (64 bytes step) : 12580.9 MB/s (2)
NEON LDP/STP copy pldl1keep (32 bytes step) : 12578.9 MB/s (2)
NEON LDP/STP copy pldl1keep (64 bytes step) : 12579.3 MB/s (2)
NEON LD1/ST1 copy : 12533.7 MB/s (2)
NEON LDP load : 19080.1 MB/s (2)
NEON LDNP load : 18200.1 MB/s (2)
NEON STP fill : 29612.6 MB/s (3, 0.9%)
NEON STNP fill : 29736.4 MB/s (3, 0.4%)
ARM LDP/STP copy : 12547.9 MB/s (2)
ARM LDP load : 18596.4 MB/s (2)
ARM LDNP load : 17484.8 MB/s (2)
ARM STP fill : 29535.6 MB/s (3, 1.7%)
ARM STNP fill : 29655.8 MB/s (2)

==========================================================================
== Memory latency test ==
== ==
== Average time is measured for random memory accesses in the buffers ==
== of different sizes. The larger is the buffer, the more significant ==
== are relative contributions of TLB, L1/L2 cache misses and SDRAM ==
== accesses. For extremely large buffer sizes we are expecting to see ==
== page table walk with several requests to SDRAM for almost every ==
== memory access (though 64MiB is not nearly large enough to experience ==
== this effect to its fullest). ==
== ==
== Note 1: All the numbers are representing extra time, which needs to ==
== be added to L1 cache latency. The cycle timings for L1 cache ==
== latency can be usually found in the processor documentation. ==
== Note 2: Dual random read means that we are simultaneously performing ==
== two independent memory accesses at a time. In the case if ==
== the memory subsystem can't handle multiple outstanding ==
== requests, dual random read has the same timings as two ==
== single reads performed one after another. ==
==========================================================================

block size : single random read / dual random read
1024 : 0.0 ns / 0.0 ns
2048 : 0.0 ns / 0.0 ns
4096 : 0.0 ns / 0.0 ns
8192 : 0.0 ns / 0.0 ns
16384 : 0.0 ns / 0.0 ns
32768 : 0.0 ns / 0.0 ns
65536 : 0.1 ns / 0.0 ns
131072 : 1.3 ns / 1.6 ns
262144 : 2.7 ns / 2.9 ns
524288 : 5.0 ns / 6.2 ns
1048576 : 11.8 ns / 13.6 ns
2097152 : 17.7 ns / 17.5 ns
4194304 : 40.4 ns / 54.1 ns
8388608 : 76.7 ns / 100.6 ns
16777216 : 97.2 ns / 117.3 ns
33554432 : 111.3 ns / 123.4 ns
67108864 : 114.2 ns / 127.0 ns

##########################################################################

Executing ramlat on cpu0 (Cortex-A55), results in ns:

size: 1x32 2x32 1x64 2x64 1xPTR 2xPTR 4xPTR 8xPTR
4k: 1.693 1.706 1.693 1.690 1.125 1.688 2.286 4.610
8k: 1.687 1.687 1.687 1.688 1.125 1.687 2.285 4.606
16k: 1.699 1.687 1.698 1.687 1.134 1.687 2.285 4.606
32k: 1.715 1.690 1.714 1.690 1.139 1.690 2.290 4.612
64k: 10.09 11.41 10.10 11.42 10.20 11.45 16.29 29.59
128k: 13.56 15.00 13.56 15.00 14.40 15.02 22.06 40.92
256k: 16.16 16.69 16.16 16.66 15.36 16.71 26.16 50.61
512k: 16.96 17.15 16.97 17.16 16.27 17.39 27.17 54.02
1024k: 17.23 17.29 17.13 17.29 16.53 17.53 28.40 54.22
2048k: 19.69 19.44 18.54 19.42 18.19 19.58 31.92 61.08
4096k: 57.41 67.01 54.35 68.29 54.01 64.94 105.6 216.1
8192k: 96.91 101.2 94.52 101.3 93.91 101.9 156.5 278.2
16384k: 116.1 114.9 113.2 114.7 112.9 116.3 174.8 313.5
32768k: 124.8 124.2 122.0 123.8 120.8 125.0 184.8 318.6
65536k: 128.7 130.2 129.0 130.2 127.8 130.2 188.8 327.8
131072k: 136.3 136.9 136.1 137.0 135.0 137.1 191.8 332.9

Executing ramlat on cpu4 (Cortex-A76), results in ns:

size: 1x32 2x32 1x64 2x64 1xPTR 2xPTR 4xPTR 8xPTR
4k: 1.759 1.759 1.761 1.759 1.759 1.761 1.759 3.350
8k: 1.759 1.759 1.761 1.759 1.758 1.761 1.759 3.427
16k: 1.761 1.759 1.761 1.759 1.758 1.761 1.759 3.429
32k: 1.761 1.759 1.761 1.759 1.758 1.761 1.759 3.429
64k: 1.768 1.762 1.768 1.762 1.765 1.768 1.765 3.436
128k: 5.365 5.361 5.367 5.361 5.359 6.063 7.555 13.36
256k: 6.200 6.270 6.199 6.260 6.207 6.208 7.758 13.33
512k: 10.85 9.717 10.73 9.730 10.66 10.30 11.78 18.56
1024k: 18.17 18.24 18.21 18.24 18.18 18.23 20.07 29.81
2048k: 24.91 22.42 24.48 22.39 24.53 22.57 24.24 34.35
4096k: 53.47 43.37 52.73 43.42 52.76 45.01 47.28 56.33
8192k: 97.69 83.00 96.80 82.99 96.00 84.52 85.43 89.93
16384k: 115.7 105.5 114.3 112.5 114.2 113.7 111.4 111.7
32768k: 122.7 124.8 124.6 125.5 122.0 123.6 122.0 116.6
65536k: 127.9 128.7 127.4 128.6 127.2 127.0 126.6 126.2
131072k: 129.3 130.7 129.5 130.8 129.6 129.1 129.0 134.4

Executing ramlat on cpu6 (Cortex-A76), results in ns:

size: 1x32 2x32 1x64 2x64 1xPTR 2xPTR 4xPTR 8xPTR
4k: 1.806 1.805 1.805 1.805 1.804 1.805 1.805 3.434
8k: 1.804 1.805 1.804 1.804 1.804 1.805 1.805 3.516
16k: 1.804 1.804 1.804 1.804 1.804 1.804 1.805 3.516
32k: 1.804 1.804 1.804 1.804 1.804 1.804 1.805 3.519
64k: 1.805 1.805 1.805 1.805 1.805 1.805 1.806 3.520
128k: 5.497 5.501 5.497 5.500 5.496 6.211 7.776 13.68
256k: 7.186 7.389 7.306 7.392 7.287 7.380 8.626 14.65
512k: 10.51 9.942 10.45 9.923 10.51 10.60 12.24 18.88
1024k: 18.95 18.14 18.85 18.14 18.85 18.26 20.25 31.20
2048k: 21.68 20.44 20.69 20.44 20.69 20.84 22.90 33.09
4096k: 54.06 42.33 51.32 42.30 51.00 44.55 45.66 55.49
8192k: 98.55 81.92 95.08 81.42 94.55 83.05 80.44 84.47
16384k: 121.1 112.3 114.9 105.6 114.0 108.6 108.6 102.8
32768k: 125.1 126.0 121.8 125.5 122.2 123.1 121.7 109.4
65536k: 127.0 127.6 126.8 127.8 126.9 126.0 126.5 124.4
131072k: 129.4 129.9 128.8 129.7 128.7 128.4 129.3 132.8

##########################################################################

Executing benchmark on each cluster individually

OpenSSL 3.0.2, built on 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes
aes-128-cbc 158023.79k 468676.91k 915873.62k 1210427.05k 1336194.39k 1346655.57k (Cortex-A55)
aes-128-cbc 644442.67k 1273380.20k 1642038.02k 1762216.28k 1809047.55k 1813861.72k (Cortex-A76)
aes-128-cbc 630312.15k 1242141.21k 1602185.81k 1717907.46k 1763661.14k 1768308.74k (Cortex-A76)
aes-192-cbc 150778.60k 417122.11k 745103.62k 933005.99k 1006034.94k 1011919.53k (Cortex-A55)
aes-192-cbc 601137.05k 1123098.86k 1393824.68k 1468218.71k 1509064.70k 1512172.20k (Cortex-A76)
aes-192-cbc 585598.94k 1094835.78k 1357408.60k 1431271.08k 1470950.06k 1473937.41k (Cortex-A76)
aes-256-cbc 146126.97k 383489.64k 645938.01k 780054.53k 830193.66k 834251.43k (Cortex-A55)
aes-256-cbc 580311.18k 998646.87k 1208005.89k 1270018.39k 1294180.35k 1296405.85k (Cortex-A76)
aes-256-cbc 568428.99k 973770.22k 1177625.43k 1238337.88k 1261497.00k 1263736.15k (Cortex-A76)

##########################################################################

Executing benchmark single-threaded on cpu0 (Cortex-A55)

7-Zip (a) [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=C,Utf16=off,HugeFiles=on,64 bits,8 CPUs LE)

LE
CPU Freq: - - 64000000 - - - - - -

RAM size: 15966 MB, # CPU hardware threads: 8
RAM usage: 435 MB, # Benchmark threads: 1

Compressing | Decompressing
Dict Speed Usage R/U Rating | Speed Usage R/U Rating
KiB/s % MIPS MIPS | KiB/s % MIPS MIPS

22: 1369 100 1333 1332 | 21619 100 1846 1846
23: 1296 100 1322 1321 | 21315 100 1845 1845
24: 1264 100 1359 1359 | 20967 100 1841 1841
25: 1226 100 1400 1400 | 20363 100 1813 1812
---------------------------------- | ------------------------------
Avr: 100 1353 1353 | 100 1836 1836
Tot: 100 1595 1595

Executing benchmark single-threaded on cpu4 (Cortex-A76)

7-Zip (a) [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=C,Utf16=off,HugeFiles=on,64 bits,8 CPUs LE)

LE
CPU Freq: - - - 64000000 - - - - -

RAM size: 15966 MB, # CPU hardware threads: 8
RAM usage: 435 MB, # Benchmark threads: 1

Compressing | Decompressing
Dict Speed Usage R/U Rating | Speed Usage R/U Rating
KiB/s % MIPS MIPS | KiB/s % MIPS MIPS

22: 3131 99 3079 3046 | 37379 99 3219 3191
23: 2941 99 3034 2997 | 36885 99 3221 3193
24: 2833 99 3084 3047 | 36246 99 3210 3182
25: 2737 99 3163 3126 | 35419 99 3181 3153
---------------------------------- | ------------------------------
Avr: 99 3090 3054 | 99 3208 3180
Tot: 99 3149 3117

Executing benchmark single-threaded on cpu6 (Cortex-A76)

7-Zip (a) [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=C,Utf16=off,HugeFiles=on,64 bits,8 CPUs LE)

LE
CPU Freq: - - - - - 256000000 - - -

RAM size: 15966 MB, # CPU hardware threads: 8
RAM usage: 435 MB, # Benchmark threads: 1

Compressing | Decompressing
Dict Speed Usage R/U Rating | Speed Usage R/U Rating
KiB/s % MIPS MIPS | KiB/s % MIPS MIPS

22: 3110 100 3026 3026 | 36506 100 3117 3117
23: 2931 100 2988 2987 | 36120 100 3127 3127
24: 2850 100 3065 3064 | 35483 100 3115 3115
25: 2727 100 3114 3114 | 34768 100 3095 3095
---------------------------------- | ------------------------------
Avr: 100 3048 3048 | 100 3113 3113
Tot: 100 3081 3081

##########################################################################

Executing benchmark 3 times multi-threaded on CPUs 0-7

7-Zip (a) [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=C,Utf16=off,HugeFiles=on,64 bits,8 CPUs LE)

LE
CPU Freq: - - - - - - - - -

RAM size: 15966 MB, # CPU hardware threads: 8
RAM usage: 1765 MB, # Benchmark threads: 8

Compressing | Decompressing
Dict Speed Usage R/U Rating | Speed Usage R/U Rating
KiB/s % MIPS MIPS | KiB/s % MIPS MIPS

22: 14683 654 2185 14284 | 200756 671 2553 17124
23: 15540 750 2110 15833 | 198338 676 2540 17164
24: 14688 734 2153 15793 | 193155 673 2520 16953
25: 14222 764 2125 16239 | 189283 675 2496 16845
---------------------------------- | ------------------------------
Avr: 725 2143 15537 | 674 2527 17021
Tot: 700 2335 16279

7-Zip (a) [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=C,Utf16=off,HugeFiles=on,64 bits,8 CPUs LE)

LE
CPU Freq: - - - - - - - - -

RAM size: 15966 MB, # CPU hardware threads: 8
RAM usage: 1765 MB, # Benchmark threads: 8

Compressing | Decompressing
Dict Speed Usage R/U Rating | Speed Usage R/U Rating
KiB/s % MIPS MIPS | KiB/s % MIPS MIPS

22: 16102 726 2159 15664 | 200146 672 2540 17072
23: 15210 721 2149 15498 | 196975 673 2532 17046
24: 14716 753 2102 15823 | 193497 675 2516 16983
25: 14290 774 2108 16316 | 188778 674 2493 16800
---------------------------------- | ------------------------------
Avr: 743 2129 15825 | 674 2520 16975
Tot: 708 2325 16400

7-Zip (a) [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=C,Utf16=off,HugeFiles=on,64 bits,8 CPUs LE)

LE
CPU Freq: - - - - - - - 1024000000 -

RAM size: 15966 MB, # CPU hardware threads: 8
RAM usage: 1765 MB, # Benchmark threads: 8

Compressing | Decompressing
Dict Speed Usage R/U Rating | Speed Usage R/U Rating
KiB/s % MIPS MIPS | KiB/s % MIPS MIPS

22: 16296 741 2141 15854 | 201042 675 2539 17148
23: 15730 755 2122 16028 | 196471 673 2527 17002
24: 14747 747 2122 15857 | 193518 676 2514 16985
25: 14217 764 2125 16233 | 188797 675 2489 16802
---------------------------------- | ------------------------------
Avr: 752 2127 15993 | 675 2517 16984
Tot: 713 2322 16489

Compression: 15537,15825,15993
Decompression: 17021,16975,16984
Total: 16279,16400,16489

##########################################################################

** cpuminer-multi 1.3.7 by tpruvot@github **
BTC donation address: 1FhDPLPpw18X4srecguG3MxJYe4a1JsZnd (tpruvot)

[2024-01-16 23:20:07] 8 miner threads started, using 'scrypt' algorithm.
[2024-01-16 23:20:07] CPU #5: 4.23 kH/s
[2024-01-16 23:20:07] CPU #4: 4.02 kH/s
[2024-01-16 23:20:07] CPU #6: 4.05 kH/s
[2024-01-16 23:20:07] CPU #7: 4.04 kH/s
[2024-01-16 23:20:08] CPU #1: 1.75 kH/s
[2024-01-16 23:20:08] CPU #3: 1.75 kH/s
[2024-01-16 23:20:08] CPU #2: 1.74 kH/s
[2024-01-16 23:20:08] CPU #0: 1.73 kH/s
[2024-01-16 23:20:12] Total: 23.53 kH/s
[2024-01-16 23:20:17] CPU #0: 1.75 kH/s
[2024-01-16 23:20:17] CPU #2: 1.75 kH/s
[2024-01-16 23:20:17] CPU #1: 1.76 kH/s
[2024-01-16 23:20:17] CPU #3: 1.76 kH/s
[2024-01-16 23:20:17] CPU #4: 4.27 kH/s
[2024-01-16 23:20:17] CPU #7: 4.17 kH/s
[2024-01-16 23:20:17] Total: 23.79 kH/s
[2024-01-16 23:20:17] CPU #6: 4.16 kH/s
[2024-01-16 23:20:17] CPU #5: 4.32 kH/s
[2024-01-16 23:20:22] Total: 23.95 kH/s
[2024-01-16 23:20:27] CPU #0: 1.75 kH/s
[2024-01-16 23:20:27] CPU #2: 1.75 kH/s
[2024-01-16 23:20:27] CPU #3: 1.76 kH/s
[2024-01-16 23:20:27] CPU #1: 1.76 kH/s
[2024-01-16 23:20:27] CPU #4: 4.28 kH/s
[2024-01-16 23:20:27] CPU #7: 4.17 kH/s
[2024-01-16 23:20:27] Total: 23.96 kH/s
[2024-01-16 23:20:27] CPU #6: 4.17 kH/s
[2024-01-16 23:20:27] CPU #5: 4.30 kH/s
[2024-01-16 23:20:32] Total: 23.94 kH/s
[2024-01-16 23:20:37] CPU #0: 1.75 kH/s
[2024-01-16 23:20:37] CPU #3: 1.76 kH/s
[2024-01-16 23:20:37] CPU #1: 1.75 kH/s
[2024-01-16 23:20:37] CPU #2: 1.73 kH/s
[2024-01-16 23:20:37] CPU #4: 4.26 kH/s
[2024-01-16 23:20:37] CPU #6: 4.17 kH/s
[2024-01-16 23:20:37] CPU #7: 4.17 kH/s
[2024-01-16 23:20:37] Total: 23.85 kH/s
[2024-01-16 23:20:37] CPU #5: 4.27 kH/s
[2024-01-16 23:20:42] Total: 23.91 kH/s
[2024-01-16 23:20:47] CPU #0: 1.75 kH/s
[2024-01-16 23:20:47] CPU #2: 1.75 kH/s
[2024-01-16 23:20:47] CPU #3: 1.76 kH/s
[2024-01-16 23:20:47] CPU #1: 1.76 kH/s
[2024-01-16 23:20:47] CPU #4: 4.27 kH/s
[2024-01-16 23:20:47] CPU #6: 4.16 kH/s
[2024-01-16 23:20:47] CPU #7: 4.17 kH/s
[2024-01-16 23:20:47] Total: 23.95 kH/s
[2024-01-16 23:20:47] CPU #5: 4.32 kH/s
[2024-01-16 23:20:52] Total: 23.95 kH/s
[2024-01-16 23:20:57] CPU #0: 1.75 kH/s
[2024-01-16 23:20:57] CPU #2: 1.75 kH/s
[2024-01-16 23:20:57] CPU #3: 1.76 kH/s
[2024-01-16 23:20:57] CPU #1: 1.75 kH/s
[2024-01-16 23:20:57] CPU #4: 4.27 kH/s
[2024-01-16 23:20:57] CPU #6: 4.17 kH/s
[2024-01-16 23:20:57] CPU #7: 4.17 kH/s
[2024-01-16 23:20:57] Total: 23.94 kH/s
[2024-01-16 23:20:57] CPU #5: 4.32 kH/s
[2024-01-16 23:21:02] Total: 23.94 kH/s
[2024-01-16 23:21:07] CPU #0: 1.75 kH/s
[2024-01-16 23:21:07] CPU #2: 1.75 kH/s
[2024-01-16 23:21:07] CPU #1: 1.76 kH/s
[2024-01-16 23:21:07] CPU #3: 1.76 kH/s
[2024-01-16 23:21:07] CPU #4: 4.27 kH/s
[2024-01-16 23:21:07] CPU #6: 4.17 kH/s
[2024-01-16 23:21:07] CPU #7: 4.17 kH/s
[2024-01-16 23:21:07] Total: 23.94 kH/s
[2024-01-16 23:21:07] CPU #5: 4.32 kH/s
[2024-01-16 23:21:12] Total: 23.93 kH/s
[2024-01-16 23:21:17] CPU #0: 1.75 kH/s
[2024-01-16 23:21:17] CPU #2: 1.75 kH/s
[2024-01-16 23:21:17] CPU #1: 1.76 kH/s
[2024-01-16 23:21:17] CPU #3: 1.76 kH/s
[2024-01-16 23:21:17] CPU #4: 4.27 kH/s
[2024-01-16 23:21:17] CPU #6: 4.17 kH/s
[2024-01-16 23:21:17] CPU #5: 4.32 kH/s
[2024-01-16 23:21:17] CPU #7: 4.16 kH/s
[2024-01-16 23:21:17] Total: 23.94 kH/s
[2024-01-16 23:21:22] Total: 23.94 kH/s
[2024-01-16 23:21:27] CPU #0: 1.75 kH/s
[2024-01-16 23:21:27] CPU #2: 1.75 kH/s
[2024-01-16 23:21:27] CPU #1: 1.75 kH/s
[2024-01-16 23:21:27] CPU #3: 1.76 kH/s
[2024-01-16 23:21:27] CPU #4: 4.27 kH/s
[2024-01-16 23:21:27] CPU #6: 4.17 kH/s
[2024-01-16 23:21:27] CPU #7: 4.17 kH/s
[2024-01-16 23:21:27] Total: 23.94 kH/s
[2024-01-16 23:21:27] CPU #5: 4.32 kH/s
[2024-01-16 23:21:32] Total: 23.94 kH/s
[2024-01-16 23:21:37] CPU #0: 1.75 kH/s
[2024-01-16 23:21:37] CPU #2: 1.75 kH/s
[2024-01-16 23:21:37] CPU #1: 1.75 kH/s
[2024-01-16 23:21:37] CPU #3: 1.76 kH/s
[2024-01-16 23:21:37] CPU #4: 4.27 kH/s
[2024-01-16 23:21:37] CPU #6: 4.17 kH/s
[2024-01-16 23:21:37] CPU #7: 4.17 kH/s
[2024-01-16 23:21:37] Total: 23.94 kH/s
[2024-01-16 23:21:37] CPU #5: 4.32 kH/s
[2024-01-16 23:21:42] Total: 23.93 kH/s
[2024-01-16 23:21:47] CPU #0: 1.75 kH/s
[2024-01-16 23:21:47] CPU #2: 1.75 kH/s
[2024-01-16 23:21:47] CPU #1: 1.75 kH/s
[2024-01-16 23:21:47] CPU #3: 1.76 kH/s
[2024-01-16 23:21:47] CPU #4: 4.27 kH/s
[2024-01-16 23:21:47] CPU #6: 4.16 kH/s
[2024-01-16 23:21:47] CPU #5: 4.31 kH/s
[2024-01-16 23:21:47] CPU #7: 4.16 kH/s
[2024-01-16 23:21:47] Total: 23.92 kH/s
[2024-01-16 23:21:52] Total: 23.94 kH/s
[2024-01-16 23:21:57] CPU #0: 1.75 kH/s
[2024-01-16 23:21:57] CPU #2: 1.75 kH/s
[2024-01-16 23:21:57] CPU #1: 1.75 kH/s
[2024-01-16 23:21:57] CPU #3: 1.76 kH/s
[2024-01-16 23:21:57] CPU #4: 4.27 kH/s
[2024-01-16 23:21:57] CPU #6: 4.17 kH/s
[2024-01-16 23:21:57] CPU #7: 4.17 kH/s
[2024-01-16 23:21:57] Total: 23.94 kH/s
[2024-01-16 23:21:57] CPU #5: 4.32 kH/s
[2024-01-16 23:22:02] Total: 23.94 kH/s
[2024-01-16 23:22:07] CPU #0: 1.75 kH/s
[2024-01-16 23:22:07] CPU #2: 1.75 kH/s
[2024-01-16 23:22:07] CPU #1: 1.75 kH/s
[2024-01-16 23:22:07] CPU #3: 1.76 kH/s
[2024-01-16 23:22:07] CPU #4: 4.27 kH/s
[2024-01-16 23:22:07] CPU #6: 4.17 kH/s
[2024-01-16 23:22:07] CPU #7: 4.17 kH/s
[2024-01-16 23:22:07] Total: 23.94 kH/s
[2024-01-16 23:22:07] CPU #5: 4.32 kH/s
[2024-01-16 23:22:12] Total: 23.92 kH/s
[2024-01-16 23:22:17] CPU #0: 1.75 kH/s
[2024-01-16 23:22:17] CPU #2: 1.75 kH/s
[2024-01-16 23:22:17] CPU #1: 1.75 kH/s
[2024-01-16 23:22:17] CPU #3: 1.76 kH/s
[2024-01-16 23:22:17] CPU #4: 4.27 kH/s
[2024-01-16 23:22:17] CPU #6: 4.17 kH/s
[2024-01-16 23:22:17] CPU #5: 4.31 kH/s
[2024-01-16 23:22:17] CPU #7: 4.16 kH/s
[2024-01-16 23:22:17] Total: 23.93 kH/s
[2024-01-16 23:22:22] Total: 23.93 kH/s
[2024-01-16 23:22:27] CPU #0: 1.75 kH/s
[2024-01-16 23:22:27] CPU #2: 1.75 kH/s
[2024-01-16 23:22:27] CPU #1: 1.75 kH/s
[2024-01-16 23:22:27] CPU #3: 1.76 kH/s
[2024-01-16 23:22:27] CPU #4: 4.27 kH/s
[2024-01-16 23:22:27] CPU #6: 4.16 kH/s
[2024-01-16 23:22:27] CPU #5: 4.31 kH/s
[2024-01-16 23:22:27] CPU #7: 4.15 kH/s
[2024-01-16 23:22:27] Total: 23.90 kH/s
[2024-01-16 23:22:32] Total: 23.92 kH/s
[2024-01-16 23:22:37] CPU #0: 1.75 kH/s
[2024-01-16 23:22:37] CPU #2: 1.75 kH/s
[2024-01-16 23:22:37] CPU #1: 1.75 kH/s
[2024-01-16 23:22:37] CPU #3: 1.76 kH/s
[2024-01-16 23:22:37] CPU #4: 4.25 kH/s
[2024-01-16 23:22:37] CPU #6: 4.17 kH/s
[2024-01-16 23:22:37] CPU #7: 4.17 kH/s
[2024-01-16 23:22:37] Total: 23.85 kH/s
[2024-01-16 23:22:37] CPU #5: 4.25 kH/s
[2024-01-16 23:22:42] Total: 23.92 kH/s
[2024-01-16 23:22:47] CPU #0: 1.75 kH/s
[2024-01-16 23:22:47] CPU #2: 1.75 kH/s
[2024-01-16 23:22:47] CPU #1: 1.75 kH/s
[2024-01-16 23:22:47] CPU #3: 1.76 kH/s
[2024-01-16 23:22:47] CPU #4: 4.27 kH/s
[2024-01-16 23:22:47] CPU #6: 4.16 kH/s
[2024-01-16 23:22:47] CPU #5: 4.31 kH/s
[2024-01-16 23:22:47] CPU #7: 4.16 kH/s
[2024-01-16 23:22:47] Total: 23.92 kH/s
[2024-01-16 23:22:52] Total: 23.93 kH/s
[2024-01-16 23:22:57] CPU #0: 1.75 kH/s
[2024-01-16 23:22:57] CPU #2: 1.75 kH/s
[2024-01-16 23:22:57] CPU #1: 1.75 kH/s
[2024-01-16 23:22:57] CPU #3: 1.76 kH/s
[2024-01-16 23:22:57] CPU #4: 4.27 kH/s
[2024-01-16 23:22:57] CPU #6: 4.16 kH/s
[2024-01-16 23:22:57] CPU #5: 4.31 kH/s
[2024-01-16 23:22:57] CPU #7: 4.16 kH/s
[2024-01-16 23:22:57] Total: 23.92 kH/s
[2024-01-16 23:23:02] Total: 23.93 kH/s
[2024-01-16 23:23:07] CPU #0: 1.75 kH/s
[2024-01-16 23:23:07] CPU #2: 1.75 kH/s
[2024-01-16 23:23:07] CPU #1: 1.75 kH/s
[2024-01-16 23:23:07] CPU #3: 1.76 kH/s
[2024-01-16 23:23:07] CPU #4: 4.27 kH/s
[2024-01-16 23:23:07] CPU #6: 4.17 kH/s
[2024-01-16 23:23:07] CPU #5: 4.31 kH/s
[2024-01-16 23:23:07] CPU #7: 4.16 kH/s
[2024-01-16 23:23:07] Total: 23.92 kH/s
[2024-01-16 23:23:12] Total: 23.88 kH/s
[2024-01-16 23:23:17] CPU #0: 1.75 kH/s
[2024-01-16 23:23:17] CPU #2: 1.75 kH/s
[2024-01-16 23:23:17] CPU #1: 1.75 kH/s
[2024-01-16 23:23:17] CPU #3: 1.75 kH/s
[2024-01-16 23:23:17] CPU #4: 4.27 kH/s
[2024-01-16 23:23:17] CPU #6: 4.16 kH/s
[2024-01-16 23:23:17] CPU #5: 4.31 kH/s
[2024-01-16 23:23:17] CPU #7: 4.16 kH/s
[2024-01-16 23:23:17] Total: 23.92 kH/s
[2024-01-16 23:23:22] Total: 23.92 kH/s
[2024-01-16 23:23:27] CPU #0: 1.75 kH/s
[2024-01-16 23:23:27] CPU #2: 1.75 kH/s
[2024-01-16 23:23:27] CPU #1: 1.75 kH/s
[2024-01-16 23:23:27] CPU #3: 1.75 kH/s
[2024-01-16 23:23:27] CPU #4: 4.27 kH/s
[2024-01-16 23:23:27] CPU #6: 4.17 kH/s
[2024-01-16 23:23:27] CPU #5: 4.31 kH/s
[2024-01-16 23:23:27] CPU #7: 4.16 kH/s
[2024-01-16 23:23:27] Total: 23.92 kH/s
[2024-01-16 23:23:32] Total: 23.92 kH/s
[2024-01-16 23:23:37] CPU #0: 1.75 kH/s
[2024-01-16 23:23:37] CPU #2: 1.75 kH/s
[2024-01-16 23:23:37] CPU #1: 1.75 kH/s
[2024-01-16 23:23:37] CPU #3: 1.75 kH/s
[2024-01-16 23:23:37] CPU #4: 4.27 kH/s
[2024-01-16 23:23:37] CPU #6: 4.17 kH/s
[2024-01-16 23:23:37] CPU #5: 4.31 kH/s
[2024-01-16 23:23:37] CPU #7: 4.16 kH/s
[2024-01-16 23:23:37] Total: 23.92 kH/s
[2024-01-16 23:23:42] Total: 23.92 kH/s
[2024-01-16 23:23:47] CPU #0: 1.75 kH/s
[2024-01-16 23:23:47] CPU #2: 1.75 kH/s
[2024-01-16 23:23:47] CPU #1: 1.75 kH/s
[2024-01-16 23:23:47] CPU #3: 1.75 kH/s
[2024-01-16 23:23:47] CPU #4: 4.27 kH/s
[2024-01-16 23:23:47] CPU #6: 4.16 kH/s
[2024-01-16 23:23:47] CPU #5: 4.31 kH/s
[2024-01-16 23:23:47] CPU #7: 4.17 kH/s
[2024-01-16 23:23:47] Total: 23.92 kH/s
[2024-01-16 23:23:52] Total: 23.92 kH/s
[2024-01-16 23:23:57] CPU #0: 1.75 kH/s
[2024-01-16 23:23:57] CPU #2: 1.75 kH/s
[2024-01-16 23:23:57] CPU #1: 1.75 kH/s
[2024-01-16 23:23:57] CPU #3: 1.75 kH/s
[2024-01-16 23:23:57] CPU #4: 4.26 kH/s
[2024-01-16 23:23:57] CPU #6: 4.16 kH/s
[2024-01-16 23:23:57] CPU #5: 4.31 kH/s
[2024-01-16 23:23:57] CPU #7: 4.16 kH/s
[2024-01-16 23:23:57] Total: 23.89 kH/s
[2024-01-16 23:24:02] Total: 23.91 kH/s
[2024-01-16 23:24:07] CPU #0: 1.75 kH/s
[2024-01-16 23:24:07] CPU #2: 1.75 kH/s
[2024-01-16 23:24:07] CPU #1: 1.75 kH/s
[2024-01-16 23:24:07] CPU #3: 1.75 kH/s
[2024-01-16 23:24:07] CPU #4: 4.27 kH/s
[2024-01-16 23:24:07] CPU #6: 4.16 kH/s
[2024-01-16 23:24:07] CPU #5: 4.31 kH/s
[2024-01-16 23:24:07] CPU #7: 4.16 kH/s
[2024-01-16 23:24:07] Total: 23.91 kH/s
[2024-01-16 23:24:12] Total: 23.89 kH/s
[2024-01-16 23:24:17] CPU #0: 1.75 kH/s
[2024-01-16 23:24:17] CPU #2: 1.75 kH/s
[2024-01-16 23:24:17] CPU #1: 1.75 kH/s
[2024-01-16 23:24:17] CPU #3: 1.75 kH/s
[2024-01-16 23:24:17] CPU #4: 4.27 kH/s
[2024-01-16 23:24:17] CPU #6: 4.16 kH/s
[2024-01-16 23:24:17] CPU #5: 4.31 kH/s
[2024-01-16 23:24:17] CPU #7: 4.16 kH/s
[2024-01-16 23:24:17] Total: 23.90 kH/s
[2024-01-16 23:24:22] Total: 23.90 kH/s
[2024-01-16 23:24:27] CPU #0: 1.75 kH/s
[2024-01-16 23:24:27] CPU #2: 1.75 kH/s
[2024-01-16 23:24:27] CPU #1: 1.75 kH/s
[2024-01-16 23:24:27] CPU #3: 1.75 kH/s
[2024-01-16 23:24:27] CPU #4: 4.27 kH/s
[2024-01-16 23:24:27] CPU #6: 4.16 kH/s
[2024-01-16 23:24:27] CPU #5: 4.31 kH/s
[2024-01-16 23:24:27] CPU #7: 4.16 kH/s
[2024-01-16 23:24:27] Total: 23.90 kH/s
[2024-01-16 23:24:32] Total: 23.91 kH/s
[2024-01-16 23:24:37] CPU #0: 1.75 kH/s
[2024-01-16 23:24:37] CPU #2: 1.75 kH/s
[2024-01-16 23:24:37] CPU #1: 1.75 kH/s
[2024-01-16 23:24:37] CPU #3: 1.75 kH/s
[2024-01-16 23:24:37] CPU #4: 4.27 kH/s
[2024-01-16 23:24:37] CPU #6: 4.16 kH/s
[2024-01-16 23:24:37] CPU #7: 4.16 kH/s
[2024-01-16 23:24:37] Total: 23.85 kH/s
[2024-01-16 23:24:37] CPU #5: 4.25 kH/s
[2024-01-16 23:24:42] Total: 23.83 kH/s
[2024-01-16 23:24:47] CPU #0: 1.75 kH/s
[2024-01-16 23:24:47] CPU #2: 1.75 kH/s
[2024-01-16 23:24:47] CPU #1: 1.75 kH/s
[2024-01-16 23:24:47] CPU #3: 1.75 kH/s
[2024-01-16 23:24:47] CPU #4: 4.27 kH/s
[2024-01-16 23:24:47] CPU #6: 4.15 kH/s
[2024-01-16 23:24:47] CPU #5: 4.31 kH/s
[2024-01-16 23:24:47] CPU #7: 4.16 kH/s
[2024-01-16 23:24:47] Total: 23.89 kH/s
[2024-01-16 23:24:52] Total: 23.91 kH/s
[2024-01-16 23:24:57] CPU #2: 1.75 kH/s
[2024-01-16 23:24:57] CPU #1: 1.75 kH/s
[2024-01-16 23:24:57] CPU #3: 1.75 kH/s
[2024-01-16 23:24:57] CPU #4: 4.27 kH/s
[2024-01-16 23:24:57] CPU #6: 4.16 kH/s
[2024-01-16 23:24:57] CPU #5: 4.31 kH/s
[2024-01-16 23:24:57] CPU #7: 4.16 kH/s
[2024-01-16 23:24:57] Total: 23.90 kH/s
[2024-01-16 23:24:58] CPU #0: 1.75 kH/s
[2024-01-16 23:25:02] Total: 23.90 kH/s
[2024-01-16 23:25:06] CPU #0: 1.75 kH/s
[2024-01-16 23:25:07] CPU #2: 1.75 kH/s
[2024-01-16 23:25:07] CPU #1: 1.75 kH/s
[2024-01-16 23:25:07] CPU #3: 1.75 kH/s
[2024-01-16 23:25:07] CPU #4: 4.27 kH/s

Total Scores: 23.96,23.95,23.94,23.93,23.92,23.91,23.90,23.89,23.88,23.85,23.83

##########################################################################

Testing maximum cpufreq again, still under full load. System health now:

Time cpu0/cpu4/cpu6 load %cpu %sys %usr %nice %io %irq Temp
23:24:42: 1800/2352/2256MHz 9.06 100% 0% 99% 0% 0% 0% 64.7°C

Checking cpufreq OPP for cpu0-cpu3 (Cortex-A55):

Cpufreq OPP: 1800 Measured: 1767 (1767.742/1767.123/1766.880) (-1.8%)

Checking cpufreq OPP for cpu4-cpu5 (Cortex-A76):

Cpufreq OPP: 2352 Measured: 2257 (2257.552/2256.976/2256.573) (-4.0%)

Checking cpufreq OPP for cpu6-cpu7 (Cortex-A76):

Cpufreq OPP: 2256 Measured: 2200 (2200.810/2200.535/2200.205) (-2.5%)

##########################################################################

Hardware sensors:

nvme-pci-0100
Composite: +42.9 C (low = -0.1 C, high = +82.8 C)
(crit = +83.8 C)
Sensor 1: +35.9 C (low = -273.1 C, high = +65261.8 C)
Sensor 2: +40.9 C (low = -273.1 C, high = +65261.8 C)

npu_thermal-virtual-0
temp1: +51.8 C

center_thermal-virtual-0
temp1: +51.8 C

bigcore1_thermal-virtual-0
temp1: +52.7 C

soc_thermal-virtual-0
temp1: +52.7 C (crit = +115.0 C)

tcpm_source_psy_6_0022-i2c-6-22
in0: 0.00 V (min = +0.00 V, max = +0.00 V)
curr1: 0.00 A (max = +0.00 A)

gpu_thermal-virtual-0
temp1: +51.8 C

littlecore_thermal-virtual-0
temp1: +52.7 C

bigcore0_thermal-virtual-0
temp1: +51.8 C

/dev/nvme0: 43°C

##########################################################################

DRAM clock transitions since last boot (3617430 ms ago):

/sys/devices/platform/dmc/devfreq/dmc:

From : To
: 528000000106800000015600000002112000000 time(ms)
528000000: 0 0 0 13366 118320
1068000000: 3 0 0 69 810
1560000000: 0 0 0 0 0
*2112000000: 13363 72 0 0 3495600
Total transition : 26873

##########################################################################

Thermal source: /sys/devices/virtual/thermal/thermal_zone0/ (soc-thermal)

System health while running tinymembench:

Time cpu0/cpu4/cpu6 load %cpu %sys %usr %nice %io %irq Temp
23:07:18: 1800/2352/2256MHz 1.94 2% 0% 1% 0% 0% 0% 38.8°C
23:07:48: 1800/2352/2256MHz 1.96 12% 0% 12% 0% 0% 0% 41.6°C
23:08:18: 1800/2352/2256MHz 1.98 12% 0% 12% 0% 0% 0% 44.4°C
23:08:48: 1800/2352/2256MHz 1.99 12% 0% 12% 0% 0% 0% 47.2°C
23:09:19: 1800/2352/2256MHz 1.99 12% 0% 12% 0% 0% 0% 47.2°C
23:09:49: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 48.1°C

System health while running ramlat:

Time cpu0/cpu4/cpu6 load %cpu %sys %usr %nice %io %irq Temp
23:10:18: 1800/2352/2256MHz 2.00 2% 0% 2% 0% 0% 0% 46.2°C
23:10:27: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 43.5°C
23:10:36: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 42.5°C
23:10:45: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 41.6°C
23:10:54: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 41.6°C
23:11:03: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 41.6°C
23:11:12: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 41.6°C
23:11:21: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 40.7°C
23:11:30: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 40.7°C
23:11:39: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 41.6°C

System health while running OpenSSL benchmark:

Time cpu0/cpu4/cpu6 load %cpu %sys %usr %nice %io %irq Temp
23:11:49: 1800/2352/2256MHz 2.00 3% 0% 2% 0% 0% 0% 42.5°C
23:12:05: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 40.7°C
23:12:21: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 40.7°C
23:12:37: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 41.6°C
23:12:53: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 40.7°C
23:13:09: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 40.7°C
23:13:25: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 41.6°C
23:13:41: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 39.8°C
23:13:57: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 40.7°C
23:14:13: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 41.6°C
23:14:29: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 41.6°C

System health while running 7-zip single core benchmark:

Time cpu0/cpu4/cpu6 load %cpu %sys %usr %nice %io %irq Temp
23:14:31: 1800/2352/2256MHz 2.00 3% 0% 3% 0% 0% 0% 41.6°C
23:14:39: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 40.7°C
23:14:47: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 39.8°C
23:14:55: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 39.8°C
23:15:03: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 39.8°C
23:15:11: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 39.8°C
23:15:19: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 39.8°C
23:15:27: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 39.8°C
23:15:35: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 39.8°C
23:15:43: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 39.8°C
23:15:51: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 39.8°C
23:15:59: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 38.8°C
23:16:07: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 40.7°C
23:16:15: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 40.7°C
23:16:24: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 41.6°C
23:16:32: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 41.6°C
23:16:40: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 41.6°C
23:16:48: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 42.5°C
23:16:56: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 42.5°C
23:17:04: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 41.6°C
23:17:12: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 42.5°C
23:17:20: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 42.5°C
23:17:28: 1800/2352/2256MHz 2.00 12% 0% 12% 0% 0% 0% 42.5°C

System health while running 7-zip multi core benchmark:

Time cpu0/cpu4/cpu6 load %cpu %sys %usr %nice %io %irq Temp
23:17:35: 1800/2352/2256MHz 2.00 4% 0% 3% 0% 0% 0% 48.1°C
23:17:45: 1800/2352/2256MHz 2.56 80% 0% 79% 0% 0% 0% 49.9°C
23:17:55: 1800/2352/2256MHz 3.70 86% 0% 86% 0% 0% 0% 51.8°C
23:18:05: 1800/2352/2256MHz 4.74 92% 1% 90% 0% 0% 0% 56.4°C
23:18:15: 1800/2352/2256MHz 5.18 78% 1% 76% 0% 0% 0% 56.4°C
23:18:25: 1800/2352/2256MHz 5.84 85% 1% 84% 0% 0% 0% 57.3°C
23:18:35: 1800/2352/2256MHz 6.33 88% 0% 87% 0% 0% 0% 56.4°C
23:18:45: 1800/2352/2256MHz 6.81 85% 0% 84% 0% 0% 0% 56.4°C
23:18:56: 1800/2352/2256MHz 6.63 89% 1% 87% 0% 0% 0% 60.1°C
23:19:06: 1800/2352/2256MHz 6.85 78% 1% 76% 0% 0% 0% 59.2°C
23:19:16: 1800/2352/2256MHz 7.62 82% 1% 81% 0% 0% 0% 57.3°C
23:19:26: 1800/2352/2256MHz 7.51 90% 0% 89% 0% 0% 0% 57.3°C
23:19:37: 1800/2352/2256MHz 7.42 86% 0% 85% 0% 0% 0% 58.2°C
23:19:48: 1800/2352/2256MHz 7.74 88% 1% 86% 0% 0% 0% 61.0°C
23:19:58: 1800/2352/2256MHz 8.08 78% 2% 76% 0% 0% 0% 60.1°C

System health while running cpuminer:

Time cpu0/cpu4/cpu6 load %cpu %sys %usr %nice %io %irq Temp
23:20:16: 1800/2352/2256MHz 7.90 8% 0% 7% 0% 0% 0% 61.0°C
23:21:00: 1800/2352/2256MHz 8.52 100% 0% 99% 0% 0% 0% 61.9°C
23:21:44: 1800/2352/2256MHz 8.82 99% 0% 99% 0% 0% 0% 62.8°C
23:22:28: 1800/2352/2256MHz 8.96 100% 0% 99% 0% 0% 0% 63.8°C
23:23:13: 1800/2352/2256MHz 9.02 100% 0% 99% 0% 0% 0% 63.8°C
23:23:57: 1800/2352/2256MHz 9.05 100% 0% 99% 0% 0% 0% 64.7°C
23:24:42: 1800/2352/2256MHz 9.06 100% 0% 99% 0% 0% 0% 64.7°C

##########################################################################

dmesg output while running the benchmarks:

[ 3188.850626] perf: interrupt took too long (2516 > 2500), lowering kernel.perf_event_max_sample_rate to 79200
[ 3249.330530] perf: interrupt took too long (3150 > 3145), lowering kernel.perf_event_max_sample_rate to 63300

##########################################################################

Linux 5.10.160-rockchip (op) 2024年01月16日 _aarch64_ (8 CPU)

avg-cpu: %user %nice %system %iowait %steal %idle
15.12 0.04 0.50 0.02 0.00 84.31

Device tps kB_read/s kB_wrtn/s kB_dscd/s kB_read kB_wrtn kB_dscd
mmcblk0 9.47 255.86 244.85 0.00 925573 885730 0
nvme0n1 0.07 1.59 0.00 0.00 5760 0 0

total used free shared buff/cache available
Mem: 15Gi 918Mi 14Gi 8.0Mi 340Mi 14Gi
Swap: 11Gi 0B 11Gi

Filename Type Size Used Priority
/swapfile file 12582908 0 -2

CPU sysfs topology (clusters, cpufreq members, clockspeeds)
cpufreq min max
CPU cluster policy speed speed core type
0 0 0 408 1800 Cortex-A55 / r2p0
1 0 0 408 1800 Cortex-A55 / r2p0
2 0 0 408 1800 Cortex-A55 / r2p0
3 0 0 408 1800 Cortex-A55 / r2p0
4 1 4 408 2352 Cortex-A76 / r4p0
5 1 4 408 2352 Cortex-A76 / r4p0
6 2 6 408 2256 Cortex-A76 / r4p0
7 2 6 408 2256 Cortex-A76 / r4p0

Architecture: aarch64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Vendor ID: ARM
Model name: Cortex-A55
Model: 0
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
Stepping: r2p0
CPU max MHz: 1800.0000
CPU min MHz: 408.0000
BogoMIPS: 48.00
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
Model name: Cortex-A76
Model: 0
Thread(s) per core: 1
Core(s) per socket: 2
Socket(s): 2
Stepping: r4p0
CPU max MHz: 2352.0000
CPU min MHz: 408.0000
BogoMIPS: 48.00
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp
L1d cache: 384 KiB (8 instances)
L1i cache: 384 KiB (8 instances)
L2 cache: 2.5 MiB (8 instances)
L3 cache: 3 MiB (1 instance)
Vulnerability Itlb multihit: Not affected
Vulnerability L1tf: Not affected
Vulnerability Mds: Not affected
Vulnerability Meltdown: Not affected
Vulnerability Mmio stale data: Not affected
Vulnerability Retbleed: Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1: Mitigation; __user pointer sanitization
Vulnerability Spectre v2: Vulnerable: Unprivileged eBPF enabled
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort: Not affected

SoC guess: Rockchip RK3588 (35881000)
DMC gov: performance (2112 MHz)
DT compat: rockchip,rk3588-orangepi-5-plus
rockchip,rk3588
Compiler: /usr/bin/gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0 / aarch64-linux-gnu
Userland: arm64
Kernel: 5.10.160-rockchip/aarch64
CONFIG_HZ=300
CONFIG_HZ_300=y
CONFIG_PREEMPT_NOTIFIERS=y
CONFIG_PREEMPT_VOLUNTARY=y
cpu cpu0: leakage=13
cpu cpu0: pvtm=1438
cpu cpu0: pvtm-volt-sel=2
cpu cpu4: leakage=10
cpu cpu4: pvtm=1673
cpu cpu4: pvtm-volt-sel=3
cpu cpu6: leakage=11
cpu cpu6: pvtm=1694
cpu cpu6: pvtm-volt-sel=4
mali fb000000.gpu: leakage=19
rockchip-dmc dmc: leakage=39
rockchip-dmc dmc: leakage-volt-sel=1
RKNPU fdab0000.npu: leakage=10

##########################################################################

Kernel 5.10.160 is not latest 5.10.208 LTS that was released on 2024-01-15.

See https://endoflife.date/linux for details. It is somewhat likely that some
exploitable vulnerabilities exist for this kernel as well as many unfixed bugs.

But this version string doesn't matter since this is not an official LTS Linux
from kernel.org. This device runs a Rockchip vendor/BSP kernel.

This kernel is based on a mixture of Android GKI and other sources. Also some
community attempts to do version string cosmetics might have happened, see
https://tinyurl.com/2p8fuubd for example. To examine how far away this 5.10.160
is from an official LTS of same version someone would have to reapply Rockchip's
thousands of patches to a clean 5.10.160 LTS.

##########################################################################

cpu0/index0: 32K, level: 1, type: Data
cpu0/index1: 32K, level: 1, type: Instruction
cpu0/index2: 128K, level: 2, type: Unified
cpu0/index3: 3072K, level: 3, type: Unified
cpu1/index0: 32K, level: 1, type: Data
cpu1/index1: 32K, level: 1, type: Instruction
cpu1/index2: 128K, level: 2, type: Unified
cpu1/index3: 3072K, level: 3, type: Unified
cpu2/index0: 32K, level: 1, type: Data
cpu2/index1: 32K, level: 1, type: Instruction
cpu2/index2: 128K, level: 2, type: Unified
cpu2/index3: 3072K, level: 3, type: Unified
cpu3/index0: 32K, level: 1, type: Data
cpu3/index1: 32K, level: 1, type: Instruction
cpu3/index2: 128K, level: 2, type: Unified
cpu3/index3: 3072K, level: 3, type: Unified
cpu4/index0: 64K, level: 1, type: Data
cpu4/index1: 64K, level: 1, type: Instruction
cpu4/index2: 512K, level: 2, type: Unified
cpu4/index3: 3072K, level: 3, type: Unified
cpu5/index0: 64K, level: 1, type: Data
cpu5/index1: 64K, level: 1, type: Instruction
cpu5/index2: 512K, level: 2, type: Unified
cpu5/index3: 3072K, level: 3, type: Unified
cpu6/index0: 64K, level: 1, type: Data
cpu6/index1: 64K, level: 1, type: Instruction
cpu6/index2: 512K, level: 2, type: Unified
cpu6/index3: 3072K, level: 3, type: Unified
cpu7/index0: 64K, level: 1, type: Data
cpu7/index1: 64K, level: 1, type: Instruction
cpu7/index2: 512K, level: 2, type: Unified
cpu7/index3: 3072K, level: 3, type: Unified

##########################################################################

vdd_cpu_big0_s0: 1000 mV (1050 mV max)
vdd_cpu_big1_s0: 1000 mV (1050 mV max)
vdd_npu_s0: 812 mV (950 mV max)

cluster0-opp-table:
408 MHz 675.0 mV (00f9 ffff)
408 MHz 750.0 mV (0006 ffff)
600 MHz 675.0 mV (00f9 ffff)
600 MHz 750.0 mV (0006 ffff)
816 MHz 675.0 mV (00f9 ffff)
816 MHz 750.0 mV (0006 ffff)
1008 MHz 675.0 mV (00f9 ffff)
1008 MHz 750.0 mV (0006 ffff)
1200 MHz 712.5 mV (00f9 ffff)
1200 MHz 750.0 mV (0006 ffff)
1296 MHz 750.0 mV (0004 ffff)
1416 MHz 750.0 mV (0006 ffff)
1416 MHz 762.5 mV (00f9 ffff)
1608 MHz 850.0 mV (00f9 ffff)
1608 MHz 887.5 mV (0006 ffff)
1704 MHz 937.5 mV (0006 ffff)
1800 MHz 950.0 mV (00f9 ffff)

cluster1-opp-table:
408 MHz 675.0 mV (00f9 ffff)
408 MHz 750.0 mV (0006 ffff)
600 MHz 675.0 mV (00f9 ffff)
600 MHz 750.0 mV (0006 ffff)
816 MHz 675.0 mV (00f9 ffff)
816 MHz 750.0 mV (0006 ffff)
1008 MHz 675.0 mV (00f9 ffff)
1008 MHz 750.0 mV (0006 ffff)
1200 MHz 675.0 mV (00f9 ffff)
1200 MHz 750.0 mV (0006 ffff)
1416 MHz 725.0 mV (00f9 ffff)
1416 MHz 750.0 mV (0006 ffff)
1608 MHz 762.5 mV (00f9 ffff)
1608 MHz 787.5 mV (0006 ffff)
1800 MHz 850.0 mV (00f9 ffff)
1800 MHz 875.0 mV (0006 ffff)
2016 MHz 925.0 mV (00f9 ffff)
2016 MHz 950.0 mV (0006 ffff)
2208 MHz 987.5 mV (00f9 ffff)
2256 MHz 1000.0 mV (00f9 0013)
2304 MHz 1000.0 mV (00f9 0024)
2352 MHz 1000.0 mV (00f9 0048)
2400 MHz 1000.0 mV (00f9 0080)

cluster2-opp-table:
408 MHz 675.0 mV (00f9 ffff)
408 MHz 750.0 mV (0006 ffff)
600 MHz 675.0 mV (00f9 ffff)
600 MHz 750.0 mV (0006 ffff)
816 MHz 675.0 mV (00f9 ffff)
816 MHz 750.0 mV (0006 ffff)
1008 MHz 675.0 mV (00f9 ffff)
1008 MHz 750.0 mV (0006 ffff)
1200 MHz 675.0 mV (00f9 ffff)
1200 MHz 750.0 mV (0006 ffff)
1416 MHz 725.0 mV (00f9 ffff)
1416 MHz 750.0 mV (0006 ffff)
1608 MHz 762.5 mV (00f9 ffff)
1608 MHz 787.5 mV (0006 ffff)
1800 MHz 850.0 mV (00f9 ffff)
1800 MHz 875.0 mV (0006 ffff)
2016 MHz 925.0 mV (00f9 ffff)
2016 MHz 950.0 mV (0006 ffff)
2208 MHz 987.5 mV (00f9 ffff)
2256 MHz 1000.0 mV (00f9 0013)
2304 MHz 1000.0 mV (00f9 0024)
2352 MHz 1000.0 mV (00f9 0048)
2400 MHz 1000.0 mV (00f9 0080)

dmc-opp-table:
528 MHz 675.0 mV (00f9 ffff)
528 MHz 750.0 mV (0006 ffff)
1068 MHz 725.0 mV (00f9 ffff)
1068 MHz 750.0 mV (0006 ffff)
1560 MHz 800.0 mV (0006 ffff)
1560 MHz 800.0 mV (00f9 ffff)
2750 MHz 875.0 mV (0006 ffff)
2750 MHz 875.0 mV (00f9 ffff)

gpu-opp-table:
300 MHz 675.0 mV (00f9 ffff)
300 MHz 750.0 mV (0006 ffff)
400 MHz 675.0 mV (00f9 ffff)
400 MHz 750.0 mV (0006 ffff)
500 MHz 675.0 mV (00f9 ffff)
500 MHz 750.0 mV (0006 ffff)
600 MHz 675.0 mV (00f9 ffff)
600 MHz 750.0 mV (0006 ffff)
700 MHz 700.0 mV (00f9 ffff)
700 MHz 750.0 mV (0006 ffff)
800 MHz 750.0 mV (0002 ffff)
800 MHz 750.0 mV (00f9 ffff)
850 MHz 787.5 mV (0004 ffff)
900 MHz 800.0 mV (0002 ffff)
900 MHz 800.0 mV (00f9 ffff)
1000 MHz 850.0 mV (0002 ffff)
1000 MHz 850.0 mV (00f9 ffff)

npu-opp-table:
300 MHz 700.0 mV (00f9 ffff)
300 MHz 750.0 mV (0006 ffff)
400 MHz 700.0 mV (00f9 ffff)
400 MHz 750.0 mV (0006 ffff)
500 MHz 700.0 mV (00f9 ffff)
500 MHz 750.0 mV (0006 ffff)
600 MHz 700.0 mV (00f9 ffff)
600 MHz 750.0 mV (0006 ffff)
700 MHz 700.0 mV (00f9 ffff)
700 MHz 750.0 mV (0006 ffff)
800 MHz 750.0 mV (0006 ffff)
800 MHz 750.0 mV (00f9 ffff)
900 MHz 800.0 mV (00f9 ffff)
950 MHz 837.5 mV (0006 ffff)
1000 MHz 850.0 mV (00f9 ffff)

venc-opp-table:
800 MHz 750.0 mV

##########################################################################

Results validation:

* Advertised vs. measured max CPU clockspeed: -3.0% before, -4.0% after -> https://tinyurl.com/32w9rr94
* No swapping
* Background activity (%system) OK
* No throttling

Status of performance related governors found below /sys (w/o cpufreq):

* dmc: performance / 2112 MHz (rknpu_ondemand dmc_ondemand userspace powersave performance simple_ondemand / 528 1068 1560 2112)
* fb000000.gpu: performance / 1000 MHz (rknpu_ondemand dmc_ondemand userspace powersave performance simple_ondemand / 300 400 500 600 700 800 900 1000)
* fdab0000.npu: performance / 1000 MHz (rknpu_ondemand dmc_ondemand userspace powersave performance simple_ondemand / 300 400 500 600 700 800 900 1000)

Status of performance related policies found below /sys:

* /sys/devices/platform/fb000000.gpu/power_policy: [coarse_demand] always_on
* /sys/module/pcie_aspm/parameters/policy: default [performance] powersave powersupersave

| Orange Pi 5 Plus | ~2220 | 5.10 | Ubuntu 22.04.3 LTS arm64 | 16390 | 3117 | 1296400 | 12550 | 29740 | 23.95 | |

Wordpress，您好！

2024-04-01T12:45:55.000Z

博客从Typecho切换到Wordpress，这是我用Wordpress写的第一篇文章。

博客最开始使用Typecho使用Handsome主题，然后觉得服务器维护太贵了，于是将数据库里面的文章全部导出为Markdown文档，使用Hexo进行写作，部署在阿里云/腾讯云的cos搭配CDN访问，降低价格，但是之后又发现这样维护很困难，有时候想写点什么都要重新部署然后上传文件，期间我也开发了两款Hexo插件，之后又换回去了Typecho，之后觉得Typecho不好用，文章的数据结构和附件混在一起，很混乱，同时又接触到了Laravel于是用Laravel自己写了一个博客，并且申请了软件著作权，之后觉得太丑了又没有用，然后又用回Typecho了，然后Typecho感觉不更新了，后台也不好看，写文章也不方便，于是现在尝试去使用Wordpress使用Argon主题。

期间还尝试了很多博客，zblog，halo，hexo，firekylin，，等等都忘记了

Xen虚拟化服务器升级到Debian12 Bookworm网卡名称被更改

2024-04-01T07:58:00.000Z

eth0 -> enX0

UnPredictableNetworkInterfaceNames ‘fun’ with Bookworm domU: eth0 -> enX0 · Issue #65 · xen-tools/xen-tools (github.com)

新版本Nginx Openresty 替换http2为http2 on

2024-03-29T14:13:00.000Z

要在所有的 .conf 文件中将 listen 443 ssl http2; 替换为 listen 443 ssl; http on;，你可以使用 sed 命令。sed 是一个流编辑器，用于对输入流（或文件）进行基本的文本转换。

下面是一个简单的命令，它会递归地搜索当前目录及其子目录中的所有 .conf 文件，并替换指定的文本：

find . -type f -name "*.conf" -exec sed -i 's/listen 443 ssl http2;/listen 443 ssl;\n\thttp2 on;/g' {} +

这个命令的解释如下：

find . -type f -name "*.conf"：查找当前目录及其子目录中所有的 .conf 文件。
-exec ... {} +：对找到的每个文件执行指定的命令。{} 是一个占位符，代表当前正在处理的文件名。
sed -i 's/原字符串/新字符串/g'：使用 sed 进行文本替换。-i 选项表示直接修改文件内容，而不是输出到标准输出。s/原字符串/新字符串/g 是替换命令，其中 g 表示全局替换（即替换每一行中的所有匹配项）。

注意：这个命令假设你的 sed 版本支持 -i 选项的扩展用法（即使用 {} + 来一次性处理多个文件）。在某些系统上，你可能需要为 -i 选项提供一个备份文件扩展名，例如 -i.bak，这样 sed 会在修改文件之前创建一个备份。

另外，这个命令将 http2 on; 添加到新的一行，并添加了一个制表符（\t）进行缩进。如果你需要不同的缩进或格式，可以相应地调整 sed 命令中的字符串。

在执行这个命令之前，建议先备份你的 .conf 文件，以防万一出现不可预见的问题。

Postfix配置多用户中继服务器

2024-03-26T14:03:00.000Z

你

Postfix设置邮件中继：设置使用同一个relay smtp.a.com，user1@c.com使用a@a.com 密码为123456邮件账户，user2@c.com使用b@a.com密码为123456邮件账户

To set up Postfix to use the same relay server smtp.a.com for both user1@c.com and user2@c.com with different credentials, you can follow these steps:

Edit the Postfix main configuration file. This file is usually located at /etc/postfix/main.cf. Open it in a text editor.
Find or add the following configuration options to configure the relay server and authentication:

relayhost = smtp.a.com
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options = noanonymous
smtp_use_tls = yes

Create the /etc/postfix/sasl_passwd file if it doesn’t exist, and add the following lines:

smtp.a.com user1@c.com:a@a.com:123456
smtp.a.com user2@c.com:b@a.com:123456

Replace a@a.com with the username for user1@c.com, b@a.com with the username for user2@c.com, and 123456 with the corresponding passwords.

Run the following command to generate the hash database for the sasl_passwd file:

sudo postmap /etc/postfix/sasl_passwd

Reload or restart the Postfix service to apply the changes:

sudo systemctl reload postfix

With these configurations, Postfix should now relay emails for user1@c.com using the credentials a@a.com and the password 123456, and for user2@c.com using the credentials b@a.com and the password 123456.

MailCow添加Catch-All捕获所有邮件

2024-03-21T12:33:00.000Z

在MailCow中，没有在哪里有明确写Catch-All设置，于是我翻阅了Receive mails on a default email if recipient doesn’t exist · Issue #4563 · mailcow/mailcow-dockerized (github.com)发现了

翻译过来就是在右上角E-mail中的别名选项进行设置

添加@ioioi.cn，并设置一个邮箱进行发送，即可

Nextcloud去除分享页面中的"获取自己的免费账号"

2024-03-20T20:31:51.000Z

解决方法：

在配置文件中添加

'simpleSignUpLink.shown' => false,

之后这句话就被隐藏了

Nginx配置deny和allow ip还是被进行访问allow不生效的问题

2024-03-08T16:28:00.000Z

Nginx 设置 allow deny ip的时候遇到了执行顺序的问题

deny all
allow the_ip

保存上面的配置问候后，会发现不管如何访问都会403禁止访问

allow the_ip
deny all

只有当它们的顺序更换过来之后才正常

经过查阅Nginx相关资料，发现他对ip的匹配是：依次检查规则，直到找到第一个匹配项，所以all中间已经包含我的ip了，于是它就直接禁止，不进行下面的操作，跟一般的配置文件不太一样，一般的配置文件是后面的配置会覆盖前面的配置，所以在编辑Nginx配置文件的时候需要注意

Home Assistant 配置反向代理提示 400: Bad Request

2024-02-27T16:43:00.000Z

https://www.home-assistant.io/integrations/http/

就是要在configuration.yaml加入以下代码

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.30.33.0/24  # Add the IP address of the proxy server

复制代码

加完之后重启，问题解决。

修改service文件中pip源以解决Home-Assistant初始化慢的问题

2024-02-27T12:01:17.000Z

sudo systemctl edit home-assistant.service

添加

[Service]
Environment="HOME=/var/lib/hass"
Environment="PIP_INDEX_URL=https://pypi.tuna.tsinghua.edu.cn/simple"

保存后重启生效

云服务器安装Arch Linux

2024-02-21T20:01:00.000Z

云服务器安装Arch Linux – 森哥Dev (senge.dev)

云服务器厂商几乎不会提供Arch Linux系统的实例，需要按照以下安装教程自行安装
对服务器Linux发行版没有特别要求，但是不允许是Windows Server系统，如果是Windows，请自行重装为任意Linux发行版（建议Ubuntu或CentOS）
安装前请知道如何使用SSH连接，否则自行搜索
确保你在实体机或虚拟机中安装过Arch Linux，否则请勿安装
如果想把自己的服务器换成Arch，安装前请务必备份服务器的所有数据
服务器的运行内存必须在2GiB及以上，否则您只能使用vps2arch命令安装
安装后服务器将会变得不稳定，仅限学习交流使用，不建议将服务器运用在生产力环境中
安装完成后控制台界面会显示服务器系统为以前的系统，但是实际你的云服务器系统已经变成了Arch Linux
本教程不适用于虚拟主机，如果您正在使用虚拟主机，请勿参考本教程
由于以下原因造成的任何后果，本人不承担任何责任

如果你同意以上条款，请按照下方的步骤开始安装

检查服务器的内存和存储空间

输入以下命令检查服务器的硬盘和存储空间剩余大小

df -h

运行后的效果如下所示，确保根分区剩余空间大于3G且磁盘大小大于等于20G，否则请勿安装

Filesystem      Size  Used Avail Use% Mounted onudev            965M     0  965M   0% /devtmpfs           200M  8.9M  191M   5% /run/dev/vda1        40G   16G   22G  42% /tmpfs           997M   88K  997M   1% /dev/shmtmpfs           5.0M  4.0K  5.0M   1% /run/locktmpfs           997M     0  997M   0% /sys/fs/cgrouptmpfs           200M     0  200M   0% /run/user/0

输入以下命令检查服务器的内存

free -h

运行后的效果如下所示，确保内存大小至少为2G（不包括交换分区/虚拟内存），否则请勿安装

total        used        free      shared  buff/cache   availableMem:           1.9G        683M        269M         36M        1.0G        1.1GSwap:          1.0G        138M        886M

下载并初始化ArchLinux安装环境

根据服务器所在地初始化

根据服务器的地理位置选择合适的镜像站，请勿盲目选择清华/中科大源，假设你选择的镜像站点为https://mirror.xtom.com.hk，则你需要在该网站下载以下文件：

archlinux-x86_64.iso
archlinux-x86_64.iso.sig
sha256sums.txt

下载命令如下所示

curl -O https://mirror.xtom.com.hk/archlinux/iso/latest/archlinux-x86_64.isocurl -O https://mirror.xtom.com.hk/archlinux/iso/latest/archlinux-x86_64.iso.sigcurl -O https://mirror.xtom.com.hk/archlinux/iso/latest/sha256sums.txt

如果你不想使用xtom下载，请将https://mirror.xtom.com.hk换成你自己选择的镜像站点，如：https://mirrors.aliyun.com，后面的无需更换，因为几乎所有的镜像站都是这个地址。

验证下载的镜像

sha256验证（必要）

sha256sum -c sha256sums.txt

gpg验证（建议，更严格的文件完整性验证）

gpg --list-keysgpg --keyserver-options auto-key-retrieve --verify archlinux-x86_64.iso.sig

保证验证没问题后再安装系统

挂载iso并复制到根目录

mount -o loop,ro archlinux-x86_64.iso /mntcp -r /mnt/* /umount /mnt/e2label /dev/vda1 archiso

进入VNC界面，同时通过ssh重启服务器

根据服务商的不同，进入服务器的VNC界面，然后通过ssh重启服务器。

重启后通过复制命令输入来向服务器输入命令（博主使用的是华为云的服务器）。

配置Grub，进入archiso

按C进入Grub命令行界面，然后根据以下命令查找archiso路径，并配置initramfs、linux内核等

ls /     # 列出根目录的所有文件如果能看到arch，则可以继续安装

配置Linux内核

linux /arch/boot/x86_64/vmlinuz-linux archisobasedir=arch archisolabel=archiso copytoram

配置initramfs

initrd /arch/boot/x86_64/initramfs-linux.img

启动archiso

boot

如果你看到了Welcome to Arch Linux字样，那么恭喜你，你可以根据Arch Wiki或本博客的ArchLinux安装教程来继续安装Arch Linux了！

开启sshd，并使用计算机ssh连接

开启sshd

systemctl start sshd

重置密码

passwd

使用实体计算机连接

ssh root@ip

如果遇到连接失败，请先删除用户目录下的.ssh目录忘记连接，也可以使用XShell（Windows）或Final Shell客户端连接

使用vps2arch一键安装

部分VPS云服务器厂商只提供了ssh连接的入口，未提供vnc连接入口，这些云服务器厂商必须使用vps2arch来进行切换

切换后，你的磁盘分区表不会被设置，如果你的服务器未使用uefi，你可以直接安装，如果使用了uefi，请谨慎使用该脚本。

安装前务必备份你的所有重要数据，安装可能会导致系统无法启动

运行以下命令一键安装

不要着急运行脚本，请先自行修改脚本，建议注释掉和reflector有关的代码，并添加一些你需要的软件包（例如：vim，git等）

wget https://felixc.at/vps2archchmod +x vps2arch

修改后，你可以进行安装，可能会报错

如果你没有设置root密码，则密码会被更改为vps2arch，如果你已经设置了root密码，则你需要先尝试使用之前的root密码登陆，如果无法登陆，请使用vps2arch作为root密码登陆。

解决HE Tunnel Broker ipv6掉线问题

2024-02-20T14:19:00.000Z

解决HE Tunnel Broker ipv6掉线问题

使用IPV6隧道的时候遇到客户端ping的时候经常显示超时

当在服务器中ping其他地址之后又全部正常

ipv6掉线问题临时解决方案（已验证可行），添加一条定时任务，每分钟ping网关或者外部ipv6地址，

懒人一键操作（这是一条命令，一次性执行）

(crontab -l 2>/dev/null; echo "# ipv6保活，建议不要删除"; echo "* * * * * /bin/ping -c 1 2400:3200::1") | crontab -

别忘了启动cron服务！！！

如果还不通可执行

ip -6 neigh flush all

这时应该就恢复了，如果没恢复，重启一次服务器即可

参考：公告信息 - 鸡仔云 (bigchick.xyz)

阿里云服务器完全卸载AliYun监控教程

2024-02-20T04:39:00.000Z

卸载AliYunDun

wget http://update.aegis.aliyun.com/download/uninstall.sh
chmod +x uninstall.sh
./uninstall.sh
wget http://update.aegis.aliyun.com/download/quartz_uninstall.sh
chmod +x quartz_uninstall.sh
./quartz_uninstall.sh

删除AliYunDun残留

pkill aliyun-service
rm -fr /etc/init.d/agentwatch /usr/sbin/aliyun-service
rm -rf /usr/local/aegis*

修改Docker-compose使Uptime-Kuma支持IPV6

2024-02-19T09:20:00.000Z

之前部署了一个Uptime-Kuma用来监控服务的运行，最近，在监控IPV6网络的时候出现了一点问题，Docker不支持IPV6网络：

解决方案：

修改/etc/docker/daemon.json文件

{
        "experimental": true,
        "fixed-cidr-v6": "fd80::/64",
        "ip6tables": true,
        "ipv6": true
}

修改docker-compose.yml

version: '3.8'

services:
  uptime-kuma:
    image: louislam/uptime-kuma:1
    container_name: uptime-kuma
    volumes:
      - ./uptime-kuma:/app/data
      - /var/run/docker.sock:/var/run/docker.sock
    ports:
      - "25003:3001"  # <Host Port>:<Container Port>
    restart: always
    networks:
      - uptime-kuma-network

networks:
  uptime-kuma-network:
    driver: bridge
    enable_ipv6: true
    ipam:
      driver: default
      config:
        - subnet: "fd00:1234:5678::/64"

重新新建了一个IPV6的网络，这样就可以避免使用host模式了

在容器里面运行ping

成功！

恢复Uptime-Kuma监控

成功！

Archlinux ARM WARNING: errors were encountered during the build. The image may not be complete

2024-02-18T09:09:34.000Z

Archlinux ARM更新内核时候出现问题，mkinitcpio -P发现任然有这个问题

==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-linux.img'
==> WARNING: errors were encountered during the build. The image may not be complete.`

把/etc/mkinitcpio.conf改了就行，删掉kms，就好了

#HOOKS=(base udev autodetect modconf kms keyboard keymap consolefont block filesystems fsck)
HOOKS=(base udev autodetect modconf keyboard keymap consolefont block filesystems fsck)

BUG:https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/issues/218
mkinitcpio exits with 1 when using the kms hook on hardware without any privacy screens.

编译Mariadb11.2.2提示Could NOT find Curses (missing: CURSES_LIBRARY CURSES_INCLUDE_PATH)

2024-01-14T12:23:05.000Z

sudo apt install libncurses-dev

编译PHP8.3出现checking if iconv supports errno... no

2024-01-14T11:31:14.000Z

原来的：

./configure --enable-static

把原来的libiconv卸载并且重新设置成下面这样的新的参数

./configure --enable-static --prefix=/usr/local/libiconv

然后就可以正常编译PHP了

修复Windows11搜索框卡死问题/关闭Windows 11网络搜索

2023-11-09T14:11:15.000Z

1.首先，我们在搜索框中输入注册表。在Windows搜索结果中直接开启注册表功能;

　　2.接着，我们在注册表中输入一下路径：计算机\HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Explorer，然后我没们用右键单击Windows选项，接着选中新建选项;

　　3.然后我们新建一个名为Explorer的项，按下回车键确认;

　　4.接下来我们右键新建立的Explorer的项，再新建一个DWORD(32位)值;

　　5.然后我们再将新建的值命名为DisableSearchBoxSuggestions，接着按下回车键。这时我们就可以控制是否开关网络搜索啦;

　　6.到这时，我没如果要关闭Win11的网络搜索就很简单。双击刚才的DisableSearchBoxSuggestions值，然后将其赋值为“1”即可;

　　7.接着保存注册表，重启电脑，这时候我们就会发现现在已经没有网络搜索的结果了。

参考：!CNblogs Akarinnnn

使用nextcloud提示：数据库被用于事务文件锁。为了增强性能，请设置memcache

2023-10-04T22:43:00.000Z

没有开启redis拓展

Archlinux开启redis扩展需要同时开启igbinary拓展，不然会如下图报错，无法使用

Archlinux php -m 提示 redis undefined symbol: igbinary_serialize

2023-10-04T14:45:00.000Z

Archlinux开启redis扩展需要同时开启igbinary拓展，不然会如下图报错，无法使用

Nextcloud通过客户端DAV上传100M+大文件时报500错

2023-10-01T22:06:00.000Z

一直更改php nginx上传文件大小限制、上传超时时间设置，但是改了也没有任何效果

发现后台日志报错：

Declaration of Aws\HashingStream::seek($offset, $whence = Aws\SEEK_SET) must be compatible with Psr\Http\Message\StreamInterface::seek(int $offset, int $whence = Psr\Http\Message\SEEK_SET): void at /data/wwwroot/cloud.ioioi.cn/nextcloud/3rdparty/aws/aws-sdk-php/src/HashingStream.php#50

通过Bing搜索，查询到nextcloud issues 39981

发现是camerarawpreviews引起的，于是，禁用并卸载了此应用，后正常

使用uptime-kuma提示node-pre-gyp: Permission denied

2023-10-01T17:03:29.000Z

npm ERR! code 126
npm ERR! path /data/wwwroot/monitor.ioioi.cn/uptime-kuma/node_modules/@louislam/sqlite3
npm ERR! command failed
npm ERR! command sh -c node-pre-gyp install --fallback-to-build
npm ERR! sh: line 1: /data/wwwroot/monitor.ioioi.cn/uptime-kuma/node_modules/.bin/node-pre-gyp: Permission denied

网上查找资料说是权限没有给够，于是使用root用户进行运行，发现还是会报错。还有的说要加**--unsafe-perm **参数，发现加了之后还是报错

全局安装 node-gyp 还是报错

最后通过Uptime-kuma issues 2606，查询到可能是安装sqlite3的包的时候会出问题

但是当时作者也没有给具体的解决方案

之后我又通过查询，找到了其他的类似案例mediacenterjs issues 191 # npm install : “node-pre-gyp: Permission denied” and sqlite3
其中dvergeylen提示到，需要

npm install -g node-pre-gyp

于是在执行这个操作之后这个问题解决了

Archlinux使用nvm提示tput: unknown terminal "xterm-256color"

2023-10-01T16:51:02.000Z

在网上找了好多，说的什么修改终端类型，还有说安装ncurses包之类的，全都尝试了没有用

最后经过查找这篇文章：weixin_34024034，发现了解决方案：

经过测试在安装好的Archlinux中的TERMINFO默认为空

在/etc/profile添加TERMINFO全局变量即可

export TERMINFO=/usr/share/terminfo

debian解决系列问题

2023-09-10T01:14:00.000Z

debian解决 Could NOT find LZ4 (missing: LZ4_LIBRARIES LZ4_INCLUDE_DIRS) (Required is at least version “1.6”)

你可以尝试使用以下命令安装LZ4库：

sudo apt-get install liblz4-dev

如果已经安装了该库，你可以尝试更新一下系统的软件包列表：

sudo apt-get update

如果问题仍然存在，你可以尝试手动安装LZ4库并将其添加到LD_LIBRARY_PATH环境变量中。具体步骤如下：

下载LZ4库的源代码：https://github.com/lz4/lz4/releases
解压源代码并进入解压后的目录。
编译并安装LZ4库：

make
sudo make install

将LZ4库的路径添加到LD_LIBRARY_PATH环境变量中：

export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH

重新运行你的程序，看看问题是否已经解决。

debian解决Could NOT find LZO (missing: LZO_LIBRARIES LZO_INCLUDE_DIRS)

你可以尝试安装lzo库和头文件，使用以下命令：

sudo apt-get install liblzo2-dev

如果已经安装了lzo库和头文件，你可以尝试更新库缓存，使用以下命令：

sudo ldconfig

debian解决Could NOT find Snappy (missing: SNAPPY_LIBRARIES SNAPPY_INCLUDE_DIRS)

你可以尝试安装snappy库和头文件，使用以下命令：

sudo apt-get install libsnappy-dev

如果已经安装了snappy库和头文件，你可以尝试重新运行CMake，并确保它能够找到正确的库和头文件路径。

CDN访问Forward Loop Detect错误解决

2023-09-10T01:12:14.000Z

一般的CDN平台都会有回源跟随301、302功能

开启后，节点回源请求若返回 301、302 状态码，则直接跳转获取资源，不会返回 301、302 给用户。

关掉它问题就解决了！

浅分析

源站301链接
给cdn开启这个功能之后
cdn不会返回301给用户
自己跳转获取资源
当链接有301之后没返回给用户跳转
cdn直接获取的链接还是301的链接
导致了一个环路
这个过程循环！导致的问题！

转载自小王总博客

从Git中删除你的敏感数据密码

2023-09-10T01:07:00.000Z

要从Git提交历史中删除敏感数据（如build.gradle文件），可以使用以下步骤：

确保你有一个备份，以防意外删除了重要数据。确保在进行任何更改之前，你已经创建了一个完整的备份。
在本地克隆你的Git存储库，如果还没有克隆的话。
使用git filter-branch命令来重写提交历史并删除build.gradle文件。在终端中导航到你的存储库所在的目录，并运行以下命令：

git filter-branch --tree-filter 'rm -f build.gradle' -- --all

这将遍历所有提交，并在每个提交中删除build.gradle文件。

运行命令后，Git会重写提交历史。这可能需要一些时间，具体取决于你的存储库的大小和提交数量。
删除本地存储库中的旧引用：

git for-each-ref --format='delete %(refname)' refs/original | git update-ref --stdin

强制推送重写后的提交历史到远程存储库：

git push --force origin

这将覆盖远程存储库中的提交历史，请确保你已经做好了备份，并且只对自己的存储库进行此操作。

请注意，这些操作将修改存储库的提交历史，并且如果其他人已经克隆了存储库，他们可能会遇到问题。因此，在执行此操作之前，请确保与团队中的其他人员进行适当的沟通，并确保每个人都了解并同意这个更改。

docker容器内部访问宿主机MySQL服务

2023-09-03T15:23:59.000Z

在宿主机中查看docker0网卡的ip地址，即为mysql服务器的地址

注意ufw需要放行ip加端口，不然会造成无法访问（这是这个折磨了我好久）

172.21.0.0/24为你的容器ip段

ufw allow from 172.21.0.0/24 to any port 3306

同时还需要在数据库phpmyadmin里面添加对应用户的登陆权限

为Luatos-ESP32-C3-Core（经典版）编译安装CircuitPython

2023-08-10T10:58:19.000Z

最近在淘宝上面购买了一个Luatos ESP32 C3 Core 带 ch343 芯片的一块开发板：想刷个micropython发现刷进去之后无法连接到串口之后看见在circuitpython上面有人发过这个板子的固件，于是刷个circuitpython，发现还是失败最后找了一圈才发现这个板子分为两个版本，也就是在淘宝上面的12.9元的和9.9元的版本，一个带usb转串口ch343芯片一个不带，本来以为他们两个之间差别不大，于是就买了12.9的图省事，想直接连type-c，结果才发现掉进了大坑。现在给大家分享一下如何为Luatos-ESP32-C3-Core（经典版）编译安装CircuitPython 编译环境： Windows Wsl Archlinux

安装git和python环境

yay -S git
yay -S python-pip
pip install --upgrade -r requirements-dev.txt
pip install --upgrade -r requirements-doc.txt

拉取8.2版本

git clone -b 8.2.x https://github.com/adafruit/circuitpython.git

拉取子模块

不需要拉取全部模块，大样子太大了，只需要拉取esp方面的模块即可

cd ports/espressif
make fetch-port-submodules

编译mpy-cross

cd ../..
make -C mpy-cross

安装ESP-IDF

如果上一步能够顺利拉下来的话，在ports/espressif下会有esp-idf目录

cd ports/espressif/esp-idf
./install.sh

上一步会有报错的

1、libusb

需要安装libusb软件包安装完后，需要初始化ESP编译环境

. export.sh

开始编译

由于**8.2.x版本的CircuitPython**暂时没有这个型号的开发板，于是在 Github 中找到上周提交的文件，将上面的文件夹手动复制到板子目录中

cd ports/espressif
make BOARD=luatos_core_esp32c3_ch343 V=2 -j17

V=2开启日志显示、-j17使用多线程编译然后就是等，我用的11代i7的CPU编译整整4个小时

编译报错解决

1、cmake

安装cmake

2、glibc

安装glibc

3、gcc

安装gcc

4、ninja

安装ninja

编译完成

进入ports/espressif/build-luatos_core_esp32c3_ch343/目录将firmware.bin从0x0000开始刷写，即可成功

结束

已经将luatos_core_esp32c3_ch343板子的文件以及编译好的固件上传至我的Github

参考： CSDN-applebomb CircuitPython-Docs

Podman 设置普通非Root用户

2023-06-22T20:07:00.000Z

root@super:/home/wwwroot/pw.xyz.blue# sudo -u www podman-compose up
['podman', '--version', '']
using podman version: 4.3.1
** excluding:  set()
['podman', 'network', 'exists', 'pwxyzblue_default']
WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available 
WARN[0000] For using systemd, you may need to login using an user session 
WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1003` (possibly as root) 
WARN[0000] Falling back to --cgroup-manager=cgroupfs  
WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available 
WARN[0000] For using systemd, you may need to login using an user session 
WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1003` (possibly as root) 
WARN[0000] Falling back to --cgroup-manager=cgroupfs  
podman create --name=bitwarden --label io.podman.compose.config-hash=123 --label io.podman.compose.project=pwxyzblue --label io.podman.compose.version=0.0.1 --label com.docker.compose.project=pwxyzblue --label com.docker.compose.project.working_dir=/home/wwwroot/pw.xyz.blue --label com.docker.compose.project.config_files=docker-compose.yml --label com.docker.compose.container-number=1 --label com.docker.compose.service=bitwarden --env-file /home/wwwroot/pw.xyz.blue/config.env -v /home/wwwroot/pw.xyz.blue/data:/data --net pwxyzblue_default --network-alias bitwarden -p 37594:80 --restart always vaultwarden/server:alpine
WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available 
WARN[0000] For using systemd, you may need to login using an user session 
WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1003` (possibly as root) 
WARN[0000] Falling back to --cgroup-manager=cgroupfs  
WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available 
WARN[0000] For using systemd, you may need to login using an user session 
WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1003` (possibly as root) 
WARN[0000] Falling back to --cgroup-manager=cgroupfs  
Error: creating container storage: the container name "bitwarden" is already in use by 12db721b020e96050076bd002d32e6fbb07807d1be46f59c9b9de4d8bb5315aa. You have to remove that container to be able to reuse that name: that name is already in use
exit code: 125
podman start -a bitwarden
WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available 
WARN[0000] For using systemd, you may need to login using an user session 
WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1003` (possibly as root) 
WARN[0000] Falling back to --cgroup-manager=cgroupfs  
WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available 
WARN[0000] For using systemd, you may need to login using an user session 
WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1003` (possibly as root) 
WARN[0000] Falling back to --cgroup-manager=cgroupfs  
ERRO[0000] failed to move the rootless netns slirp4netns process to the systemd user.slice: exec: "dbus-launch": executable file not found in $PATH 
Failed to connect to bus: No such file or directory
ERRO[0000] Unable to clean up network for container 12db721b020e96050076bd002d32e6fbb07807d1be46f59c9b9de4d8bb5315aa: "tearing down network namespace configuration for container 12db721b020e96050076bd002d32e6fbb07807d1be46f59c9b9de4d8bb5315aa: netavark: IO error: aardvark pid not found" 
Error: unable to start container 12db721b020e96050076bd002d32e6fbb07807d1be46f59c9b9de4d8bb5315aa: crun: sd-bus call: Permission denied: Permission denied: OCI permission denied
exit code: 125

loginctl enable-linger 1003

Nextcloud Nginx配置文件

2023-06-08T12:55:12.000Z

# Set the `immutable` cache control options only for assets with a cache busting `v` argument
map $arg_v $asset_immutable {
    "" "";
    default "immutable";
}
server
{
    listen 80;
        listen 443 ssl http2;
    server_name cloud.xyz.blue;
    index index.php index.html index.htm default.php default.htm default.html;
    root /www/wwwroot/cloud.xyz.blue/nextcloud;

    #SSL-START SSL相关配置，请勿删除或修改下一行带注释的404规则
    #error_page 404/404.html;
    #HTTP_TO_HTTPS_START
    if ($server_port !~ 443){
        rewrite ^(/.*)$ https://$host$1 permanent;
    }
    #HTTP_TO_HTTPS_END
    ssl_certificate    /www/server/panel/vhost/cert/cloud.xyz.blue/fullchain.pem;
    ssl_certificate_key    /www/server/panel/vhost/cert/cloud.xyz.blue/privkey.pem;
    ssl_protocols TLSv1.1 TLSv1.2 TLSv1.3;
    ssl_ciphers EECDH+CHACHA20:EECDH+CHACHA20-draft:EECDH+AES128:RSA+AES128:EECDH+AES256:RSA+AES256:EECDH+3DES:RSA+3DES:!MD5;
    ssl_prefer_server_ciphers on;
    ssl_session_cache shared:SSL:10m;
    ssl_session_timeout 10m;
    add_header Strict-Transport-Security "max-age=31536000";
    error_page 497  https://$host$request_uri;
        #SSL-END

    #ERROR-PAGE-START  错误页配置，可以注释、删除或修改
    #error_page 404 /404.html;
    #error_page 502 /502.html;
    #ERROR-PAGE-END

    #PHP-INFO-START  PHP引用配置，可以注释或修改
    #清理缓存规则

    location ~ /purge(/.*) {
        proxy_cache_purge cache_one $host$1$is_args$args;
        #access_log  /www/wwwlogs/cloud.xyz.blue_purge_cache.log;
    }
    #引用反向代理规则，注释后配置的反向代理将无效
    include /www/server/panel/vhost/nginx/proxy/cloud.xyz.blue/*.conf;

    include enable-php-81.conf;
    #PHP-INFO-END

    #REWRITE-START URL重写规则引用,修改后将导致面板设置的伪静态规则失效
    include /www/server/panel/vhost/rewrite/cloud.xyz.blue.conf;
    #REWRITE-END

    #禁止访问的文件或目录
    location ~ ^/(\.user.ini|\.htaccess|\.git|\.env|\.svn|\.project|LICENSE|README.md)
    {
        return 404;
    }

    #一键申请SSL证书验证目录相关设置
    location ~ \.well-known{
        allow all;
    }

    #禁止在证书验证目录放入敏感文件
    if ( $uri ~ "^/\.well-known/.*\.(php|jsp|py|js|css|lua|ts|go|zip|tar\.gz|rar|7z|sql|bak)$" ) {
        return 403;
    }

    access_log  /www/wwwlogs/cloud.xyz.blue.log;
    error_log  /www/wwwlogs/cloud.xyz.blue.error.log;
    #Nextcloud 配置
    # Prevent nginx HTTP Server Detection
    server_tokens off;

    # HSTS settings
    # WARNING: Only add the preload option once you read about
    # the consequences in https://hstspreload.org/. This option
    # will add the domain to a hardcoded list that is shipped
    # in all major browsers and getting removed from this list
    # could take several months.
    #add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload" always;

    # set max upload size and increase upload timeout:
    client_max_body_size 512M;
    client_body_timeout 300s;
    fastcgi_buffers 64 4K;

    # Enable gzip but do not remove ETag headers
    gzip on;
    gzip_vary on;
    gzip_comp_level 4;
    gzip_min_length 256;
    gzip_proxied expired no-cache no-store private no_last_modified no_etag auth;
    gzip_types application/atom+xml application/javascript application/json application/ld+json application/manifest+json application/rss+xml application/vnd.geo+json application/vnd.ms-fontobject application/wasm application/x-font-ttf application/x-web-app-manifest+json application/xhtml+xml application/xml font/opentype image/bmp image/svg+xml image/x-icon text/cache-manifest text/css text/plain text/vcard text/vnd.rim.location.xloc text/vtt text/x-component text/x-cross-domain-policy;

    # Pagespeed is not supported by Nextcloud, so if your server is built
    # with the `ngx_pagespeed` module, uncomment this line to disable it.
    #pagespeed off;

    # The settings allows you to optimize the HTTP2 bandwitdth.
    # See https://blog.cloudflare.com/delivering-http-2-upload-speed-improvements/
    # for tunning hints
    client_body_buffer_size 512k;

    # HTTP response headers borrowed from Nextcloud `.htaccess`
    # add_header Referrer-Policy                   "no-referrer"       always;
    # add_header X-Content-Type-Options            "nosniff"           always;
    add_header X-Download-Options                "noopen"            always;
    # add_header X-Frame-Options                   "SAMEORIGIN"        always;
    # add_header X-Permitted-Cross-Domain-Policies "none"              always;
    # add_header X-Robots-Tag                      "noindex, nofollow" always;
    # add_header X-XSS-Protection                  "1; mode=block"     always;

    # Remove X-Powered-By, which is an information leak
    fastcgi_hide_header X-Powered-By;

    # Specify how to handle directories -- specifying `/index.php$request_uri`
    # here as the fallback means that Nginx always exhibits the desired behaviour
    # when a client requests a path that corresponds to a directory that exists
    # on the server. In particular, if that directory contains an index.php file,
    # that file is correctly served; if it doesn't, then the request is passed to
    # the front-end controller. This consistent behaviour means that we don't need
    # to specify custom rules for certain paths (e.g. images and other assets,
    # `/updater`, `/ocm-provider`, `/ocs-provider`), and thus
    # `try_files $uri $uri/ /index.php$request_uri`
    # always provides the desired behaviour.
    index index.php index.html /index.php$request_uri;

    # Rule borrowed from `.htaccess` to handle Microsoft DAV clients
    location = / {
        if ( $http_user_agent ~ ^DavClnt ) {
            return 302 /remote.php/webdav/$is_args$args;
        }
    }

    location = /robots.txt {
        allow all;
        log_not_found off;
        access_log off;
    }

    # Make a regex exception for `/.well-known` so that clients can still
    # access it despite the existence of the regex rule
    # `location ~ /(\.|autotest|...)` which would otherwise handle requests
    # for `/.well-known`.
    location ^~ /.well-known {
        # The rules in this block are an adaptation of the rules
        # in `.htaccess` that concern `/.well-known`.

        location = /.well-known/carddav { return 301 /remote.php/dav/; }
        location = /.well-known/caldav  { return 301 /remote.php/dav/; }

        location /.well-known/acme-challenge    { try_files $uri $uri/ =404; }
        location /.well-known/pki-validation    { try_files $uri $uri/ =404; }

        # Let Nextcloud's API for `/.well-known` URIs handle all other
        # requests by passing them to the front-end controller.
        return 301 /index.php$request_uri;
    }

    # Rules borrowed from `.htaccess` to hide certain paths from clients
    location ~ ^/(?:build|tests|config|lib|3rdparty|templates|data)(?:$|/)  { return 404; }
    location ~ ^/(?:\.|autotest|occ|issue|indie|db_|console)                { return 404; }

    # Ensure this block, which passes PHP files to the PHP process, is above the blocks
    # which handle static assets (as seen below). If this block is not declared first,
    # then Nginx will encounter an infinite rewriting loop when it prepends `/index.php`
    # to the URI, resulting in a HTTP 500 error response.
    location ~ \.php(?:$|/) {
        # Required for legacy support
        rewrite ^/(?!index|remote|public|cron|core\/ajax\/update|status|ocs\/v[12]|updater\/.+|oc[ms]-provider\/.+|.+\/richdocumentscode\/proxy) /index.php$request_uri;

        fastcgi_split_path_info ^(.+?\.php)(/.*)$;
        set $path_info $fastcgi_path_info;

        try_files $fastcgi_script_name =404;

        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        fastcgi_param PATH_INFO $path_info;
        fastcgi_param HTTPS on;

        fastcgi_param modHeadersAvailable true;         # Avoid sending the security headers twice
        fastcgi_param front_controller_active true;     # Enable pretty urls
        fastcgi_pass unix:/tmp/php-cgi-81.sock;

        fastcgi_intercept_errors on;
        fastcgi_request_buffering off;

        fastcgi_max_temp_file_size 0;
    }

    location ~ \.(?:css|js|svg|gif|png|jpg|ico|wasm|tflite|map)$ {
        try_files $uri /index.php$request_uri;
        add_header Cache-Control "public, max-age=15778463, $asset_immutable";
        access_log off;     # Optional: Don't log access to assets

        location ~ \.wasm$ {
            default_type application/wasm;
        }
    }

    location ~ \.woff2?$ {
        try_files $uri /index.php$request_uri;
        expires 7d;         # Cache-Control policy borrowed from `.htaccess`
        access_log off;     # Optional: Don't log access to assets
    }

    # Rule borrowed from `.htaccess`
    location /remote {
        return 301 /remote.php$request_uri;
    }

    location / {
        try_files $uri $uri/ /index.php$request_uri;
    }
}

Debian 解决错误：“configure: error: GNU MP Library version 4.2 or greater required.”

2023-06-07T11:29:52.000Z

apt install libgmp-dev

socketio

2023-05-12T12:05:00.000Z

很抱歉，我无法为您提供完整的代码，因为这需要根据您的具体需求和环境进行编写。但是，我可以为您提供一些参考代码和示例，帮助您开始构建您的应用程序。

首先，您需要安装相关的依赖：

npm install express react react-dom react-router-dom socket.io

然后，您可以按照以下步骤来构建您的应用程序：

创建一个Node.js应用程序，并使用Express框架来管理路由和中间件。

const express = require('express');
const app = express();

// 中间件
app.use(express.static('public'));

// 路由
app.get('/', (req, res) => {
  // 渲染页面
});

// 启动服务器
const server = app.listen(3000, () => {
  console.log('Server is running on port 3000');
});

在Node.js应用程序中使用React来构建您的前端界面，并使用React Router来管理路由。

import React from 'react';
import ReactDOM from 'react-dom';
import { BrowserRouter as Router, Route, Switch } from 'react-router-dom';

import Home from './pages/Home';
import About from './pages/About';

ReactDOM.render(
  <Router>
    <Switch>
      <Route exact path="/" component={Home} />
      <Route path="/about" component={About} />
    </Switch>
  </Router>,
  document.getElementById('root')
);

使用Socket.io来实现实时通信功能，并在服务器端和客户端之间建立双向通信。

const io = require('socket.io')(server);

io.on('connection', (socket) => {
  console.log('A user connected');

  socket.on('disconnect', () => {
    console.log('A user disconnected');
  });
});

import io from 'socket.io-client';

const socket = io('http://localhost:3000');

socket.on('connect', () => {
  console.log('Connected to server');
});

socket.on('disconnect', () => {
  console.log('Disconnected from server');
});

在服务器端使用Node.js的模板引擎来渲染您的页面，并将渲染后的HTML发送给客户端。

const ejs = require('ejs');

app.set('view engine', 'ejs');

app.get('/', (req, res) => {
  const data = {
    title: 'My Website',
    message: 'Welcome to my website!'
  };

  res.render('index', data);
});

在客户端使用React来渲染您的页面，并使用Socket.io来实时更新数据。

import React, { useState, useEffect } from 'react';

import io from 'socket.io-client';

const socket = io('http://localhost:3000');

const Home = () => {
  const [data, setData] = useState([]);

  useEffect(() => {
    socket.on('data', (data) => {
      setData(data);
    });
  }, []);

  return (
    <div>
      {data.map((item) => (
        <div key={item.id}>{item.name}</div>
      ))}
    </div>
  );
};

export default Home;

在服务器端使用Node.js来处理数据，并将数据发送给客户端。

const data = [
  { id: 1, name: 'Alice' },
  { id: 2, name: 'Bob' },
  { id: 3, name: 'Charlie' }
];

io.on('connection', (socket) => {
  socket.emit('data', data);
});

在客户端使用React来实时更新您的数据，并使用Socket.io来实现实时排名功能。

import React, { useState, useEffect } from 'react';

import io from 'socket.io-client';

const socket = io('http://localhost:3000');

const Home = () => {
  const [data, setData] = useState([]);

  useEffect(() => {
    socket.on('data', (data) => {
      setData(data);
    });
  }, []);

  return (
    <div>
      {data
        .sort((a, b) => b.score - a.score)
        .map((item) => (
          <div key={item.id}>
            {item.name} - {item.score}
          </div>
        ))}
    </div>
  );
};

export default Home;

以上是一个简单的示例代码，您可以根据您的具体需求进行调整和优化。

Can't access PWA settings because "This page has been blocked by Microsoft Edge"

2023-05-10T20:06:00.000Z

I am trying to change my PWA settings, but when pressing on settings button in PWA or going to edge://app-settings, it’s saying, that “app-settings is blocked” “This page has been blocked by Microsoft Edge” “ERR_BLOCKED_BY_CLIENT”. Can’t really understand why edge blocking it’s pages lmao. Btw my privacy settings are set to Balanced. yeah I am getting that too, installed a new PWA from Twitter to test edge://app-settings/jgeocpdicgmkeemopbanhokmhcgcflmi is the URL it gives me (the second part is the PWA hash i think) edit: found the fix!!!!!!!!!!!! GO TO edge://apps/all https://i.vgy.me/s4ODA0.png - screenshot tap LINK HANDLING FOR WINDOWS then it started working for me

Can’t access PWA settings because “This page has been blocked by Microsoft Edge” : r/edge (reddit.com)

编译Mariadb10.11 报 troff: fatal error: can't find macro file m

2023-05-09T13:35:00.000Z

troff: fatal error: can't find macro file m
[ 37%] Built target user_t
Scanning dependencies of target mariadb
troff: fatal error: can't find macro file m
[ 37%] Built target user_ps

安装groff即可

apt install groff

mysql常见错误

2023-05-09T12:08:00.000Z

Download mysql source
Ran the following cmake command based on the documentation

cmake \
  -DCMAKE_INSTALL_PREFIX=/usr/local/mac-dev-env/mysql-5.7.18 \
  -DCMAKE_CXX_FLAGS="-stdlib=libstdc++" \
  -DDEFAULT_CHARSET=utf8 \
  -DDEFAULT_COLLATION=utf8_general_ci \
  -DDOWNLOAD_BOOST=ON \
  -DWITH_BOOST=/usr/local/src/boost \
  ..

cmake \
  -DCMAKE_INSTALL_PREFIX=./mysql-5.7.18 \
  -DCMAKE_CXX_FLAGS="-stdlib=libstdc++" \
  -DDEFAULT_CHARSET=utf8 \
  -DDEFAULT_COLLATION=utf8_general_ci \
  -DDOWNLOAD_BOOST=1 \
  ..

gives the following error

CMake Error at cmake/boost.cmake:81 (MESSAGE):
You can download it with -DDOWNLOAD_BOOST=1 -DWITH_BOOST=<directory>

following https://geeksww.com/tutorials/operating_systems/linux/installation/installing_mysql_client_tools_binaries_and_library_on_ubuntu_linux.php

./configure.cmake --without-server --enable-thread-safe-client \
    --with-client-ldflags=-all-static --prefix=./mybuild \
    --without-debug  --without-docs --with-big-tables

this didn’t work

Building boost

http://www.boost.org/doc/libs/1_65_0/more/getting_started/unix-variants.html#prepare-to-use-a-boost-library-binary

download boost and untar

mkdir mybuild
./bootstrap.sh --prefix=mybuild/
./b2

building taking time
create folder mybuild inside mysql source
folder so that cmake files are in that folder and it’s easy to delete
the tmp files. Also put the entire src in git to see if the original src
folder gets new files.

cmake \
  -DCMAKE_INSTALL_PREFIX= ./mysql-5.7.18\
  -DCMAKE_CXX_FLAGS="-stdlib=libstdc++" \
  -DDEFAULT_CHARSET=utf8 \
  -DDEFAULT_COLLATION=utf8_general_ci \
  -DDOWNLOAD_BOOST=ON \
  -DWITH_BOOST=../../boost_1_65_0.tar.gz \
  ..

gives error -- MySQL currently requires boost_1_59_0

cmake \
  -DCMAKE_INSTALL_PREFIX= ./mysql-5.7.18\
  -DCMAKE_CXX_FLAGS="-stdlib=libstdc++" \
  -DDEFAULT_CHARSET=utf8 \
  -DDEFAULT_COLLATION=utf8_general_ci \
  -DDOWNLOAD_BOOST=ON \
  -DWITH_BOOST=../../ \
  ..

this tried to download boost but later got timeout error
downloaded boost package wget http://sourceforge.net/projects/boost/files/boost/1.59.0/boost_1_59_0.tar.gz

cmake \
  -DCMAKE_INSTALL_PREFIX= ./mysql-5.7.18\
  -DCMAKE_CXX_FLAGS="-stdlib=libstdc++" \
  -DDEFAULT_CHARSET=utf8 \
  -DDEFAULT_COLLATION=utf8_general_ci \
  -DDOWNLOAD_BOOST=ON \
  -DWITH_BOOST=../../ \
  ..

the cmake is running ok
make to build the exe
got this error /Users/anjesh/Dev/source/mysql-5.7.19/mysys/charset.c:403:22: error: use of undeclared identifier 'DEFAULT_CHARSET_HOME'
Found the bug reported here https://bugs.mysql.com/bug.php?id=78214
not sure how to fix
looks like this error might be due to space after PREFIX= , something that’s mentioned in above command

cmake \
  -DCMAKE_INSTALL_PREFIX=./mysql-5.7.18 \
  -DCMAKE_CXX_FLAGS="-stdlib=libstdc++" \
  -DDEFAULT_CHARSET=utf8 \
  -DDEFAULT_COLLATION=utf8_general_ci \
  -DDOWNLOAD_BOOST=ON \
  -DWITH_BOOST=../../ \
  ..

make

still cann’t compile Mysql-python becauase of some .h file folder issues.
again runnnig cmake and make with some change in the prefix

cmake \
  -DCMAKE_INSTALL_PREFIX=./ \
  -DCMAKE_CXX_FLAGS="-stdlib=libstdc++" \
  -DDEFAULT_CHARSET=utf8 \
  -DDEFAULT_COLLATION=utf8_general_ci \
  -DDOWNLOAD_BOOST=ON \
  -DWITH_BOOST=../../ \
  ..

make

make install without sudo and the necessary files are installed in the same folder

Now i was able to install MySQL-Python after configuring mysql_config, i put mysql_config in ~/bin and the installation worked.

https://gist.github.com/anjesh/d35fac0d5b85a0d71fb04d72e1c7925c

Typecho使用腾讯云CDN后台卡在登录页无法登录解决

2023-05-09T12:08:00.000Z

Typecho使用腾讯云CDN后台卡在登录页无法登录解决

现象

后台登录时，即使密码正确也会跳回后台登录页，重试依旧，陷入死循环

后台登录页

解决

到腾讯CDN后台，把回源跟随301/302配置关掉。

位置在回源配置 > 回源跟随301/302配置

回源跟随301/302配置

原因

猜测

登录成功后Typecho会返回一个302请求，以及成功后的Cookie之类的凭证，浏览器带着这个Cookie之类的凭证进行302转跳就能进入后台。

开启CDN的302回源后，CDN不会按照302返回的请求设置新的、成功登录的Cookie，而是带着旧的、为成功登录的Cookie访问Typecho，Typecho看到未登录得Cookie就返回了登录页给CDN，CDN再把这个登录页返回给用户。
导致登录一直卡在登录页，因为CDN没有用302返回的新的Cookie去进行请求。

其他问题

如果还是无法登录，可以看看缓存键规则配置里的忽略参数有没有设置成不忽略

缓存键规则配置

Gitea 默认配置文件分享

2023-05-07T09:15:00.000Z

来源：Archlinux Packages

; This file lists the default values used by Gitea
;; Copy required sections to your own app.ini (default is custom/conf/app.ini)
;; and modify as needed.
;; Do not copy the whole file as-is, as it contains some invalid sections for illustrative purposes.
;; If you don't know what a setting is you should not set it.
;;
;; see https://docs.gitea.io/en-us/config-cheat-sheet/ for additional documentation.


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; General Settings
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; App name that shows in every page title
APP_NAME = ; Gitea: Git with a cup of tea
;;
;; RUN_USER will automatically detect the current user - but you can set it here change it if you run locally
RUN_USER = ; git
;;
;; Application run mode, affects performance and debugging. Either "dev", "prod" or "test", default is "prod"
RUN_MODE = ; prod

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
[server]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; The protocol the server listens on. One of 'http', 'https', 'unix' or 'fcgi'. Defaults to 'http'
;PROTOCOL = http
;;
;; Expect PROXY protocol headers on connections
;USE_PROXY_PROTOCOL = false
;;
;; Use PROXY protocol in TLS Bridging mode
;PROXY_PROTOCOL_TLS_BRIDGING = false
;;
; Timeout to wait for PROXY protocol header (set to 0 to have no timeout)
;PROXY_PROTOCOL_HEADER_TIMEOUT=5s
;;
; Accept PROXY protocol headers with UNKNOWN type
;PROXY_PROTOCOL_ACCEPT_UNKNOWN=false
;;
;; Set the domain for the server
;DOMAIN = localhost
;;
;; Overwrite the automatically generated public URL. Necessary for proxies and docker.
;ROOT_URL = %(PROTOCOL)s://%(DOMAIN)s:%(HTTP_PORT)s/
;;
;; when STATIC_URL_PREFIX is empty it will follow ROOT_URL
;STATIC_URL_PREFIX =
;;
;; The address to listen on. Either a IPv4/IPv6 address or the path to a unix socket.
;HTTP_ADDR = 0.0.0.0
;;
;; The port to listen on. Leave empty when using a unix socket.
;HTTP_PORT = 3000
;;
;; If REDIRECT_OTHER_PORT is true, and PROTOCOL is set to https an http server
;; will be started on PORT_TO_REDIRECT and it will redirect plain, non-secure http requests to the main
;; ROOT_URL.  Defaults are false for REDIRECT_OTHER_PORT and 80 for
;; PORT_TO_REDIRECT.
;REDIRECT_OTHER_PORT = false
;PORT_TO_REDIRECT = 80
;;
;; expect PROXY protocol header on connections to https redirector.
;REDIRECTOR_USE_PROXY_PROTOCOL = %(USE_PROXY_PROTOCOL)
;; Minimum and maximum supported TLS versions
;SSL_MIN_VERSION=TLSv1.2
;SSL_MAX_VERSION=
;;
;; SSL Curve Preferences
;SSL_CURVE_PREFERENCES=X25519,P256
;;
;; SSL Cipher Suites
;SSL_CIPHER_SUITES=; Will default to "ecdhe_ecdsa_with_aes_256_gcm_sha384,ecdhe_rsa_with_aes_256_gcm_sha384,ecdhe_ecdsa_with_aes_128_gcm_sha256,ecdhe_rsa_with_aes_128_gcm_sha256,ecdhe_ecdsa_with_chacha20_poly1305,ecdhe_rsa_with_chacha20_poly1305" if aes is supported by hardware, otherwise chacha will be first.
;;
;; Timeout for any write to the connection. (Set to -1 to disable all timeouts.)
;PER_WRITE_TIMEOUT = 30s
;;
;; Timeout per Kb written to connections.
;PER_WRITE_PER_KB_TIMEOUT = 30s
;;
;; Permission for unix socket
;UNIX_SOCKET_PERMISSION = 666
;;
;; Local (DMZ) URL for Gitea workers (such as SSH update) accessing web service.
;; In most cases you do not need to change the default value.
;; Alter it only if your SSH server node is not the same as HTTP node.
;; Do not set this variable if PROTOCOL is set to 'unix'.
;LOCAL_ROOT_URL = %(PROTOCOL)s://%(HTTP_ADDR)s:%(HTTP_PORT)s/
;;
;; When making local connections pass the PROXY protocol header.
;LOCAL_USE_PROXY_PROTOCOL = %(USE_PROXY_PROTOCOL)
;;
;; Disable SSH feature when not available
;DISABLE_SSH = false
;;
;; Whether to use the builtin SSH server or not.
;START_SSH_SERVER = false
;;
;; Expect PROXY protocol header on connections to the built-in SSH server
;SSH_SERVER_USE_PROXY_PROTOCOL = false
;;
;; Username to use for the builtin SSH server. If blank, then it is the value of RUN_USER.
;BUILTIN_SSH_SERVER_USER = %(RUN_USER)s
;;
;; Domain name to be exposed in clone URL
;SSH_DOMAIN = %(DOMAIN)s
;;
;; SSH username displayed in clone URLs.
;SSH_USER = %(BUILTIN_SSH_SERVER_USER)s
;;
;; The network interface the builtin SSH server should listen on
;SSH_LISTEN_HOST =
;;
;; Port number to be exposed in clone URL
;SSH_PORT = 22
;;
;; The port number the builtin SSH server should listen on
;SSH_LISTEN_PORT = %(SSH_PORT)s
;;
;; Root path of SSH directory, default is '~/.ssh', but you have to use '/home/git/.ssh'.
;SSH_ROOT_PATH =
;;
;; Gitea will create a authorized_keys file by default when it is not using the internal ssh server
;; If you intend to use the AuthorizedKeysCommand functionality then you should turn this off.
;SSH_CREATE_AUTHORIZED_KEYS_FILE = true
;;
;; Gitea will create a authorized_principals file by default when it is not using the internal ssh server
;; If you intend to use the AuthorizedPrincipalsCommand functionality then you should turn this off.
;SSH_CREATE_AUTHORIZED_PRINCIPALS_FILE = true
;;
;; For the built-in SSH server, choose the ciphers to support for SSH connections,
;; for system SSH this setting has no effect
;SSH_SERVER_CIPHERS = chacha20-poly1305@openssh.com, aes128-ctr, aes192-ctr, aes256-ctr, aes128-gcm@openssh.com, aes256-gcm@openssh.com
;;
;; For the built-in SSH server, choose the key exchange algorithms to support for SSH connections,
;; for system SSH this setting has no effect
;SSH_SERVER_KEY_EXCHANGES = curve25519-sha256, ecdh-sha2-nistp256, ecdh-sha2-nistp384, ecdh-sha2-nistp521, diffie-hellman-group14-sha256, diffie-hellman-group14-sha1
;;
;; For the built-in SSH server, choose the MACs to support for SSH connections,
;; for system SSH this setting has no effect
;SSH_SERVER_MACS = hmac-sha2-256-etm@openssh.com, hmac-sha2-256, hmac-sha1
;;
;; For the built-in SSH server, choose the keypair to offer as the host key
;; The private key should be at SSH_SERVER_HOST_KEY and the public SSH_SERVER_HOST_KEY.pub
;; relative paths are made absolute relative to the APP_DATA_PATH
;SSH_SERVER_HOST_KEYS=ssh/gitea.rsa, ssh/gogs.rsa
;;
;; Directory to create temporary files in when testing public keys using ssh-keygen,
;; default is the system temporary directory.
;SSH_KEY_TEST_PATH =
;;
;; Path to ssh-keygen, default is 'ssh-keygen' which means the shell is responsible for finding out which one to call.
;SSH_KEYGEN_PATH = ssh-keygen
;;
;; Enable SSH Authorized Key Backup when rewriting all keys, default is true
;SSH_AUTHORIZED_KEYS_BACKUP = true
;;
;; Determines which principals to allow
;; - empty: if SSH_TRUSTED_USER_CA_KEYS is empty this will default to off, otherwise will default to email, username.
;; - off: Do not allow authorized principals
;; - email: the principal must match the user's email
;; - username: the principal must match the user's username
;; - anything: there will be no checking on the content of the principal
;SSH_AUTHORIZED_PRINCIPALS_ALLOW = email, username
;;
;; Enable SSH Authorized Principals Backup when rewriting all keys, default is true
;SSH_AUTHORIZED_PRINCIPALS_BACKUP = true
;;
;; Specifies the public keys of certificate authorities that are trusted to sign user certificates for authentication.
;; Multiple keys should be comma separated.
;; E.g."ssh-<algorithm> <key>". or "ssh-<algorithm> <key1>, ssh-<algorithm> <key2>".
;; For more information see "TrustedUserCAKeys" in the sshd config manpages.
;SSH_TRUSTED_USER_CA_KEYS =
;; Absolute path of the `TrustedUserCaKeys` file gitea will manage.
;; Default this `RUN_USER`/.ssh/gitea-trusted-user-ca-keys.pem
;; If you're running your own ssh server and you want to use the gitea managed file you'll also need to modify your
;; sshd_config to point to this file. The official docker image will automatically work without further configuration.
;SSH_TRUSTED_USER_CA_KEYS_FILENAME =
;;
;; Enable exposure of SSH clone URL to anonymous visitors, default is false
;SSH_EXPOSE_ANONYMOUS = false
;;
;; Timeout for any write to ssh connections. (Set to -1 to disable all timeouts.)
;; Will default to the PER_WRITE_TIMEOUT.
;SSH_PER_WRITE_TIMEOUT = 30s
;;
;; Timeout per Kb written to ssh connections.
;; Will default to the PER_WRITE_PER_KB_TIMEOUT.
;SSH_PER_WRITE_PER_KB_TIMEOUT = 30s
;;
;; Indicate whether to check minimum key size with corresponding type
;MINIMUM_KEY_SIZE_CHECK = false
;;
;; Disable CDN even in "prod" mode
;OFFLINE_MODE = false
;DISABLE_ROUTER_LOG = false
;;
;; TLS Settings: Either ACME or manual
;; (Other common TLS configuration are found before)
;ENABLE_ACME = false
;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; ACME automatic TLS settings
;;
;; ACME directory URL (e.g. LetsEncrypt's staging/testing URL: https://acme-staging-v02.api.letsencrypt.org/directory)
;; Leave empty to default to LetsEncrypt's (production) URL
;ACME_URL =
;;
;; Explicitly accept the ACME's TOS. The specific TOS cannot be retrieved at the moment.
;ACME_ACCEPTTOS = false
;;
;; If the ACME CA is not in your system's CA trust chain, it can be manually added here
;ACME_CA_ROOT =
;;
;; Email used for the ACME registration service
;; Can be left blank to initialize at first run and use the cached value
;ACME_EMAIL =
;;
;; ACME live directory (not to be confused with ACME directory URL: ACME_URL)
;; (Refer to caddy's ACME manager https://github.com/caddyserver/certmagic)
;ACME_DIRECTORY = https
;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;;  Manual TLS settings: (Only applicable if ENABLE_ACME=false)
;;
;; Generate steps:
;; $ ./gitea cert -ca=true -duration=8760h0m0s -host=myhost.example.com
;;
;; Or from a .pfx file exported from the Windows certificate store (do
;; not forget to export the private key):
;; $ openssl pkcs12 -in cert.pfx -out cert.pem -nokeys
;; $ openssl pkcs12 -in cert.pfx -out key.pem -nocerts -nodes
;; Paths are relative to CUSTOM_PATH
;CERT_FILE = https/cert.pem
;KEY_FILE = https/key.pem
;;
;; Root directory containing templates and static files.
;; default is the path where Gitea is executed
;STATIC_ROOT_PATH =
;;
;; Default path for App data
;APP_DATA_PATH = data
;;
;; Enable gzip compression for runtime-generated content, static resources excluded
;ENABLE_GZIP = false
;;
;; Application profiling (memory and cpu)
;; For "web" command it listens on localhost:6060
;; For "serve" command it dumps to disk at PPROF_DATA_PATH as (cpuprofile|memprofile)_<username>_<temporary id>
;ENABLE_PPROF = false
;;
;; PPROF_DATA_PATH, use an absolute path when you start gitea as service
;PPROF_DATA_PATH = data/tmp/pprof
;;
;; Landing page, can be "home", "explore", "organizations", "login", or any URL such as "/org/repo" or even "https://anotherwebsite.com"
;; The "login" choice is not a security measure but just a UI flow change, use REQUIRE_SIGNIN_VIEW to force users to log in.
;LANDING_PAGE = home
;;
;; Enables git-lfs support. true or false, default is false.
;LFS_START_SERVER = false
;;
;;
;; LFS authentication secret, change this yourself
LFS_JWT_SECRET =
;;
;; LFS authentication validity period (in time.Duration), pushes taking longer than this may fail.
;LFS_HTTP_AUTH_EXPIRY = 20m
;;
;; Maximum allowed LFS file size in bytes (Set to 0 for no limit).
;LFS_MAX_FILE_SIZE = 0
;;
;; Maximum number of locks returned per page
;LFS_LOCKS_PAGING_NUM = 50
;;
;; Allow graceful restarts using SIGHUP to fork
;ALLOW_GRACEFUL_RESTARTS = true
;;
;; After a restart the parent will finish ongoing requests before
;; shutting down. Force shutdown if this process takes longer than this delay.
;; set to a negative value to disable
;GRACEFUL_HAMMER_TIME = 60s
;;
;; Allows the setting of a startup timeout and waithint for Windows as SVC service
;; 0 disables this.
;STARTUP_TIMEOUT = 0
;;
;; Static resources, includes resources on custom/, public/ and all uploaded avatars web browser cache time. Note that this cache is disabled when RUN_MODE is "dev". Default is 6h
;STATIC_CACHE_TIME = 6h

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
[database]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Database to use. Either "mysql", "postgres", "mssql" or "sqlite3".
;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; MySQL Configuration
;;
DB_TYPE = mysql
HOST = 127.0.0.1:3306 ; can use socket e.g. /var/run/mysqld/mysqld.sock
NAME = gitea
USER = root
;PASSWD = ;Use PASSWD = `your password` for quoting if you use special characters in the password.
;SSL_MODE = false ; either "false" (default), "true", or "skip-verify"
;CHARSET = utf8mb4 ;either "utf8" or "utf8mb4", default is "utf8mb4".
;;
;; NOTICE: for "utf8mb4" you must use MySQL InnoDB > 5.6. Gitea is unable to check this.
;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Postgres Configuration
;;
;DB_TYPE = postgres
;HOST = 127.0.0.1:5432 ; can use socket e.g. /var/run/postgresql/
;NAME = gitea
;USER = root
;PASSWD =
;SCHEMA =
;SSL_MODE=disable ;either "disable" (default), "require", or "verify-full"
;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; SQLite Configuration
;;
;DB_TYPE = sqlite3
;PATH= ; defaults to data/gitea.db
;SQLITE_TIMEOUT = ; Query timeout defaults to: 500
;SQLITE_JOURNAL_MODE = ; defaults to sqlite database default (often DELETE), can be used to enable WAL mode. https://www.sqlite.org/pragma.html#pragma_journal_mode
;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; MSSQL Configuration
;;
;DB_TYPE = mssql
;HOST = 172.17.0.2:1433
;NAME = gitea
;USER = SA
;PASSWD = MwantsaSecurePassword1
;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Other settings
;;
;; For iterate buffer, default is 50
;ITERATE_BUFFER_SIZE = 50
;;
;; Show the database generated SQL
LOG_SQL = false ; if unset defaults to true
;;
;; Maximum number of DB Connect retries
;DB_RETRIES = 10
;;
;; Backoff time per DB retry (time.Duration)
;DB_RETRY_BACKOFF = 3s
;;
;; Max idle database connections on connection pool, default is 2
;MAX_IDLE_CONNS = 2
;;
;; Database connection max life time, default is 0 or 3s mysql (See #6804 & #7071 for reasoning)
;CONN_MAX_LIFETIME = 3s
;;
;; Database maximum number of open connections, default is 0 meaning no maximum
;MAX_OPEN_CONNS = 0

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
[security]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Whether the installer is disabled (set to true to disable the installer)
INSTALL_LOCK = false
;;
;; Global secret key that will be used
;; This key is VERY IMPORTANT. If you lose it, the data encrypted by it (like 2FA secret) can't be decrypted anymore.
SECRET_KEY =
;;
;; Alternative location to specify secret key, instead of this file; you cannot specify both this and SECRET_KEY, and must pick one
;; This key is VERY IMPORTANT. If you lose it, the data encrypted by it (like 2FA secret) can't be decrypted anymore.
;SECRET_KEY_URI = file:/etc/gitea/secret_key
;;
;; Secret used to validate communication within Gitea binary.
INTERNAL_TOKEN=
;;
;; Alternative location to specify internal token, instead of this file; you cannot specify both this and INTERNAL_TOKEN, and must pick one
;INTERNAL_TOKEN_URI = file:/etc/gitea/internal_token
;;
;; How long to remember that a user is logged in before requiring relogin (in days)
;LOGIN_REMEMBER_DAYS = 7
;;
;; Name of the cookie used to store the current username.
;COOKIE_USERNAME = gitea_awesome
;;
;; Name of cookie used to store authentication information.
;COOKIE_REMEMBER_NAME = gitea_incredible
;;
;; Reverse proxy authentication header name of user name, email, and full name
;REVERSE_PROXY_AUTHENTICATION_USER = X-WEBAUTH-USER
;REVERSE_PROXY_AUTHENTICATION_EMAIL = X-WEBAUTH-EMAIL
;REVERSE_PROXY_AUTHENTICATION_FULL_NAME = X-WEBAUTH-FULLNAME
;;
;; Interpret X-Forwarded-For header or the X-Real-IP header and set this as the remote IP for the request
;REVERSE_PROXY_LIMIT = 1
;;
;; List of IP addresses and networks separated by comma of trusted proxy servers. Use `*` to trust all.
;REVERSE_PROXY_TRUSTED_PROXIES = 127.0.0.0/8,::1/128
;;
;; The minimum password length for new Users
;MIN_PASSWORD_LENGTH = 6
;;
;; Set to true to allow users to import local server paths
;IMPORT_LOCAL_PATHS = false
;;
;; Set to false to allow users with git hook privileges to create custom git hooks.
;; Custom git hooks can be used to perform arbitrary code execution on the host operating system.
;; This enables the users to access and modify this config file and the Gitea database and interrupt the Gitea service.
;; By modifying the Gitea database, users can gain Gitea administrator privileges.
;; It also enables them to access other resources available to the user on the operating system that is running the Gitea instance and perform arbitrary actions in the name of the Gitea OS user.
;; WARNING: This maybe harmful to you website or your operating system.
;; WARNING: Setting this to true does not change existing hooks in git repos; adjust it before if necessary.
;DISABLE_GIT_HOOKS = true
;;
;; Set to true to disable webhooks feature.
;DISABLE_WEBHOOKS = false
;;
;; Set to false to allow pushes to gitea repositories despite having an incomplete environment - NOT RECOMMENDED
;ONLY_ALLOW_PUSH_IF_GITEA_ENVIRONMENT_SET = true
;;
;;Comma separated list of character classes required to pass minimum complexity.
;;If left empty or no valid values are specified, the default is off (no checking)
;;Classes include "lower,upper,digit,spec"
;PASSWORD_COMPLEXITY = off
;;
;; Password Hash algorithm, either "argon2", "pbkdf2", "scrypt" or "bcrypt"
;PASSWORD_HASH_ALGO = pbkdf2
;;
;; Set false to allow JavaScript to read CSRF cookie
;CSRF_COOKIE_HTTP_ONLY = true
;;
;; Validate against https://haveibeenpwned.com/Passwords to see if a password has been exposed
;PASSWORD_CHECK_PWN = false
;;
;; Cache successful token hashes. API tokens are stored in the DB as pbkdf2 hashes however, this means that there is a potentially significant hashing load when there are multiple API operations.
;; This cache will store the successfully hashed tokens in a LRU cache as a balance between performance and security.
;SUCCESSFUL_TOKENS_CACHE_SIZE = 20

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
[camo]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; At the moment we only support images
;;
;; if the camo is enabled
;ENABLED = false
;; url to a camo image proxy, it **is required** if camo is enabled.
;SERVER_URL =
;; HMAC to encode urls with, it **is required** if camo is enabled.
;HMAC_KEY =
;; Set to true to use camo for https too lese only non https urls are proxyed
;ALLWAYS = false

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
[oauth2]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Enables OAuth2 provider
ENABLE = true
;;
;; Algorithm used to sign OAuth2 tokens. Valid values: HS256, HS384, HS512, RS256, RS384, RS512, ES256, ES384, ES512, EdDSA
;JWT_SIGNING_ALGORITHM = RS256
;;
;; Private key file path used to sign OAuth2 tokens. The path is relative to APP_DATA_PATH.
;; This setting is only needed if JWT_SIGNING_ALGORITHM is set to RS256, RS384, RS512, ES256, ES384 or ES512.
;; The file must contain a RSA or ECDSA private key in the PKCS8 format. If no key exists a 4096 bit key will be created for you.
;JWT_SIGNING_PRIVATE_KEY_FILE = jwt/private.pem
;;
;; OAuth2 authentication secret for access and refresh tokens, change this yourself to a unique string. CLI generate option is helpful in this case. https://docs.gitea.io/en-us/command-line/#generate
;; This setting is only needed if JWT_SIGNING_ALGORITHM is set to HS256, HS384 or HS512.
;JWT_SECRET =
;;
;; Lifetime of an OAuth2 access token in seconds
;ACCESS_TOKEN_EXPIRATION_TIME = 3600
;;
;; Lifetime of an OAuth2 refresh token in hours
;REFRESH_TOKEN_EXPIRATION_TIME = 730
;;
;; Check if refresh token got already used
;INVALIDATE_REFRESH_TOKENS = false
;;
;; Maximum length of oauth2 token/cookie stored on server
;MAX_TOKEN_LENGTH = 32767

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
[log]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Root path for the log files - defaults to %(GITEA_WORK_DIR)/log
;ROOT_PATH =
;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Main Logger
;;
;; Either "console", "file", "conn", "smtp" or "database", default is "console"
;; Use comma to separate multiple modes, e.g. "console, file"
MODE = console
;;
;; Either "Trace", "Debug", "Info", "Warn", "Error", "Critical" or "None", default is "Info"
LEVEL = Info
;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Router Logger
;;
;; Switch off the router log
;DISABLE_ROUTER_LOG=false
;;
;; Set the log "modes" for the router log (if file is set the log file will default to router.log)
ROUTER = console
;;
;; The router will log different things at different levels.
;;
;; * started messages will be logged at TRACE level
;; * polling/completed routers will be logged at INFO
;; * slow routers will be logged at WARN
;; * failed routers will be logged at WARN
;;
;; The routing level will default to that of the system but individual router level can be set in
;; [log.<mode>.router] LEVEL
;;

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Access Logger (Creates log in NCSA common log format)
;;
;ENABLE_ACCESS_LOG = false
;;
;; Set the log "modes" for the access log (if file is set the log file will default to access.log)
;ACCESS = file
;;
;; Sets the template used to create the access log.
;ACCESS_LOG_TEMPLATE = {{.Ctx.RemoteAddr}} - {{.Identity}} {{.Start.Format "[02/Jan/2006:15:04:05 -0700]" }} "{{.Ctx.Req.Method}} {{.Ctx.Req.URL.RequestURI}} {{.Ctx.Req.Proto}}" {{.ResponseWriter.Status}} {{.ResponseWriter.Size}} "{{.Ctx.Req.Referer}}\" \"{{.Ctx.Req.UserAgent}}"
;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; SSH log (Creates log from ssh git request)
;;
;ENABLE_SSH_LOG = false
;;
;; Other Settings
;;
;; Print Stacktraces with logs. (Rarely helpful.) Either "Trace", "Debug", "Info", "Warn", "Error", "Critical", default is "None"
;STACKTRACE_LEVEL = None
;;
;; Buffer length of the channel, keep it as it is if you don't know what it is.
;BUFFER_LEN = 10000

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Creating specific log configuration
;;
;; You can set specific configuration for individual modes and subloggers
;;
;; Configuration available to all log modes/subloggers
;LEVEL=
;FLAGS = stdflags
;EXPRESSION =
;PREFIX =
;COLORIZE = false
;;
;; For "console" mode only
;STDERR = false
;;
;; For "file" mode only
;LEVEL =
;; Set the file_name for the logger. If this is a relative path this
;; will be relative to ROOT_PATH
;FILE_NAME =
;; This enables automated log rotate(switch of following options), default is true
;LOG_ROTATE = true
;; Max size shift of a single file, default is 28 means 1 << 28, 256MB
;MAX_SIZE_SHIFT = 28
;; Segment log daily, default is true
;DAILY_ROTATE = true
;; delete the log file after n days, default is 7
;MAX_DAYS = 7
;; compress logs with gzip
;COMPRESS = true
;; compression level see godoc for compress/gzip
;COMPRESSION_LEVEL = -1
;
;; For "conn" mode only
;LEVEL =
;; Reconnect host for every single message, default is false
;RECONNECT_ON_MSG = false
;; Try to reconnect when connection is lost, default is false
;RECONNECT = false
;; Either "tcp", "unix" or "udp", default is "tcp"
;PROTOCOL = tcp
;; Host address
;ADDR =
;
;; For "smtp" mode only
;LEVEL =
;; Name displayed in mail title, default is "Diagnostic message from server"
;SUBJECT = Diagnostic message from server
;; Mail server
;HOST =
;; Mailer user name and password
;USER =
;; Use PASSWD = `your password` for quoting if you use special characters in the password.
;PASSWD =
;; Receivers, can be one or more, e.g. 1@example.com,2@example.com
;RECEIVERS =

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
[git]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; The path of git executable. If empty, Gitea searches through the PATH environment.
;PATH =
;;
;; The HOME directory for Git
;HOME_PATH = %(APP_DATA_PATH)/home
;;
;; Disables highlight of added and removed changes
;DISABLE_DIFF_HIGHLIGHT = false
;;
;; Max number of lines allowed in a single file in diff view
;MAX_GIT_DIFF_LINES = 1000
;;
;; Max number of allowed characters in a line in diff view
;MAX_GIT_DIFF_LINE_CHARACTERS = 5000
;;
;; Max number of files shown in diff view
;MAX_GIT_DIFF_FILES = 100
;;
;; Set the default commits range size
;COMMITS_RANGE_SIZE = 50
;;
;; Set the default branches range size
;BRANCHES_RANGE_SIZE = 20
;;
;; Arguments for command 'git gc', e.g. "--aggressive --auto"
;; see more on http://git-scm.com/docs/git-gc/
;GC_ARGS =
;;
;; If use git wire protocol version 2 when git version >= 2.18, default is true, set to false when you always want git wire protocol version 1
;; To enable this for Git over SSH when using a OpenSSH server, add `AcceptEnv GIT_PROTOCOL` to your sshd_config file.
;ENABLE_AUTO_GIT_WIRE_PROTOCOL = true
;;
;; Respond to pushes to a non-default branch with a URL for creating a Pull Request (if the repository has them enabled)
;PULL_REQUEST_PUSH_MESSAGE = true
;;
;; (Go-Git only) Don't cache objects greater than this in memory. (Set to 0 to disable.)
;LARGE_OBJECT_THRESHOLD = 1048576
;; Set to true to forcibly set core.protectNTFS=false
;DISABLE_CORE_PROTECT_NTFS=false
;; Disable the usage of using partial clones for git.
;DISABLE_PARTIAL_CLONE = false

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
[service]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Time limit to confirm account/email registration
;ACTIVE_CODE_LIVE_MINUTES = 180
;;
;; Time limit to perform the reset of a forgotten password
;RESET_PASSWD_CODE_LIVE_MINUTES = 180
;;
;; Whether a new user needs to confirm their email when registering.
;REGISTER_EMAIL_CONFIRM = false
;;
;; Whether a new user needs to be confirmed manually after registration. (Requires `REGISTER_EMAIL_CONFIRM` to be disabled.)
;REGISTER_MANUAL_CONFIRM = false
;;
;; List of domain names that are allowed to be used to register on a Gitea instance
;; gitea.io,example.com
;EMAIL_DOMAIN_WHITELIST =
;;
;; Comma-separated list of domain names that are not allowed to be used to register on a Gitea instance
;EMAIL_DOMAIN_BLOCKLIST =
;;
;; Disallow registration, only allow admins to create accounts.
;DISABLE_REGISTRATION = false
;;
;; Allow registration only using gitea itself, it works only when DISABLE_REGISTRATION is false
;ALLOW_ONLY_INTERNAL_REGISTRATION = false
;;
;; Allow registration only using third-party services, it works only when DISABLE_REGISTRATION is false
;ALLOW_ONLY_EXTERNAL_REGISTRATION = false
;;
;; User must sign in to view anything.
;REQUIRE_SIGNIN_VIEW = false
;;
;; Mail notification
;ENABLE_NOTIFY_MAIL = false
;;
;; This setting enables gitea to be signed in with HTTP BASIC Authentication using the user's password
;; If you set this to false you will not be able to access the tokens endpoints on the API with your password
;; Please note that setting this to false will not disable OAuth Basic or Basic authentication using a token
;ENABLE_BASIC_AUTHENTICATION = true
;;
;; More detail: https://github.com/gogits/gogs/issues/165
;ENABLE_REVERSE_PROXY_AUTHENTICATION = false
;ENABLE_REVERSE_PROXY_AUTO_REGISTRATION = false
;ENABLE_REVERSE_PROXY_EMAIL = false
;ENABLE_REVERSE_PROXY_FULL_NAME = false
;;
;; Enable captcha validation for registration
;ENABLE_CAPTCHA = false
;;
;; Type of captcha you want to use. Options: image, recaptcha, hcaptcha, mcaptcha.
;CAPTCHA_TYPE = image
;;
;; Change this to use recaptcha.net or other recaptcha service
;RECAPTCHA_URL = https://www.google.com/recaptcha/
;; Enable recaptcha to use Google's recaptcha service
;; Go to https://www.google.com/recaptcha/admin to sign up for a key
;RECAPTCHA_SECRET =
;RECAPTCHA_SITEKEY =
;;
;; For hCaptcha, create an account at https://accounts.hcaptcha.com/login to get your keys
;HCAPTCHA_SECRET =
;HCAPTCHA_SITEKEY =
;;
;; Change this to use demo.mcaptcha.org or your self-hosted mcaptcha.org instance.
;MCAPTCHA_URL = https://demo.mcaptcha.org
;;
;; Go to your configured mCaptcha instance and register a sitekey
;; and use your account's secret.
;MCAPTCHA_SECRET =
;MCAPTCHA_SITEKEY =
;;
;; Default value for KeepEmailPrivate
;; Each new user will get the value of this setting copied into their profile
;DEFAULT_KEEP_EMAIL_PRIVATE = false
;;
;; Default value for AllowCreateOrganization
;; Every new user will have rights set to create organizations depending on this setting
;DEFAULT_ALLOW_CREATE_ORGANIZATION = true
;; Default value for IsRestricted
;; Every new user will have restricted permissions depending on this setting
;DEFAULT_USER_IS_RESTRICTED = false
;;
;; Either "public", "limited" or "private", default is "public"
;; Limited is for users visible only to signed users
;; Private is for users visible only to members of their organizations
;; Public is for users visible for everyone
;DEFAULT_USER_VISIBILITY = public
;;
;; Set which visibility modes a user can have
;ALLOWED_USER_VISIBILITY_MODES = public,limited,private
;;
;; Either "public", "limited" or "private", default is "public"
;; Limited is for organizations visible only to signed users
;; Private is for organizations visible only to members of the organization
;; Public is for organizations visible to everyone
;DEFAULT_ORG_VISIBILITY = public
;;
;; Default value for DefaultOrgMemberVisible
;; True will make the membership of the users visible when added to the organisation
;DEFAULT_ORG_MEMBER_VISIBLE = false
;;
;; Default value for EnableDependencies
;; Repositories will use dependencies by default depending on this setting
;DEFAULT_ENABLE_DEPENDENCIES = true
;;
;; Dependencies can be added from any repository where the user is granted access or only from the current repository depending on this setting.
;ALLOW_CROSS_REPOSITORY_DEPENDENCIES = true
;;
;; Enable heatmap on users profiles.
;ENABLE_USER_HEATMAP = true
;;
;; Enable Timetracking
;ENABLE_TIMETRACKING = true
;;
;; Default value for EnableTimetracking
;; Repositories will use timetracking by default depending on this setting
;DEFAULT_ENABLE_TIMETRACKING = true
;;
;; Default value for AllowOnlyContributorsToTrackTime
;; Only users with write permissions can track time if this is true
;DEFAULT_ALLOW_ONLY_CONTRIBUTORS_TO_TRACK_TIME = true
;;
;; Value for the domain part of the user's email address in the git log if user
;; has set KeepEmailPrivate to true. The user's email will be replaced with a
;; concatenation of the user name in lower case, "@" and NO_REPLY_ADDRESS. Default
;; value is "noreply." + DOMAIN, where DOMAIN resolves to the value from server.DOMAIN
;; Note: do not use the <DOMAIN> notation below
;NO_REPLY_ADDRESS = ; noreply.<DOMAIN>
;;
;; Show Registration button
;SHOW_REGISTRATION_BUTTON = true
;;
;; Show milestones dashboard page - a view of all the user's milestones
;SHOW_MILESTONES_DASHBOARD_PAGE = true
;;
;; Default value for AutoWatchNewRepos
;; When adding a repo to a team or creating a new repo all team members will watch the
;; repo automatically if enabled
;AUTO_WATCH_NEW_REPOS = true
;;
;; Default value for AutoWatchOnChanges
;; Make the user watch a repository When they commit for the first time
;AUTO_WATCH_ON_CHANGES = false
;;
;; Minimum amount of time a user must exist before comments are kept when the user is deleted.
;USER_DELETE_WITH_COMMENTS_MAX_TIME = 0
;; Valid site url schemes for user profiles
;VALID_SITE_URL_SCHEMES=http,https


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Other Settings
;;
;; Uncomment the [section.header] if you wish to
;; set the below settings.
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[repository]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Root path for storing all repository data. By default, it is set to %(APP_DATA_PATH)/gitea-repositories.
;; A relative path is interpreted as %(GITEA_WORK_DIR)/%(ROOT)
;ROOT =
;;
;; The script type this server supports. Usually this is `bash`, but some users report that only `sh` is available.
;SCRIPT_TYPE = bash
;;
;; DETECTED_CHARSETS_ORDER tie-break order for detected charsets.
;; If the charsets have equal confidence, tie-breaking will be done by order in this list
;; with charsets earlier in the list chosen in preference to those later.
;; Adding "defaults" will place the unused charsets at that position.
;DETECTED_CHARSETS_ORDER = UTF-8, UTF-16BE, UTF-16LE, UTF-32BE, UTF-32LE, ISO-8859, windows-1252, ISO-8859, windows-1250, ISO-8859, ISO-8859, ISO-8859, windows-1253, ISO-8859, windows-1255, ISO-8859, windows-1251, windows-1256, KOI8-R, ISO-8859, windows-1254, Shift_JIS, GB18030, EUC-JP, EUC-KR, Big5, ISO-2022, ISO-2022, ISO-2022, IBM424_rtl, IBM424_ltr, IBM420_rtl, IBM420_ltr
;;
;; Default ANSI charset to override non-UTF-8 charsets to
;ANSI_CHARSET =
;;
;; Force every new repository to be private
;FORCE_PRIVATE = false
;;
;; Default privacy setting when creating a new repository, allowed values: last, private, public. Default is last which means the last setting used.
;DEFAULT_PRIVATE = last
;;
;; Default private when using push-to-create
;DEFAULT_PUSH_CREATE_PRIVATE = true
;;
;; Global limit of repositories per user, applied at creation time. -1 means no limit
;MAX_CREATION_LIMIT = -1
;;
;; Mirror sync queue length, increase if mirror syncing starts hanging (DEPRECATED: please use [queue.mirror] LENGTH instead)
;MIRROR_QUEUE_LENGTH = 1000
;;
;; Patch test queue length, increase if pull request patch testing starts hanging (DEPRECATED: please use [queue.pr_patch_checker] LENGTH instead)
;PULL_REQUEST_QUEUE_LENGTH = 1000
;;
;; Preferred Licenses to place at the top of the List
;; The name here must match the filename in options/license or custom/options/license
;PREFERRED_LICENSES = Apache License 2.0,MIT License
;;
;; Disable the ability to interact with repositories using the HTTP protocol
;DISABLE_HTTP_GIT = false
;;
;; Value for Access-Control-Allow-Origin header, default is not to present
;; WARNING: This may be harmful to your website if you do not give it a right value.
;ACCESS_CONTROL_ALLOW_ORIGIN =
;;
;; Force ssh:// clone url instead of scp-style uri when default SSH port is used
;USE_COMPAT_SSH_URI = false
;;
;; Close issues as long as a commit on any branch marks it as fixed
;; Comma separated list of globally disabled repo units. Allowed values: repo.issues, repo.ext_issues, repo.pulls, repo.wiki, repo.ext_wiki, repo.projects
;DISABLED_REPO_UNITS =
;;
;; Comma separated list of default repo units. Allowed values: repo.code, repo.releases, repo.issues, repo.pulls, repo.wiki, repo.projects.
;; Note: Code and Releases can currently not be deactivated. If you specify default repo units you should still list them for future compatibility.
;; External wiki and issue tracker can't be enabled by default as it requires additional settings.
;; Disabled repo units will not be added to new repositories regardless if it is in the default list.
;DEFAULT_REPO_UNITS = repo.code,repo.releases,repo.issues,repo.pulls,repo.wiki,repo.projects
;;
;; Prefix archive files by placing them in a directory named after the repository
;PREFIX_ARCHIVE_FILES = true
;;
;; Disable migrating feature.
;DISABLE_MIGRATIONS = false
;;
;; Disable stars feature.
;DISABLE_STARS = false
;;
;; The default branch name of new repositories
;DEFAULT_BRANCH = main
;;
;; Allow adoption of unadopted repositories
;ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES = false
;;
;; Allow deletion of unadopted repositories
;ALLOW_DELETION_OF_UNADOPTED_REPOSITORIES = false

;; Don't allow download source archive files from UI
;DISABLE_DOWNLOAD_SOURCE_ARCHIVES = false

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[repository.editor]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; List of file extensions for which lines should be wrapped in the Monaco editor
;; Separate extensions with a comma. To line wrap files without an extension, just put a comma
;LINE_WRAP_EXTENSIONS = .txt,.md,.markdown,.mdown,.mkd,
;;
;; Valid file modes that have a preview API associated with them, such as api/v1/markdown
;; Separate the values by commas. The preview tab in edit mode won't be displayed if the file extension doesn't match
;PREVIEWABLE_FILE_MODES = markdown

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[repository.local]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Path for local repository copy. Defaults to `tmp/local-repo` (content gets deleted on gitea restart)
;LOCAL_COPY_PATH = tmp/local-repo

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[repository.upload]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Whether repository file uploads are enabled. Defaults to `true`
;ENABLED = true
;;
;; Path for uploads. Defaults to `data/tmp/uploads` (content gets deleted on gitea restart)
;TEMP_PATH = data/tmp/uploads
;;
;; Comma-separated list of allowed file extensions (`.zip`), mime types (`text/plain`) or wildcard type (`image/*`, `audio/*`, `video/*`). Empty value or `*/*` allows all types.
;ALLOWED_TYPES =
;;
;; Max size of each file in megabytes. Defaults to 3MB
;FILE_MAX_SIZE = 3
;;
;; Max number of files per upload. Defaults to 5
;MAX_FILES = 5

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[repository.pull-request]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; List of prefixes used in Pull Request title to mark them as Work In Progress (matched in a case-insensitive manner)
;WORK_IN_PROGRESS_PREFIXES = WIP:,[WIP]
;;
;; List of keywords used in Pull Request comments to automatically close a related issue
;CLOSE_KEYWORDS = close,closes,closed,fix,fixes,fixed,resolve,resolves,resolved
;;
;; List of keywords used in Pull Request comments to automatically reopen a related issue
;REOPEN_KEYWORDS = reopen,reopens,reopened
;;
;; Set default merge style for repository creating, valid options: merge, rebase, rebase-merge, squash
;DEFAULT_MERGE_STYLE = merge
;;
;; In the default merge message for squash commits include at most this many commits
;DEFAULT_MERGE_MESSAGE_COMMITS_LIMIT = 50
;;
;; In the default merge message for squash commits limit the size of the commit messages to this
;DEFAULT_MERGE_MESSAGE_SIZE = 5120
;;
;; In the default merge message for squash commits walk all commits to include all authors in the Co-authored-by otherwise just use those in the limited list
;DEFAULT_MERGE_MESSAGE_ALL_AUTHORS = false
;;
;; In default merge messages limit the number of approvers listed as Reviewed-by: to this many
;DEFAULT_MERGE_MESSAGE_MAX_APPROVERS = 10
;;
;; In default merge messages only include approvers who are official
;DEFAULT_MERGE_MESSAGE_OFFICIAL_APPROVERS_ONLY = true
;;
;; Add co-authored-by and co-committed-by trailers if committer does not match author
;ADD_CO_COMMITTER_TRAILERS = true
;;
;; In addition to testing patches using the three-way merge method, re-test conflicting patches with git apply
;TEST_CONFLICTING_PATCHES_WITH_GIT_APPLY = true

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[repository.issue]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; List of reasons why a Pull Request or Issue can be locked
;LOCK_REASONS = Too heated,Off-topic,Resolved,Spam

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[repository.release]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Comma-separated list of allowed file extensions (`.zip`), mime types (`text/plain`) or wildcard type (`image/*`, `audio/*`, `video/*`). Empty value or `*/*` allows all types.
;ALLOWED_TYPES =
;DEFAULT_PAGING_NUM = 10

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[repository.signing]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; GPG key to use to sign commits, Defaults to the default - that is the value of git config --get user.signingkey
;; run in the context of the RUN_USER
;; Switch to none to stop signing completely
;SIGNING_KEY = default
;;
;; If a SIGNING_KEY ID is provided and is not set to default, use the provided Name and Email address as the signer.
;; These should match a publicized name and email address for the key. (When SIGNING_KEY is default these are set to
;; the results of git config --get user.name and git config --get user.email respectively and can only be overridden
;; by setting the SIGNING_KEY ID to the correct ID.)
;SIGNING_NAME =
;SIGNING_EMAIL =
;;
;; Sets the default trust model for repositories. Options are: collaborator, committer, collaboratorcommitter
;DEFAULT_TRUST_MODEL = collaborator
;;
;; Determines when gitea should sign the initial commit when creating a repository
;; Either:
;; - never
;; - pubkey: only sign if the user has a pubkey
;; - twofa: only sign if the user has logged in with twofa
;; - always
;; options other than none and always can be combined as comma separated list
;INITIAL_COMMIT = always
;;
;; Determines when to sign for CRUD actions
;; - as above
;; - parentsigned: requires that the parent commit is signed.
;CRUD_ACTIONS = pubkey, twofa, parentsigned
;; Determines when to sign Wiki commits
;; - as above
;WIKI = never
;;
;; Determines when to sign on merges
;; - basesigned: require that the parent of commit on the base repo is signed.
;; - commitssigned: require that all the commits in the head branch are signed.
;; - approved: only sign when merging an approved pr to a protected branch
;MERGES = pubkey, twofa, basesigned, commitssigned

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[repository.mimetype_mapping]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Custom MIME type mapping for downloadable files
;.apk=application/vnd.android.package-archive

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[project]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Default templates for project boards
;PROJECT_BOARD_BASIC_KANBAN_TYPE = To Do, In Progress, Done
;PROJECT_BOARD_BUG_TRIAGE_TYPE = Needs Triage, High Priority, Low Priority, Closed

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cors]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; More information about CORS can be found here: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS#The_HTTP_response_headers
;; enable cors headers (disabled by default)
;ENABLED = false
;;
;; scheme of allowed requests
;SCHEME = http
;;
;; list of requesting domains that are allowed
;ALLOW_DOMAIN = *
;;
;; allow subdomains of headers listed above to request
;ALLOW_SUBDOMAIN = false
;;
;; list of methods allowed to request
;METHODS = GET,HEAD,POST,PUT,PATCH,DELETE,OPTIONS
;;
;; max time to cache response
;MAX_AGE = 10m
;;
;; allow request with credentials
;ALLOW_CREDENTIALS = false
;;
;; set X-FRAME-OPTIONS header
;X_FRAME_OPTIONS = SAMEORIGIN

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[ui]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Number of repositories that are displayed on one explore page
;EXPLORE_PAGING_NUM = 20
;;
;; Number of issues that are displayed on one page
;ISSUE_PAGING_NUM = 20
;;
;; Number of maximum commits displayed in one activity feed
;FEED_MAX_COMMIT_NUM = 5
;;
;; Number of items that are displayed in home feed
;FEED_PAGING_NUM = 20
;;
;; Number of items that are displayed in a single subsitemap
;SITEMAP_PAGING_NUM = 20
;;
;; Number of maximum commits displayed in commit graph.
;GRAPH_MAX_COMMIT_NUM = 100
;;
;; Number of line of codes shown for a code comment
;CODE_COMMENT_LINES = 4
;;
;; Value of `theme-color` meta tag, used by Android >= 5.0
;; An invalid color like "none" or "disable" will have the default style
;; More info: https://developers.google.com/web/updates/2014/11/Support-for-theme-color-in-Chrome-39-for-Android
;THEME_COLOR_META_TAG = `#6cc644`
;;
;; Max size of files to be displayed (default is 8MiB)
;MAX_DISPLAY_FILE_SIZE = 8388608
;;
;; Whether the email of the user should be shown in the Explore Users page
;SHOW_USER_EMAIL = true
;;
;; Set the default theme for the Gitea install
;DEFAULT_THEME = auto
;;
;; All available themes. Allow users select personalized themes regardless of the value of `DEFAULT_THEME`.
;THEMES = auto,gitea,arc-green
;;
;; All available reactions users can choose on issues/prs and comments.
;; Values can be emoji alias (:smile:) or a unicode emoji.
;; For custom reactions, add a tightly cropped square image to public/img/emoji/reaction_name.png
;REACTIONS = +1, -1, laugh, hooray, confused, heart, rocket, eyes
;;
;; Additional Emojis not defined in the utf8 standard
;; By default we support gitea (:gitea:), to add more copy them to public/img/emoji/emoji_name.png and add it to this config.
;; Dont mistake it for Reactions.
;CUSTOM_EMOJIS = gitea, codeberg, gitlab, git, github, gogs
;;
;; Whether the full name of the users should be shown where possible. If the full name isn't set, the username will be used.
;DEFAULT_SHOW_FULL_NAME = false
;;
;; Whether to search within description at repository search on explore page.
;SEARCH_REPO_DESCRIPTION = true
;;
;; Whether to enable a Service Worker to cache frontend assets
;USE_SERVICE_WORKER = false
;;
;; Whether to only show relevant repos on the explore page when no keyword is specified and default sorting is used.
;; A repo is considered irrelevant if it's a fork or if it has no metadata (no description, no icon, no topic).
;ONLY_SHOW_RELEVANT_REPOS = false

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[ui.admin]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Number of users that are displayed on one page
;USER_PAGING_NUM = 50
;;
;; Number of repos that are displayed on one page
;REPO_PAGING_NUM = 50
;;
;; Number of notices that are displayed on one page
;NOTICE_PAGING_NUM = 25
;;
;; Number of organizations that are displayed on one page
;ORG_PAGING_NUM = 50

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[ui.user]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Number of repos that are displayed on one page
;REPO_PAGING_NUM = 15

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[ui.meta]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;AUTHOR = Gitea - Git with a cup of tea
;DESCRIPTION = Gitea (Git with a cup of tea) is a painless self-hosted Git service written in Go
;KEYWORDS = go,git,self-hosted,gitea

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[ui.notification]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Control how often the notification endpoint is polled to update the notification
;; The timeout will increase to MAX_TIMEOUT in TIMEOUT_STEPs if the notification count is unchanged
;; Set MIN_TIMEOUT to -1 to turn off
;MIN_TIMEOUT = 10s
;MAX_TIMEOUT = 60s
;TIMEOUT_STEP = 10s
;;
;; This setting determines how often the db is queried to get the latest notification counts.
;; If the browser client supports EventSource and SharedWorker, a SharedWorker will be used in preference to polling notification. Set to -1 to disable the EventSource
;EVENT_SOURCE_UPDATE_TIME = 10s

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[ui.svg]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Whether to render SVG files as images.  If SVG rendering is disabled, SVG files are displayed as text and cannot be embedded in markdown files as images.
;ENABLE_RENDER = true

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[ui.csv]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Maximum allowed file size in bytes to render CSV files as table. (Set to 0 for no limit).
;MAX_FILE_SIZE = 524288

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[markdown]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Render soft line breaks as hard line breaks, which means a single newline character between
;; paragraphs will cause a line break and adding trailing whitespace to paragraphs is not
;; necessary to force a line break.
;; Render soft line breaks as hard line breaks for comments
;ENABLE_HARD_LINE_BREAK_IN_COMMENTS = true
;;
;; Render soft line breaks as hard line breaks for markdown documents
;ENABLE_HARD_LINE_BREAK_IN_DOCUMENTS = false
;;
;; Comma separated list of custom URL-Schemes that are allowed as links when rendering Markdown
;; for example git,magnet,ftp (more at https://en.wikipedia.org/wiki/List_of_URI_schemes)
;; URLs starting with http and https are always displayed, whatever is put in this entry.
;CUSTOM_URL_SCHEMES =
;;
;; List of file extensions that should be rendered/edited as Markdown
;; Separate the extensions with a comma. To render files without any extension as markdown, just put a comma
;FILE_EXTENSIONS = .md,.markdown,.mdown,.mkd
;;
;; Enables math inline and block detection
;ENABLE_MATH = true

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[ssh.minimum_key_sizes]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Define allowed algorithms and their minimum key length (use -1 to disable a type)
;ED25519 = 256
;ECDSA = 256
;RSA = 2047 ; we allow 2047 here because an otherwise valid 2048 bit RSA key can be reported as having 2047 bit length
;DSA = -1 ; set to 1024 to switch on

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[indexer]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Issue Indexer settings
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Issue indexer type, currently support: bleve, db or elasticsearch, default is bleve
;ISSUE_INDEXER_TYPE = bleve
;;
;; Issue indexer storage path, available when ISSUE_INDEXER_TYPE is bleve
;ISSUE_INDEXER_PATH = indexers/issues.bleve
;;
;; Issue indexer connection string, available when ISSUE_INDEXER_TYPE is elasticsearch
;ISSUE_INDEXER_CONN_STR = http://elastic:changeme@localhost:9200
;;
;; Issue indexer name, available when ISSUE_INDEXER_TYPE is elasticsearch
;ISSUE_INDEXER_NAME = gitea_issues
;;
;; Timeout the indexer if it takes longer than this to start.
;; Set to -1 to disable timeout.
;STARTUP_TIMEOUT = 30s
;;
;; Issue indexer queue, currently support: channel, levelqueue or redis, default is levelqueue (deprecated - use [queue.issue_indexer])
;ISSUE_INDEXER_QUEUE_TYPE = levelqueue; **DEPRECATED** use settings in `[queue.issue_indexer]`.
;;
;; When ISSUE_INDEXER_QUEUE_TYPE is levelqueue, this will be the path where the queue will be saved.
;; This can be overridden by `ISSUE_INDEXER_QUEUE_CONN_STR`.
;; default is queues/common
;ISSUE_INDEXER_QUEUE_DIR = queues/common; **DEPRECATED** use settings in `[queue.issue_indexer]`.
;;
;; When `ISSUE_INDEXER_QUEUE_TYPE` is `redis`, this will store the redis connection string.
;; When `ISSUE_INDEXER_QUEUE_TYPE` is `levelqueue`, this is a directory or additional options of
;; the form `leveldb://path/to/db?option=value&....`, and overrides `ISSUE_INDEXER_QUEUE_DIR`.
;ISSUE_INDEXER_QUEUE_CONN_STR = "addrs=127.0.0.1:6379 db=0"; **DEPRECATED** use settings in `[queue.issue_indexer]`.
;;
;; Batch queue number, default is 20
;ISSUE_INDEXER_QUEUE_BATCH_NUMBER = 20; **DEPRECATED** use settings in `[queue.issue_indexer]`.

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Repository Indexer settings
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; repo indexer by default disabled, since it uses a lot of disk space
;REPO_INDEXER_ENABLED = false
;;
;; Code search engine type, could be `bleve` or `elasticsearch`.
;REPO_INDEXER_TYPE = bleve
;;
;; Index file used for code search. available when `REPO_INDEXER_TYPE` is bleve
;REPO_INDEXER_PATH = indexers/repos.bleve
;;
;; Code indexer connection string, available when `REPO_INDEXER_TYPE` is elasticsearch. i.e. http://elastic:changeme@localhost:9200
;REPO_INDEXER_CONN_STR =
;;
;; Code indexer name, available when `REPO_INDEXER_TYPE` is elasticsearch
;REPO_INDEXER_NAME = gitea_codes
;;
;; A comma separated list of glob patterns (see https://github.com/gobwas/glob) to include
;; in the index; default is empty
;REPO_INDEXER_INCLUDE =
;;
;; A comma separated list of glob patterns to exclude from the index; ; default is empty
;REPO_INDEXER_EXCLUDE =
;;
;;
;UPDATE_BUFFER_LEN = 20; **DEPRECATED** use settings in `[queue.issue_indexer]`.
;MAX_FILE_SIZE = 1048576

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[queue]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Specific queues can be individually configured with [queue.name]. [queue] provides defaults
;; ([queue.issue_indexer] is special due to the old configuration described above)
;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; General queue queue type, currently support: persistable-channel, channel, level, redis, dummy
;; default to persistable-channel
;TYPE = persistable-channel
;;
;; data-dir for storing persistable queues and level queues, individual queues will default to `queues/common` meaning the queue is shared.
;DATADIR = queues/
;;
;; Default queue length before a channel queue will block
;LENGTH = 20
;;
;; Batch size to send for batched queues
;BATCH_LENGTH = 20
;;
;; Connection string for redis queues this will store the redis connection string.
;; When `TYPE` is `persistable-channel`, this provides a directory for the underlying leveldb
;; or additional options of the form `leveldb://path/to/db?option=value&....`, and will override `DATADIR`.
;CONN_STR = "addrs=127.0.0.1:6379 db=0"
;;
;; Provides the suffix of the default redis/disk queue name - specific queues can be overridden within in their [queue.name] sections.
;QUEUE_NAME = "_queue"
;;
;; Provides the suffix of the default redis/disk unique queue set name - specific queues can be overridden within in their [queue.name] sections.
;SET_NAME = "_unique"
;;
;; If the queue cannot be created at startup - level queues may need a timeout at startup - wrap the queue:
;WRAP_IF_NECESSARY = true
;;
;; Attempt to create the wrapped queue at max
;MAX_ATTEMPTS = 10
;;
;; Timeout queue creation
;TIMEOUT = 15m30s
;;
;; Create a pool with this many workers
;WORKERS = 0
;;
;; Dynamically scale the worker pool to at this many workers
;MAX_WORKERS = 10
;;
;; Add boost workers when the queue blocks for BLOCK_TIMEOUT
;BLOCK_TIMEOUT = 1s
;;
;; Remove the boost workers after BOOST_TIMEOUT
;BOOST_TIMEOUT = 5m
;;
;; During a boost add BOOST_WORKERS
;BOOST_WORKERS = 1

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[admin]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Disallow regular (non-admin) users from creating organizations.
;DISABLE_REGULAR_ORG_CREATION = false
;;
;; Default configuration for email notifications for users (user configurable). Options: enabled, onmention, disabled
;DEFAULT_EMAIL_NOTIFICATIONS = enabled

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[openid]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; OpenID is an open, standard and decentralized authentication protocol.
;; Your identity is the address of a webpage you provide, which describes
;; how to prove you are in control of that page.
;;
;; For more info: https://en.wikipedia.org/wiki/OpenID
;;
;; Current implementation supports OpenID-2.0
;;
;; Tested to work providers at the time of writing:
;;  - Any GNUSocial node (your.hostname.tld/username)
;;  - Any SimpleID provider (http://simpleid.koinic.net)
;;  - http://openid.org.cn/
;;  - openid.stackexchange.com
;;  - login.launchpad.net
;;  - <username>.livejournal.com
;;
;; Whether to allow signin in via OpenID
;ENABLE_OPENID_SIGNIN = true
;;
;; Whether to allow registering via OpenID
;; Do not include to rely on rhw DISABLE_REGISTRATION setting
;;ENABLE_OPENID_SIGNUP = true
;;
;; Allowed URI patterns (POSIX regexp).
;; Space separated.
;; Only these would be allowed if non-blank.
;; Example value: trusted.domain.org trusted.domain.net
;WHITELISTED_URIS =
;;
;; Forbidden URI patterns (POSIX regexp).
;; Space separated.
;; Only used if WHITELISTED_URIS is blank.
;; Example value: loadaverage.org/badguy stackexchange.com/.*spammer
;BLACKLISTED_URIS =

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[oauth2_client]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Whether a new auto registered oauth2 user needs to confirm their email.
;; Do not include to use the REGISTER_EMAIL_CONFIRM setting from the `[service]` section.
;REGISTER_EMAIL_CONFIRM =
;;
;; Scopes for the openid connect oauth2 provider (separated by space, the openid scope is implicitly added).
;; Typical values are profile and email.
;; For more information about the possible values see https://openid.net/specs/openid-connect-core-1_0.html#ScopeClaims
;OPENID_CONNECT_SCOPES =
;;
;; Automatically create user accounts for new oauth2 users.
;ENABLE_AUTO_REGISTRATION = false
;;
;; The source of the username for new oauth2 accounts:
;; userid = use the userid / sub attribute
;; nickname = use the nickname attribute
;; email = use the username part of the email attribute
;USERNAME = nickname
;;
;; Update avatar if available from oauth2 provider.
;; Update will be performed on each login.
;UPDATE_AVATAR = false
;;
;; How to handle if an account / email already exists:
;; disabled = show an error
;; login = show an account linking login
;; auto = link directly with the account
;ACCOUNT_LINKING = login

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[webhook]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Hook task queue length, increase if webhook shooting starts hanging
;QUEUE_LENGTH = 1000
;;
;; Deliver timeout in seconds
;DELIVER_TIMEOUT = 5
;;
;; Webhook can only call allowed hosts for security reasons. Comma separated list, eg: external, 192.168.1.0/24, *.mydomain.com
;; Built-in: loopback (for localhost), private (for LAN/intranet), external (for public hosts on internet), * (for all hosts)
;; CIDR list: 1.2.3.0/8, 2001:db8::/32
;; Wildcard hosts: *.mydomain.com, 192.168.100.*
;; Since 1.15.7. Default to * for 1.15.x, external for 1.16 and later
;ALLOWED_HOST_LIST = external
;;
;; Allow insecure certification
;SKIP_TLS_VERIFY = false
;;
;; Number of history information in each page
;PAGING_NUM = 10
;;
;; Proxy server URL, support http://, https//, socks://, blank will follow environment http_proxy/https_proxy
;PROXY_URL =
;;
;; Comma separated list of host names requiring proxy. Glob patterns (*) are accepted; use ** to match all hosts.
;PROXY_HOSTS =

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[mailer]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; NOTICE: this section is for Gitea 1.18 and later. If you are using Gitea 1.17 or older,
;; please refer to
;; https://github.com/go-gitea/gitea/blob/release/v1.17/custom/conf/app.example.ini
;; https://github.com/go-gitea/gitea/blob/release/v1.17/docs/content/doc/advanced/config-cheat-sheet.en-us.md
;;
;ENABLED = false
;;
;; Buffer length of channel, keep it as it is if you don't know what it is.
;SEND_BUFFER_LEN = 100
;;
;; Prefix displayed before subject in mail
;SUBJECT_PREFIX =
;;
;; Mail server protocol. One of "smtp", "smtps", "smtp+starttls", "smtp+unix", "sendmail", "dummy".
;; - sendmail: use the operating system's `sendmail` command instead of SMTP. This is common on Linux systems.
;; - dummy: send email messages to the log as a testing phase.
;; If your provider does not explicitly say which protocol it uses but does provide a port,
;; you can set SMTP_PORT instead and this will be inferred.
;; (Before 1.18, see the notice, this was controlled via MAILER_TYPE and IS_TLS_ENABLED.)
;PROTOCOL =
;;
;; Mail server address, e.g. smtp.gmail.com.
;; For smtp+unix, this should be a path to a unix socket instead.
;; (Before 1.18, see the notice, this was combined with SMTP_PORT as HOST.)
;SMTP_ADDR =
;;
;; Mail server port. Common ports are:
;;   25:  insecure SMTP
;;   465: SMTP Secure
;;   587: StartTLS
;; If no protocol is specified, it will be inferred by this setting.
;; (Before 1.18, this was combined with SMTP_ADDR as HOST.)
;SMTP_PORT =
;;
;; Enable HELO operation. Defaults to true.
;ENABLE_HELO = true
;;
;; Custom hostname for HELO operation.
;; If no value is provided, one is retrieved from system.
;HELO_HOSTNAME =
;;
;; If set to `true`, completely ignores server certificate validation errors.
;; This option is unsafe. Consider adding the certificate to the system trust store instead.
;FORCE_TRUST_SERVER_CERT = false
;;
;; Use client certificate in connection.
;USE_CLIENT_CERT = false
;CLIENT_CERT_FILE = custom/mailer/cert.pem
;CLIENT_KEY_FILE = custom/mailer/key.pem
;;
;; Mail from address, RFC 5322. This can be just an email address, or the `"Name" <email@example.com>` format
;FROM =
;;
;; Sometimes it is helpful to use a different address on the envelope. Set this to use ENVELOPE_FROM as the from on the envelope. Set to `<>` to send an empty address.
;ENVELOPE_FROM =
;;
;; Mailer user name and password, if required by provider.
;USER =
;;
;; Use PASSWD = `your password` for quoting if you use special characters in the password.
;PASSWD =
;;
;; Send mails only in plain text, without HTML alternative
;SEND_AS_PLAIN_TEXT = false
;;
;; Specify an alternative sendmail binary
;SENDMAIL_PATH = sendmail
;;
;; Specify any extra sendmail arguments
;; WARNING: if your sendmail program interprets options you should set this to "--" or terminate these args with "--"
;SENDMAIL_ARGS =
;;
;; Timeout for Sendmail
;SENDMAIL_TIMEOUT = 5m
;;
;; convert \r\n to \n for Sendmail
;SENDMAIL_CONVERT_CRLF = true

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cache]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; if the cache enabled
;ENABLED = true
;;
;; Either "memory", "redis", "memcache", or "twoqueue". default is "memory"
;ADAPTER = memory
;;
;; For "memory" only, GC interval in seconds, default is 60
;INTERVAL = 60
;;
;; For "redis" and "memcache", connection host address
;; redis: network=tcp,addr=:6379,password=macaron,db=0,pool_size=100,idle_timeout=180
;; memcache: `127.0.0.1:11211`
;; twoqueue: `{"size":50000,"recent_ratio":0.25,"ghost_ratio":0.5}` or `50000`
;HOST =
;;
;; Time to keep items in cache if not used, default is 16 hours.
;; Setting it to -1 disables caching
;ITEM_TTL = 16h

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Last commit cache
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cache.last_commit]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; if the cache enabled
;ENABLED = true
;;
;; Time to keep items in cache if not used, default is 8760 hours.
;; Setting it to -1 disables caching
;ITEM_TTL = 8760h
;;
;; Only enable the cache when repository's commits count great than
;COMMITS_COUNT = 1000

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[session]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Either "memory", "file", "redis", "db", "mysql", "couchbase", "memcache" or "postgres"
;; Default is "memory". "db" will reuse the configuration in [database]
;PROVIDER = memory
;;
;; Provider config options
;; memory: doesn't have any config yet
;; file: session file path, e.g. `data/sessions`
;; redis: network=tcp,addr=:6379,password=macaron,db=0,pool_size=100,idle_timeout=180
;; mysql: go-sql-driver/mysql dsn config string, e.g. `root:password@/session_table`
;PROVIDER_CONFIG = data/sessions
;;
;; Session cookie name
;COOKIE_NAME = i_like_gitea
;;
;; If you use session in https only, default is false
;COOKIE_SECURE = false
;;
;; Session GC time interval in seconds, default is 86400 (1 day)
;GC_INTERVAL_TIME = 86400
;;
;; Session life time in seconds, default is 86400 (1 day)
;SESSION_LIFE_TIME = 86400
;;
;; SameSite settings. Either "none", "lax", or "strict"
;SAME_SITE=lax

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[picture]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;AVATAR_UPLOAD_PATH = data/avatars
;REPOSITORY_AVATAR_UPLOAD_PATH = data/repo-avatars
;;
;; How Gitea deals with missing repository avatars
;; none = no avatar will be displayed; random = random avatar will be displayed; image = default image will be used
;REPOSITORY_AVATAR_FALLBACK = none
;REPOSITORY_AVATAR_FALLBACK_IMAGE = /img/repo_default.png
;;
;; Max Width and Height of uploaded avatars.
;; This is to limit the amount of RAM used when resizing the image.
;AVATAR_MAX_WIDTH = 4096
;AVATAR_MAX_HEIGHT = 3072
;;
;; The multiplication factor for rendered avatar images.
;; Larger values result in finer rendering on HiDPI devices.
;AVATAR_RENDERED_SIZE_FACTOR = 3
;;
;; Maximum allowed file size for uploaded avatars.
;; This is to limit the amount of RAM used when resizing the image.
;AVATAR_MAX_FILE_SIZE = 1048576
;;
;; Chinese users can choose "duoshuo"
;; or a custom avatar source, like: http://cn.gravatar.com/avatar/
;GRAVATAR_SOURCE = gravatar
;;
;; This value will always be true in offline mode.
;DISABLE_GRAVATAR = false
;;
;; Federated avatar lookup uses DNS to discover avatar associated
;; with emails, see https://www.libravatar.org
;; This value will always be false in offline mode or when Gravatar is disabled.
;ENABLE_FEDERATED_AVATAR = false

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[attachment]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Whether issue and pull request attachments are enabled. Defaults to `true`
;ENABLED = true
;;
;; Comma-separated list of allowed file extensions (`.zip`), mime types (`text/plain`) or wildcard type (`image/*`, `audio/*`, `video/*`). Empty value or `*/*` allows all types.
;ALLOWED_TYPES = .csv,.docx,.fodg,.fodp,.fods,.fodt,.gif,.gz,.jpeg,.jpg,.log,.md,.mov,.mp4,.odf,.odg,.odp,.ods,.odt,.pdf,.png,.pptx,.svg,.tgz,.txt,.webm,.xls,.xlsx,.zip
;;
;; Max size of each file. Defaults to 4MB
;MAX_SIZE = 4
;;
;; Max number of files per upload. Defaults to 5
;MAX_FILES = 5
;;
;; Storage type for attachments, `local` for local disk or `minio` for s3 compatible
;; object storage service, default is `local`.
;STORAGE_TYPE = local
;;
;; Allows the storage driver to redirect to authenticated URLs to serve files directly
;; Currently, only `minio` is supported.
;SERVE_DIRECT = false
;;
;; Path for attachments. Defaults to `data/attachments` only available when STORAGE_TYPE is `local`
;PATH = data/attachments
;;
;; Minio endpoint to connect only available when STORAGE_TYPE is `minio`
;MINIO_ENDPOINT = localhost:9000
;;
;; Minio accessKeyID to connect only available when STORAGE_TYPE is `minio`
;MINIO_ACCESS_KEY_ID =
;;
;; Minio secretAccessKey to connect only available when STORAGE_TYPE is `minio`
;MINIO_SECRET_ACCESS_KEY =
;;
;; Minio bucket to store the attachments only available when STORAGE_TYPE is `minio`
;MINIO_BUCKET = gitea
;;
;; Minio location to create bucket only available when STORAGE_TYPE is `minio`
;MINIO_LOCATION = us-east-1
;;
;; Minio base path on the bucket only available when STORAGE_TYPE is `minio`
;MINIO_BASE_PATH = attachments/
;;
;; Minio enabled ssl only available when STORAGE_TYPE is `minio`
;MINIO_USE_SSL = false

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[time]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Specifies the format for fully outputted dates. Defaults to RFC1123
;; Special supported values are ANSIC, UnixDate, RubyDate, RFC822, RFC822Z, RFC850, RFC1123, RFC1123Z, RFC3339, RFC3339Nano, Kitchen, Stamp, StampMilli, StampMicro and StampNano
;; For more information about the format see http://golang.org/pkg/time/#pkg-constants
;FORMAT =
;;
;; Location the UI time display i.e. Asia/Shanghai
;; Empty means server's location setting
;DEFAULT_UI_LOCATION =

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Common settings
;;
;; Setting this to true will enable all cron tasks periodically with default settings.
;ENABLED = false
;; Setting this to true will run all enabled cron tasks when Gitea starts.
;RUN_AT_START = false
;;
;; Note: ``SCHEDULE`` accept formats
;;    - Full crontab specs, e.g. "* * * * * ?"
;;    - Descriptors, e.g. "@midnight", "@every 1h30m"
;; See more: https://pkg.go.dev/github.com/gogs/cron@v0.0.0-20171120032916-9f6c956d3e14

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Basic cron tasks - enabled by default
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Clean up old repository archives
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.archive_cleanup]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Whether to enable the job
;ENABLED = true
;; Whether to always run at least once at start up time (if ENABLED)
;RUN_AT_START = true
;; Whether to emit notice on successful execution too
;NOTICE_ON_SUCCESS = false
;; Time interval for job to run
;SCHEDULE = @midnight
;; Archives created more than OLDER_THAN ago are subject to deletion
;OLDER_THAN = 24h

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Update mirrors
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.update_mirrors]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;SCHEDULE = @every 10m
;; Enable running Update mirrors task periodically.
;ENABLED = true
;; Run Update mirrors task when Gitea starts.
;RUN_AT_START = false
;; Notice if not success
;NOTICE_ON_SUCCESS = false
;; Limit the number of mirrors added to the queue to this number
;; (negative values mean no limit, 0 will result in no result in no mirrors being queued effectively disabling pull mirror updating.)
;PULL_LIMIT=50
;; Limit the number of mirrors added to the queue to this number
;; (negative values mean no limit, 0 will result in no mirrors being queued effectively disabling push mirror updating)
;PUSH_LIMIT=50

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Repository health check
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.repo_health_check]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;SCHEDULE = @midnight
;; Enable running Repository health check task periodically.
;ENABLED = true
;; Run Repository health check task when Gitea starts.
;RUN_AT_START = false
;; Notice if not success
;NOTICE_ON_SUCCESS = false
;TIMEOUT = 60s
;; Arguments for command 'git fsck', e.g. "--unreachable --tags"
;; see more on http://git-scm.com/docs/git-fsck
;ARGS =

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Check repository statistics
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.check_repo_stats]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Enable running check repository statistics task periodically.
;ENABLED = true
;; Run check repository statistics task when Gitea starts.
;RUN_AT_START = true
;; Notice if not success
;NOTICE_ON_SUCCESS = false
;SCHEDULE = @midnight

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.update_migration_poster_id]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Update migrated repositories' issues and comments' posterid, it will always attempt synchronization when the instance starts.
;ENABLED = true
;; Update migrated repositories' issues and comments' posterid when starting server (default true)
;RUN_AT_START = true
;; Notice if not success
;NOTICE_ON_SUCCESS = false
;; Interval as a duration between each synchronization. (default every 24h)
;SCHEDULE = @midnight

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Synchronize external user data (only LDAP user synchronization is supported)
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.sync_external_users]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;ENABLED = true
;; Synchronize external user data when starting server (default false)
;RUN_AT_START = false
;; Notice if not success
;NOTICE_ON_SUCCESS = false
;; Interval as a duration between each synchronization (default every 24h)
;SCHEDULE = @midnight
;; Create new users, update existing user data and disable users that are not in external source anymore (default)
;;   or only create new users if UPDATE_EXISTING is set to false
;UPDATE_EXISTING = true

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Clean-up deleted branches
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.deleted_branches_cleanup]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;ENABLED = true
;; Clean-up deleted branches when starting server (default true)
;RUN_AT_START = true
;; Notice if not success
;NOTICE_ON_SUCCESS = false
;; Interval as a duration between each synchronization (default every 24h)
;SCHEDULE = @midnight
;; deleted branches than OLDER_THAN ago are subject to deletion
;OLDER_THAN = 24h

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Cleanup hook_task table
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.cleanup_hook_task_table]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Whether to enable the job
;ENABLED = true
;; Whether to always run at start up time (if ENABLED)
;RUN_AT_START = false
;; Time interval for job to run
;SCHEDULE = @midnight
;; OlderThan or PerWebhook. How the records are removed, either by age (i.e. how long ago hook_task record was delivered) or by the number to keep per webhook (i.e. keep most recent x deliveries per webhook).
;CLEANUP_TYPE = OlderThan
;; If CLEANUP_TYPE is set to OlderThan, then any delivered hook_task records older than this expression will be deleted.
;OLDER_THAN = 168h
;; If CLEANUP_TYPE is set to PerWebhook, this is number of hook_task records to keep for a webhook (i.e. keep the most recent x deliveries).
;NUMBER_TO_KEEP = 10

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Cleanup expired packages
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.cleanup_packages]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Whether to enable the job
;ENABLED = true
;; Whether to always run at least once at start up time (if ENABLED)
;RUN_AT_START = true
;; Whether to emit notice on successful execution too
;NOTICE_ON_SUCCESS = false
;; Time interval for job to run
;SCHEDULE = @midnight
;; Unreferenced blobs created more than OLDER_THAN ago are subject to deletion
;OLDER_THAN = 24h

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Extended cron task - not enabled by default
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Delete all unactivated accounts
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.delete_inactive_accounts]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;ENABLED = false
;RUN_AT_START = false
;NOTICE_ON_SUCCESS = false
;SCHEDULE = @annually
;OLDER_THAN = 168h

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Delete all repository archives
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.delete_repo_archives]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;ENABLED = false
;RUN_AT_START = false
;NOTICE_ON_SUCCESS = false
;SCHEDULE = @annually;

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Garbage collect all repositories
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.git_gc_repos]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;ENABLED = false
;RUN_AT_START = false
;NOTICE_ON_SUCCESS = false
;SCHEDULE = @every 72h
;TIMEOUT = 60s
;; Arguments for command 'git gc'
;; The default value is same with [git] -> GC_ARGS
;ARGS =

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Update the '.ssh/authorized_keys' file with Gitea SSH keys
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.resync_all_sshkeys]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;ENABLED = false
;RUN_AT_START = false
;NOTICE_ON_SUCCESS = false
;SCHEDULE = @every 72h

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Resynchronize pre-receive, update and post-receive hooks of all repositories.
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.resync_all_hooks]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;ENABLED = false
;RUN_AT_START = false
;NOTICE_ON_SUCCESS = false
;SCHEDULE = @every 72h

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Reinitialize all missing Git repositories for which records exist
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.reinit_missing_repos]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;ENABLED = false
;RUN_AT_START = false
;NOTICE_ON_SUCCESS = false
;SCHEDULE = @every 72h

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Delete all repositories missing their Git files
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.delete_missing_repos]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;ENABLED = false
;RUN_AT_START = false
;NOTICE_ON_SUCCESS = false
;SCHEDULE = @every 72h

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Delete generated repository avatars
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.delete_generated_repository_avatars]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;ENABLED = false
;RUN_AT_START = false
;NOTICE_ON_SUCCESS = false
;SCHEDULE = @every 72h

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Delete all old actions from database
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.delete_old_actions]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;ENABLED = false
;RUN_AT_START = false
;NOTICE_ON_SUCCESS = false
;SCHEDULE = @every 168h
;OLDER_THAN = 8760h

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Check for new Gitea versions
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.update_checker]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;ENABLED = false
;RUN_AT_START = false
;ENABLE_SUCCESS_NOTICE = false
;SCHEDULE = @every 168h
;HTTP_ENDPOINT = https://dl.gitea.io/gitea/version.json

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Delete all old system notices from database
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.delete_old_system_notices]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;ENABLED = false
;RUN_AT_START = false
;NO_SUCCESS_NOTICE = false
;SCHEDULE = @every 168h
;OLDER_THAN = 8760h

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Git Operation timeout in seconds
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[git.timeout]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;DEFAULT = 360
;MIGRATE = 600
;MIRROR = 300
;CLONE = 300
;PULL = 300
;GC = 60

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[mirror]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Enables the mirror functionality. Set to **false** to disable all mirrors. Pre-existing mirrors remain valid but won't be updated; may be converted to regular repo.
;ENABLED = true
;; Disable the creation of **new** pull mirrors. Pre-existing mirrors remain valid. Will be ignored if `mirror.ENABLED` is `false`.
;DISABLE_NEW_PULL = false
;; Disable the creation of **new** push mirrors. Pre-existing mirrors remain valid. Will be ignored if `mirror.ENABLED` is `false`.
;DISABLE_NEW_PUSH = false
;; Default interval as a duration between each check
;DEFAULT_INTERVAL = 8h
;; Min interval as a duration must be > 1m
;MIN_INTERVAL = 10m

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[api]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Enables the API documentation endpoints (/api/swagger, /api/v1/swagger, …). True or false.
;ENABLE_SWAGGER = true
;; Max number of items in a page
;MAX_RESPONSE_ITEMS = 50
;; Default paging number of api
;DEFAULT_PAGING_NUM = 30
;; Default and maximum number of items per page for git trees api
;DEFAULT_GIT_TREES_PER_PAGE = 1000
;; Default max size of a blob returned by the blobs API (default is 10MiB)
;DEFAULT_MAX_BLOB_SIZE = 10485760

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[i18n]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; The first locale will be used as the default if user browser's language doesn't match any locale in the list.
;LANGS = en-US,zh-CN,zh-HK,zh-TW,de-DE,fr-FR,nl-NL,lv-LV,ru-RU,uk-UA,ja-JP,es-ES,pt-BR,pt-PT,pl-PL,bg-BG,it-IT,fi-FI,tr-TR,cs-CZ,sv-SE,ko-KR,el-GR,fa-IR,hu-HU,id-ID,ml-IN
;NAMES = English,简体中文,繁體中文（香港）,繁體中文（台灣）,Deutsch,Français,Nederlands,Latviešu,Русский,Українська,日本語,Español,Português do Brasil,Português de Portugal,Polski,Български,Italiano,Suomi,Türkçe,Čeština,Српски,Svenska,한국어,Ελληνικά,فارسی,Magyar nyelv,Bahasa Indonesia,മലയാളം

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[highlight.mapping]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Extension mapping to highlight class
;; e.g. .toml=ini

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[other]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;SHOW_FOOTER_BRANDING = false
;; Show version information about Gitea and Go in the footer
;SHOW_FOOTER_VERSION = true
;; Show template execution time in the footer
;SHOW_FOOTER_TEMPLATE_LOAD_TIME = true


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[markup]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Set the maximum number of characters in a mermaid source. (Set to -1 to disable limits)
;MERMAID_MAX_SOURCE_CHARACTERS = 5000

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[markup.sanitizer.1]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; The following keys can appear once to define a sanitation policy rule.
;; This section can appear multiple times by adding a unique alphanumeric suffix to define multiple rules.
;; e.g., [markup.sanitizer.1] -> [markup.sanitizer.2] -> [markup.sanitizer.TeX]
;ELEMENT = span
;ALLOW_ATTR = class
;REGEXP = ^(info|warning|error)$
;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Other markup formats e.g. asciidoc
;;
;; uncomment and enable the below section.
;; (You can add other markup formats by copying the section and adjusting
;;  the section name suffix "asciidoc" to something else.)
;[markup.asciidoc]
;ENABLED = false
;; List of file extensions that should be rendered by an external command
;FILE_EXTENSIONS = .adoc,.asciidoc
;; External command to render all matching extensions
;RENDER_COMMAND = "asciidoc --out-file=- -"
;; Don't pass the file on STDIN, pass the filename as argument instead.
;IS_INPUT_FILE = false
;; How the content will be rendered.
;; * sanitized: Sanitize the content and render it inside current page, default to only allow a few HTML tags and attributes. Customized sanitizer rules can be defined in [markup.sanitizer.*] .
;; * no-sanitizer: Disable the sanitizer and render the content inside current page. It's **insecure** and may lead to XSS attack if the content contains malicious code.
;; * iframe: Render the content in a separate standalone page and embed it into current page by iframe. The iframe is in sandbox mode with same-origin disabled, and the JS code are safely isolated from parent page.
;RENDER_CONTENT_MODE=sanitized

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[metrics]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Enables metrics endpoint. True or false; default is false.
;ENABLED = false
;; If you want to add authorization, specify a token here
;TOKEN =
;; Enable issue by label metrics; default is false
;ENABLED_ISSUE_BY_LABEL = false
;; Enable issue by repository metrics; default is false
;ENABLED_ISSUE_BY_REPOSITORY = false

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[task]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Task queue type, could be `channel` or `redis`.
;QUEUE_TYPE = channel
;;
;; Task queue length, available only when `QUEUE_TYPE` is `channel`.
;QUEUE_LENGTH = 1000
;;
;; Task queue connection string, available only when `QUEUE_TYPE` is `redis`.
;; If there is a password of redis, use `addrs=127.0.0.1:6379 password=123 db=0`.
;QUEUE_CONN_STR = "addrs=127.0.0.1:6379 db=0"

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[migrations]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Max attempts per http/https request on migrations.
;MAX_ATTEMPTS = 3
;;
;; Backoff time per http/https request retry (seconds)
;RETRY_BACKOFF = 3
;;
;; Allowed domains for migrating, default is blank. Blank means everything will be allowed.
;; Multiple domains could be separated by commas.
;; Wildcard is supported: "github.com, *.github.com"
;ALLOWED_DOMAINS =
;;
;; Blocklist for migrating, default is blank. Multiple domains could be separated by commas.
;; When ALLOWED_DOMAINS is not blank, this option has a higher priority to deny domains.
;; Wildcard is supported.
;BLOCKED_DOMAINS =
;;
;; Allow private addresses defined by RFC 1918, RFC 1122, RFC 4632 and RFC 4291 (false by default)
;; If a domain is allowed by ALLOWED_DOMAINS, this option will be ignored.
;ALLOW_LOCALNETWORKS = false

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[federation]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Enable/Disable federation capabilities
;ENABLED = false
;;
;; Enable/Disable user statistics for nodeinfo if federation is enabled
;SHARE_USER_STATISTICS = true
;;
;; Maximum federation request and response size (MB)
;MAX_SIZE = 4
;;
;; WARNING: Changing the settings below can break federation.
;;
;; HTTP signature algorithms
;ALGORITHMS = rsa-sha256, rsa-sha512, ed25519
;;
;; HTTP signature digest algorithm
;DIGEST_ALGORITHM = SHA-256
;;
;; GET headers for federation requests
;GET_HEADERS = (request-target), Date
;;
;; POST headers for federation requests
;POST_HEADERS = (request-target), Date, Digest

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[packages]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
;; Enable/Disable package registry capabilities
;ENABLED = true
;;
;; Path for chunked uploads. Defaults to APP_DATA_PATH + `tmp/package-upload`
;CHUNKED_UPLOAD_PATH = tmp/package-upload

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; default storage for attachments, lfs and avatars
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[storage]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; storage type
;STORAGE_TYPE = local

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; settings for repository archives, will override storage setting
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[storage.repo-archive]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; storage type
;STORAGE_TYPE = local

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; lfs storage will override storage
;;
;[lfs]
;STORAGE_TYPE = local
;;
;; Where your lfs files reside, default is data/lfs.
;PATH = data/lfs

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; settings for packages, will override storage setting
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[storage.packages]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; storage type
;STORAGE_TYPE = local

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; customize storage
;[storage.my_minio]
;STORAGE_TYPE = minio
;;
;; Minio endpoint to connect only available when STORAGE_TYPE is `minio`
;MINIO_ENDPOINT = localhost:9000
;;
;; Minio accessKeyID to connect only available when STORAGE_TYPE is `minio`
;MINIO_ACCESS_KEY_ID =
;;
;; Minio secretAccessKey to connect only available when STORAGE_TYPE is `minio`
;MINIO_SECRET_ACCESS_KEY =
;;
;; Minio bucket to store the attachments only available when STORAGE_TYPE is `minio`
;MINIO_BUCKET = gitea
;;
;; Minio location to create bucket only available when STORAGE_TYPE is `minio`
;MINIO_LOCATION = us-east-1
;;
;; Minio enabled ssl only available when STORAGE_TYPE is `minio`
;MINIO_USE_SSL = false

;[proxy]
;; Enable the proxy, all requests to external via HTTP will be affected
;PROXY_ENABLED = false
;; Proxy server URL, support http://, https//, socks://, blank will follow environment http_proxy/https_proxy/no_proxy
;PROXY_URL =
;; Comma separated list of host names requiring proxy. Glob patterns (*) are accepted; use ** to match all hosts.
;PROXY_HOSTS =

电脑配置VHD启动缩小磁盘大小，不自动扩展

2023-03-09T13:25:24.000Z

简介
当系统启动时, 为了保证有足够的空间和防止数据损坏, 动态扩展VHD将扩大到其完整大小. 如果计算机无法分配足够的物理硬盘空间放置VHD, 它将会生成一个停止错误信息, 并且阻止操作系统继续启动.

当你只有一个VHD配置在计算机上时, 这通常不会出现问题. 然而, 当你有多个VHD时, 同时你不想使用VHD的所有空间时, 你可以通过调整注册表来阻止这种扩展. 有时候, 这也被称作”自动精简配置(thin provisioning)”.

这里有2中方式设置阻止动态扩展VHD扩展到完整大小. 第一种是启动到系统后修改注册表的方式, 另一种方式则进入Windows PE 后挂载VHD后修改系统组册表.

而这里只说明第一种设置方式, 第二种设置方式可以参考第一种方式操作.

设置方法
启动到系统后, 打开”运行”, 输入”regedit”(不包括双引号)命令打开注册表, 定位到 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\FsDepends\Parameters 项, 修改 VirtualDiskExpandOnMount 的16进制数值为4, 重启电脑后生效.
在这里插入图片描述

当然还可以使用直接导入的方式, 新建一个TXT记事本, 将以下内容拷贝到记事本, 保存后修改文件扩展名为”reg”, 双击导入注册表即可:

XMLRPC是什么及如何影响WordPress网站安全？

2023-03-09T13:24:20.000Z

xmlrpc.php文件存在于 WordPress 网站根目录中，本意是给网站提供一种远程通信方式，让其他应用程序与 json文件早了很多。

RPC 代表远程过程调用。也就是一个程序可以要求另外一个程序做事情。而现在使用 API调用代替了 RPC调用。

二、xmlrpc.php如何工作

向 xmlrpc.php发布一条信息，启动一个 post请求，把 xml文件传递上去，就可以在 WordPress 网站中完成发布文章、pingback 等操作，而无需登录 WordPress 后台，用起来很方便。

三、xmlrpc.php带来的安全问题

很长一段时间中，xmlrpc.php是一个挺有用的工具，记得很早之前羊毛之家也尝试一段时间利用 xmlrpc.php 远程发布文章，也蛮方便和有趣的。

随着 REST API的兴起，xmlrpc.php已经被代替了，但WordPress仍然保留着这个文件。很可能给网站带来一些安全风险，被利用来攻击 WordPress 网站。

3.1、XMLRPC 蛮力攻击

XMLRPC 攻击比较简单的方法是蛮力攻击。因为利用 XMLRPC 登录需要用户名和密码登录，因此攻击者可以很方便的不断组合用户名和密码，直到找到正确的。很多站长会限制用户登录尝试次数，但不会想到阻止 XMLRPC 请求，这就为攻击者提供了可趁之机。

一旦攻击者穷举登录成功，就可以随便把广告、链接、垃圾内容写入你的数据库。小白经常发现一些新手、小白的网站后台评论，平均都有几十~几千条，把数据库搞大了，越来越臃肿，网站打开速度就慢下来了。

3.2、XMLRPC 发起 DDoS 攻击

XMLRPC 的另外一种利用方法是 pingback，恶意用户同时发出大量请求来挂掉服务器。

pingback 不但能把大量垃圾信息写入你的数据库。而且同时数百~数千个 pingback 可以让服务器瘫痪。

这也就是俗称的 DDos（分布式拒绝服务攻击），通常是由分布在世界不同地方的大量肉鸡发起的。

四、禁用 XMLRPC

有多种方法可以禁用 XMLRPC，你要根据自己的实际情况来选择合适的方法。

4.1、如果你手动更新WordPress版本，那么就直接删除 xmlrpc.php，以后更新版本时也手动删除掉安装包里面的 xmlrpc.php。

这是最直接有效的方法。带来的弊端是你也无法使用远程发布文章功能了，当然绝大多数人根本用不到。

4.2、如果你用到了 xmlrpc.php ，就不能删除。对于 apache 服务或虚拟主机，可以把下列代码添加到网站根目录的 .htaccess 文件中。

order deny,allow

deny from all

这样就把任何想要利用 xmlrpc的攻击都拦截在外面了。

4.3、主题functions.php文件

如果不喜欢在 Web 服务中添加代码，也可以在主题的 functions.php 文件中添加下面的一行代码。

add_filter(‘xmlrpc_enabled’, ‘__return_false’);

看清楚了在单词 return 之前是 2 个下划线。这也能关闭 xmlrpc。

弊端是每次主题更新都要手动添加这段代码，但保不齐哪次就忘记了，所以小白并不推荐用这个办法。

4.4、如果不想在主题 functions.php 中添加代码，可以安装插件禁用 XMLRPC。比如常见的 Wordfence Security插件、WordPress 安全插件 All In One WP Security & Firewall、SiteGround Security插件都提供禁用功能。

也有一些专门禁用 XMLRPC的插件，其实就是主题functions.php文件的代码，插件不会因为更新主题就被覆盖掉，这个禁用功能也就能一直保持工作。

五、总结

XMLRPC 在很早之前提供了很好的服务，方便、快捷、好用。但现在用的人越来越少了，那么通过上述办法禁用来保护网站安全，是每个WordPress网站必须考虑的操作。

来源

Archlinux安装后注销、关机、重启卡死问题

2023-03-03T03:47:00.000Z

需要禁用nouveau

blacklist nouveau

并重新生成mkinitcpio镜像

Laravel数据转换typecho

2023-02-28T09:30:00.000Z

博客从Laravel自建换成了之前用的typecho，维护开发太累了，我也太懒了，下面是用ChatGPT生成的数据迁移后cid混乱的代码

-- 清除之前的自增数据
ALTER TABLE typecho_contents AUTO_INCREMENT = 1;

-- 按照modified字段中的时间戳从小到大进行排序，并以此排序对cid字段中的id从1开始排序
SET @new_cid := 0;
UPDATE typecho_contents SET cid = @new_cid := (@new_cid + 1) ORDER BY modified ASC;

拉取CODING代码突然出现：Permission denied (publickey).

2022-09-27T14:32:53.000Z

输入 ssh -T git@e.coding.net 会出现 Permission denied (publickey). 一开始以为密钥过期了，后来重新生成之后还是出现 Permission denied (publickey).

解决办法：
git的安装目录下有一个 ssh_config的文件用记事本打开

在文件的最下面，添加如下配置：

#Added by git-extra

Host *.coding.net
HostkeyAlgorithms +ssh-rsa
PubkeyAcceptedAlgorithms +ssh-rsa

保存关闭即可，在次输入：ssh -T git@e.coding.net

————————————————
版权声明：本文为CSDN博主「lo浅安灬时光ve」的原创文章，遵循CC 4.0 BY-SA版权协议，转载请附上原文出处链接及本声明。
原文链接：https://blog.csdn.net/qq_23118345/article/details/121938638

git clone本地为空目录

2022-09-27T14:30:08.000Z

步骤一 ：

git clone + 路径，显示是空文件夹~~~~

步骤二 ：

git checkout 分支名称

祝各位秃头 👩🏻‍🦲 小 baby，快乐…

1 . git clone +url ---- 只是要下载的项目而已（一般默认 master）

2 . 没有默认 master 的话，那就选分支---- 执行命令：git checkout 分支名称

ps：知道分支名称就直接写

本文来自博客园，作者：Song0916，转载请注明原文链接：https://www.cnblogs.com/song0916/p/15990083.html

Windows设置锁屏状态下超时时间

2022-03-17T14:35:10.000Z

添加控制面板选项（无法设置小于1min的值）

1、打开注册表编辑器；

2、导航到路径计算机\ HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Power \ PowerSettings \ 7516b95f-f776-4464-8c53-06167f40cc99 \ 8EC4B3A5-6868-48c2-BE75-4F3044BE88A7；

3、在右侧窗格中，单击“属性”键上的 2x。然后将其值更改为 2.如果单击确定以保存更改；

命令行设置（推荐）

powercfg.exe /setacvalueindex SCHEME_CURRENT SUB_VIDEO VIDEOIDLE \<time in seconds>

powercfg.exe /setacvalueindex SCHEME_CURRENT SUB_VIDEO VIDEOCONLOCK \<time in seconds>

powercfg.exe /setactive SCHEME_CURRENT

选项	参考解释
setacvalueindex	设置AC状态下
setdcvalueindex	设置DC状态下
VIDEOIDLE	桌面界面锁屏时间
VIDEOCONLOCK	锁屏界面锁屏时间
`<time in seconds>`	输入设置的秒速

激活你的配置

powercfg.exe /setactive SCHEME_CURRENT

之后重启电脑即可

参考：

1、Win10 系统下设置锁定屏幕超时的解决方法－系统城 (xitongcheng.com)

2、Read: How to change Lock Screen Timeout Period in Windows 11/10 (thewindowsclub.com)

3、Monitor powers off when computer is locked - Windows Client | Microsoft Docs

Windows 11加载iso慢的解决办法

2022-03-17T14:34:01.000Z

Windows 11 加载 iso 慢的解决办法
解决办法：加载应用或打开很慢时，关闭任务管理器里的 Microsoft defender smartScreen 程序马上加载。还可以在安全中心里左边打开应用与浏览器控制，再点击右边基于声誉的保护设置，关闭检查应用和文件就行，但是有一个问题每次打开都询问。

彻底解决办法：解除浏览器下载 iso 的“锁定”状态
每次用浏览器下载文件后，下载的文件属性都有个解除锁定，很麻烦，在windows11中打开浏览器下载的大文件如 win 系统的 iso 文件用很长时间，把文件里的注册表文件导入注册表再下载就没有了。已经下载的可以在属性里解除锁定，还可以运行：使用 PowerShell 批量解除锁定下载的文件.ps1，解除当前文件夹下下载的所有文件的锁定。

来源：Pcbeta

虎年快乐！

2022-01-31T17:17:58.000Z

新年快乐！

更换VditorCDN源时出现跨域问题

2022-01-01T06:25:28.000Z

最近不是CDN JSDeliver无了吗，，然后今天打开我的网站一看，好家伙，文章直接加载卡死，于是去上面把 dist文件夹给他下载下来了。

然后发现有个巨大的 323K 的 lute.min.js（也是这个最大，之前加载半天，导致文章渲染不了）然后换了之后发现只有 index.min.js改过来了而 lute.min.js并没有更换过来，然后通过代码分析

然后修改之后就发现

后台编辑文章的页面因为确实 ant.js而缺失元素

然后转到 index.min.js文件

发现是插入 js文件的时候跨域出现了问题

于是进入阿里云CDN更改跨域

遂解决。

2022新年快乐

2021-12-31T16:00:00.000Z

关于本博客

2021-12-15T04:07:55.000Z

这个博客是基于Laravel框架搭建的

手制版见我的Github 所以很多功能还需要慢慢添加

首页

待添加

美化
独立页面

Windows计划任务程序报错：2147943726 解決方法

2021-12-12T13:06:09.000Z

将用户改为 SYSTEM

记一次失误上传阿里云OSS AssessKey密钥的事情

2021-09-25T15:08:29.000Z

之前在修改后台上传的时候不小心直接用后台页面的AccessKey密钥，然后忘了修改从 .env文件

再来看看Js实现的后台上传代码

<div class="container">
<!-- 引入在线资源 -->
<script src="https://gosspublic.alicdn.com/aliyun-oss-sdk-6.8.0.min.js"></script>
<script>
const client = new OSS({
    // yourRegion填写Bucket所在地域。以华东1（杭州）为例，Region填写为oss-cn-hangzhou。
    region: 'oss-cn-shanghai',
    // 从STS服务获取的临时访问密钥（AccessKey ID和AccessKey Secret）。
    accessKeyId: '<?php echo env("ALIYUN_ACCESS_ID"); ?>',
    accessKeySecret: '<?php echo env("ALIYUN_ACCESS_KEY"); ?>',
    // 填写Bucket名称。
    bucket: 'assets-xyz-blue'
});
</script>            
<a href="javascript:void(0)" onclick="uploadPhoto()">选择图片</a>
<input type="file" id="photoFile" style="display: none;" onchange="upload()">
<script>
    function uploadPhoto() {
        $("#photoFile").click();
    }

    /**
     * 上传图片
     */
    function upload() {
        if ($("#photoFile").val() == '') {
            return;
        }
        // var CTime = Math.round(new Date());
        // var formData = new FormData();
        // formData.append('photo', document.getElementById('photoFile').files[0]);
        const data = document.getElementById('photoFile').files[0];
        // var FileName = document.getElementById('photoFile').files[0].name
        async function put () {
            try {
                // object表示上传到OSS的文件名称。
                // file表示浏览器中需要上传的文件，支持HTML5 file和Blob类型。
                var now = new Date();
                month = now.getMonth();
                month = month + 1;
                if (month < 10) month = "0" + month;
                var filename = 'attachments' + '/' + now.getFullYear() + '/' +  month + '/' + now.getTime() + '.' + data.name.split(".")[1];
                const r1 = await client.put(filename, data);
                var link = "<?php if (env('ASSETS_URL') !== '') { echo env('ASSETS_URL'); } ?>" + '/' + filename;
                content = "<img src='"+ link +"' alt=" + data.name +">";
                window.vditor.insertValue(content);
                console.log('put success: %j', r1);
            } catch (e) {
                console.error('error: %j', e);
            }
        }
        put();
        // formData.append('time', CTime);
        // $.ajax({
        //     url:"<?php echo env('APP_URL') ?>/admin/upload",
        //     type:"post",
        //     async: false,
        //     data: formData,
        //     contentType: false,
        //     processData: false,
        //     success: function(data) {
        //         if (data !== '') {
        //             content = "<img src='"+ data +"' alt=" + FileName +">";
        //             window.vditor.insertValue(content);
        //         }
        //     },
        //     error:function(data) {
        //         alert("上传失败")
        //     }
        // });
        // let content = this.vditor.getValue();
        // content = "<img src='/storage/"+ CTime +".png'>";
        // this.vditor.insertValue(content);
    }
</script>

或者数据库获取密钥，然后今天在修改完Navbar忘记了。一兴奋直接就一连串 git commit git push然后提交完了，我还在思考那个 views的怎么设置，然后我竟然收到了阿里云的短信

紧接着就是就是阿里云和Github/Gitguardian的邮件通知

Centos(Grub)云服务器安装ArchLinux

2021-09-18T15:41:07.000Z

新建磁盘这里以腾讯云为例

只要满足镜像大小即可

挂载并下载镜像

编辑启动文件 /etc/grub.d/40_custom以实际为准

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
menuentry "Archboot" --class iso {
  set label=ARCH_202106
  set isofile='/archlinux-2021.06.01-x86_64.iso'
  loopback loop (hd0,gpt2)$isofile
  linux (loop)/arch/boot/x86_64/vmlinuz-linux archisolabel=$label img_dev=/dev/vdb1 img_loop=$isofile earlymodules=loop
  initrd (loop)/arch/boot/x86_64/initramfs-linux.img
}

具体以实际镜像、磁盘号、硬盘UEFI/MBR 为准

别忘了更新 Grub

重启

选择启动项即可

ArchLinux使用php-redis启用失败

2021-09-18T15:22:55.000Z

Redis

Install and configure Redis, then install php-redis.

Uncomment the line of the package, e.g. /etc/php/conf.d/redis.ini. Also ensure that the igbinary extension is enabled (also uncommented) in /etc/php/conf.d/igbinary.ini

PHP - ArchWiki (archlinux.org)

Win11 DEV版任务栏空白

2021-09-03T04:50:52.000Z

今天早上打开电脑，大概是8:00左右，在未更新的情况下直接打开出现状态栏空白，uwp应用无法打开的情况然后我去 酷安、贴吧、rabbit看了之后说是要卸载更新，但是我试了下，直接提示卸载不了，进入 /r /o恢复模式也不行，然后过一段时间后，看见有人说恢复还原点可以，于是我试了一下，发现正好有一个9月2号的还原点，正好是昨天更新之后（不得不说win10更新自动创建还原点这个设计还是不错的）恢复之后就正常了，于是不信邪想着更新那个最新的 DEV版，正在更新时候就看见说是微软授时服务器出现问题，然后，幸好没像某些人一样，直接放弃重装系统😂😂😂

看见IThome 赛文奥特曼的一个评论挺有意思的

if ( Datetime.Now < new datetime(2021,9,4) ) {
    Taskbar.broken();
}

笑死

增加博客直接上传腾讯云COS功能

2021-09-02T16:06:35.000Z

最近发现如果要转移数据到另一台服务器，特别麻烦，不仅需要 git clone还需要拷贝 storage相关文件、还有 .env文件，所以将文件直接上传至腾讯云COS是一个不错的选择

MariaDB删除账号测试

2021-08-19T12:19:13.000Z

删除内置 mariadb.sys账户（初始为 USAGE权限）后无其他问题，但是 phpmyadmin无法显示和编辑用户，添加授予任意一项权限后正常
删除内置 mysql账户后暂时无明显异常

phpmyadmin安装后显示空白页面

2021-08-19T12:17:50.000Z

启用 iconv和 mysqli扩展即可

第一篇日记2021/08/15

2021-08-15T04:53:40.000Z

第一篇日记2021/08/15

开发了博客分类栏目

Linux截图无法获取最新画面

2021-08-04T05:44:32.000Z

环境：KDE

截图一直出现微风的启动加载画面，或者就是一些过时的桌面屏幕

经过我百般搜索百度、CSDN、StackOverflow、Google等等

最终在Arch论坛里面发现了解决方案

他的标题是 Spectacle Screenshot uses old screen state

恩，一样的问题

解决方案

If installed, remove xf86-video-intel, reboot and retry. ---By V1del
如果安装了 xf86-video-intel请移除，重启后再试一次。

分享一张有趣的图片-1

2021-07-24T14:04:05.000Z

我的英语功底太薄，无法翻译此处，请期待其他翻译人员来翻译吧。

其实那个英文版掉了一个词 fstab-entry现在给加上了

Arch查看某个命令属于那个软件包

2021-07-24T13:54:46.000Z

事情的原因是这样的

我看见

 /usr/bin/vglrun: 第 251 行：exec: microsoft-edge-dev-bin：未找到

出现错误了，于是想去找他软件包

我但是以为这个就是那个软件包的名称

结果

我先到 AUR源去找 …没有找到

然后去 Package里面找

仍然没有找到于是我想到能不能通过文件来搜索软件包了？

于是，我去百度，发现果然有人跟我有一样的想法～

来看看来自灰信网的解决方案

pacman -Fl | grep command

机智

最终成功找到！

CrossOver输入密钥时显示注册失败

2021-07-20T07:00:00.000Z

`root`权限修改文件

修改 /opt/cxoffice/lib/python/demoutils.py这个文件

将第250行修改为如下：

request = urllib_request.Request(URL, request_body.encode("utf-8"), header)

将第253行修改如下：

responseBuffer = response.read().decode("utf-8")

来自：CodeWeavers社区

Archlinux使用人脸识别登录

2021-07-19T10:02:49.000Z

使用 Howdy

一、安装 `Howdy`

yay -S howdy

二、配置

输入命令

sudo howdy config

修改配置文件

选择你的摄像头设备

device_path = /dev/video0

禁用 confirmation信息

no_confirmation = true

编辑 /etc/pam.d/system-auth

在最上面添加

auth sufficient pam_python.so /lib/security/howdy/pam.py

如图所示添到最上面

最后赋权

sudo chmod -R 755 /lib/security/howdy/

即可享受所有输入密码的位置均可人脸识别！！！

参考文件:

Howdy_Archlinux_Wiki && Githu_Issue_For_Howdy

Jquery页面加载完成时的判断

2021-07-03T13:59:40.000Z

最近在弄Blog图片懒加载，发现要等那个js文件加载完，在运行一段js脚本才能实现功能，于是想到此方法，即检测页面加载情况然后运行相关代码

以下为判断页面是否加载完成的代码

<script type='text/javascript'>

　　window.onload = function(){
　　　　alert("页面加载完成====》onload");
　　}

　　$(window).load(function(){
　　　　alert("jquery===》window load" );
　　})

　　$(document).ready(function () {
　　　　alert("jquery====》document ready");
　　});

　　$(function(){
　　　　alert("jquery====》document onload");
　　});

　　function aaa(){
　　　　alert("静态标签====》onload");
　　}

</script>

摘自忆飞雪

解决Win10预览体验计划界面为空

2021-06-24T11:38:35.000Z

打开 Powershell输入以下代码

$path = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection"
# Telemetry level: 1 - basic, 3 - full
$value = "3"
New-ItemProperty -Path $path -Name AllowTelemetry -Value $value -Type Dword -Force
New-ItemProperty -Path $path -Name MaxTelemetryAllowed -Value $value -Type Dword -Force

重启即可

如果不行则是该注册表权限出现问题

Win+R打开 regedit

找到

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\DataCollection

在左栏中右键该项

点击权限-高级设置

将 Owner设置为 SYSTEM（如果它不是的话）

然后点击禁用继承

然后同意后再点击启用

重启即可

解决使用Webpack打包Awesome-fonts时Can't resolve '../webfonts/fa-regular-400.eot'

2021-06-24T11:18:11.000Z

在使用 Webpack过程中你可能会遇到以下情况

经过查找stackoverflow和Github-vuejs-templates-webpack与Github-JeffreyWay-laravel-mix

$fa-font-path: '~@fortawesome/fontawesome-free/webfonts';
@import '@fortawesome/fontawesome-free/scss/fontawesome';
@import '@fortawesome/fontawesome-free/scss/solid';
@import '@fortawesome/fontawesome-free/scss/regular';
@import '@fortawesome/fontawesome-free/scss/brands';
@import '@fortawesome/fontawesome-free/scss/v4-shims';

修改后发现

但是我知道他上一个问题已经解决了

这个是新的一个问题：Webpack无法解析 woff2 eot svg等等文件

于是修改 Webpack.config.js文件

在 module->rules下添加

{
    test: /\.(ttf|eot|svg|gif|woff|woff2)(\?v=[0-9]\.[0-9]\.[0-9])?$/,
    use: [{
        loader: 'file-loader',
    }]
},

然后重新打包

看到这满屏绿，我就知道这个问题解决了！

解决 gpg: key xxx: no user ID for key signature packet of class 10

2021-06-24T11:07:55.000Z

有些 keyserver过时了需要更新，遂改变为其他 keyserver

nano /etc/pacman.d/gpg.conf

keyserver hkps://pgp.circl.lu

如果你安装了 yay或者其他 AUR Helper需要去导入 key你可以按照一下方法来操作

mkdir -p ~/.gnupg/
vi ~/.gnupg/gpg.conf

之后添加

keyserver hkps.pool.sks-keyservers.net

artixlinux.org论坛

后台上传图片初步完成

2021-06-20T09:23:19.000Z

Typecho之BaiduSubmit插件（四）

2021-02-08T07:22:00.000Z

已经发布到Github：BaiduSubmit

目前只实现了后台提交链接功能 0.0.1

下一步

将实现页面链接显示及按钮提交功能

Typecho之BaiduSubmit插件（三）

2021-02-08T07:02:00.000Z

本来百度原本就提供自动推送js，但是不知道为什么他就把他关了，而写个js用处也不是太大。）~~主要还是想自定义一个美丽的站点地图~~测试一些自己的能力

然后中途就遇到了一些问题

1.列表过长，需要设置分页

尝试了一下这个没成功。。。

2.Typecho路由设置

/**
 * 增加路由
 *
 * @access public
 * @param string $name 路由名称
 * @param string $url 路由路径
 * @param string $widget 组件名称
 * @param string $action 组件动作
 * @param string $after 在某个路由后面
 * @return integer
 */
public static function addRoute($name, $url, $widget, $action = NULL, $after = NULL)
{
// some code here...

[collapse status=“false” title=“思否-老高@PHPer”]

获取配置

# 获取系统配置
Helper::options();

# 获取指定插件配置
Helper::options()->plugin('BaiduSubmit');

# 获取当前插件配置
Helper::options()->plugin(str_replace('_Plugin','',__CLASS__));

路径安全

用于生成安全的URL，带有token验证，如果牵扯到action等核心操作时会用到。系统在验证请求是会用到 $this->widget('Widget_Security')->protect()去验证来源token。

$s = Helper::security();
echo $s->index('/');

# 输出类似 http://www.phpgao.com/?_=ce4a9617aa228bb85ba696c9ba9784be

强行删除某插件

此方法用于卸载插件失败时的替补方法，老高一般将此方法写入 HELLO_WORLD插件的 render方法里，这样刷新以下后台，出问题的插件就被卸载了。

Helper::removePlugin('BaiduSubmit');

路由增删

如果你的插件需要给系统添加一个新的路由，那么此方法就能派上用场！

路由表保存在表 typecho_options 中的 routingTable中。

比如老高的插件BaiduSubmit，就用此方法为系统添加了一个 http://yourweb/baidu_sitemap.xml的路由。

/**
 * 增加路由
 *
 * @access public
 * @param string $name 路由名称
 * @param string $url 路由路径
 * @param string $widget 组件名称
 * @param string $action 组件动作
 * @param string $after 在某个路由后面
 * @return integer
 */
Helper::addRoute('baidu_sitemap', '/baidu_sitemap.xml', 'BaiduSubmit_Action', 'sitemap');

不要忘记在卸载的时候调用 Helper::removeRoute('baidu_sitemap');删除刚才添加的路由！

Action

有心的同学应该能够发现，后台发送文章的form表单的action地址为类似 http://web/action/contents-post-edit?_=xxx，这个链接表示什么意思呢？请听老高分解！

Action是typecho中的一类操作，它对应一条特殊的路由/action/，也就是路由表中的 $table[0]['do']，具体内容如下

 [do] => Array
(
        [url] => /action/[action:alpha]
        [widget] => Widget_Do
        [action] => action
        [regx] => |^/action/([_0-9a-zA-Z-]+)[/]?$|
        [format] => /action/%s
        [params] => Array
            (
                [0] => action
            )

    )

从路由表能够看出，下一步我们需要找到类 Widget_Do。我们能在该类中找到系统默认的action对应关系！

    private $_map = array(
        'ajax'                      =>  'Widget_Ajax',
        'login'                     =>  'Widget_Login',
        'logout'                    =>  'Widget_Logout',
        'register'                  =>  'Widget_Register',
        'upgrade'                   =>  'Widget_Upgrade',
        'upload'                    =>  'Widget_Upload',
        'service'                   =>  'Widget_Service',
        'xmlrpc'                    =>  'Widget_XmlRpc',
        'comments-edit'             =>  'Widget_Comments_Edit',
        'contents-page-edit'        =>  'Widget_Contents_Page_Edit',
        'contents-post-edit'        =>  'Widget_Contents_Post_Edit',
        'contents-attachment-edit'  =>  'Widget_Contents_Attachment_Edit',
        'metas-category-edit'       =>  'Widget_Metas_Category_Edit',
        'metas-tag-edit'            =>  'Widget_Metas_Tag_Edit',
        'options-discussion'        =>  'Widget_Options_Discussion',
        'options-general'           =>  'Widget_Options_General',
        'options-permalink'         =>  'Widget_Options_Permalink',
        'options-reading'           =>  'Widget_Options_Reading',
        'plugins-edit'              =>  'Widget_Plugins_Edit',
        'themes-edit'               =>  'Widget_Themes_Edit',
        'users-edit'                =>  'Widget_Users_Edit',
        'users-profile'             =>  'Widget_Users_Profile'
    );

由此映射关系我们知道，当我们需要发布文章的时候（contents-post-edit），就去调用 Widget_Contents_Post_Edit的action方法即可。

当我们要添加action对应关系的时候，就可以调用 Helper:addAction()执行添加，系统就会添加一条 'new_action' => 'some_action'。

新增的动作保存在表 typecho_options 中的 actionTable中。

需要提醒的是，当我们添加一条action后，需要让其实现类 some_action实现 Widget_Interface_Do的接口，即必须有实现 public function action()，否则调回失败。

同route一样，在卸载插件时不要忘了移除action！

菜单 & 面板

这个很好理解，不再赘述。

手动配置

当我们需要更自由的配置功能时，可以在Plugin.php文件中添加 public static function configHandle($config)方法，当后台保存插件设置的时候就会调用此方法而不是默认的简单保存配置。

helper::configPlugin('BaiduSubmit', $config);

[/collapse]

3.Typecho 插件的配置信息没有找到

将 ____Class____改为插件名称

[collapse status=“false” title=“Moleft”]

解决 Typecho 插件的配置信息没有找到

避免踩坑展开目录

入坑 Typecho 已经一个多月了，在这期间 Typecho 的插件也开发了两个 (其实我现在正在开发第三个，就不告诉你是个采集插件)，然后大大小小的坑也踩了不少，其实最深的坑还是启用插件时提示 “插件的配置信息没有找到”，这个具体原因就是因为首次启用插件时，在 config() 里面获取配置信息，这当然是获取不到的，我们复现一个这个错误。

先写插件展开目录

在写一个插件肯定是没那个精力了，我们就稍微改一下官方的 HelloWorld 插件吧，首先我们先启用报错，在 Plugins.php 最上面加入下面的代码，这样的话我们就可以看到错误信息了，不然就是 Server Error

define('__TYPECHO_DEBUG__', true);

然后我们找到 config 这个函数，复现一下具体错误，我们加一个获取插件配置的代码，然后保存。

$setting = $options = Typecho_Widget::widget('Widget_Options')->plugin('HelloWorld');
echo "<script>alert(\"{$setting->word}\")</script>";

然后我们启用一下插件，看看会不会报错。

果不其然，真的报错了，有的时候在 config() 函数里面获取配置信息是为了更好的显示插件的某些配置，所以说这个对我们来说真的很重要，经过我多方摸索，最后找到了解决办法。

如何解决展开目录

其实解决方法也是灰常简单的，只需要加一个捕捉异常，就可以跳过这个坑 (傻傻的我为什么早没有想到呢)，我们来修改一下代码，我们加一个 try catch，保存之后在重新启用插件。

try {
    $setting = $options = Typecho_Widget::widget('Widget_Options')->plugin('HelloWorld');
    echo "<script>alert(\"{$setting->word}\")</script>";
} catch (Exception $e) {
    echo "<script>alert(\"获取配置失败\")</script>";
}

重新启用插件之后果然没有报错，所以说这个方法是可行的，其他的思路我暂时没有，如果你们有好的方法可以在下面评论。

[/collapse]

4. function static

action不能使用static

Typecho之BaiduSubmit插件（二）

2021-02-08T06:51:00.000Z

在研究了

寒泥的sitemap插件

$pages = $db->fetchAll($db->select()->from('table.contents')
        ->where('table.contents.status = ?', 'publish')
        ->where('table.contents.created < ?', $options->gmtTime)
        ->where('table.contents.type = ?', 'page')
        ->order('table.contents.created', Typecho_Db::SORT_DESC));

        $articles = $db->fetchAll($db->select()->from('table.contents')
        ->where('table.contents.status = ?', 'publish')
        ->where('table.contents.created < ?', $options->gmtTime)
        ->where('table.contents.type = ?', 'post')
        ->order('table.contents.created', Typecho_Db::SORT_DESC));

        foreach($pages AS $page) {
            $type = $page['type'];
            $routeExists = (NULL != Typecho_Router::get($type));
            $page['pathinfo'] = $routeExists ? Typecho_Router::url($type, $page) : '#';
            $page['permalink'] = Typecho_Common::url($page['pathinfo'], $options->index);
        }
        foreach($articles AS $article) {
            $type = $article['type'];
            $article['categories'] = $db->fetchAll($db->select()->from('table.metas')
                    ->join('table.relationships', 'table.relationships.mid = table.metas.mid')
                    ->where('table.relationships.cid = ?', $article['cid'])
                    ->where('table.metas.type = ?', 'category')
                    ->order('table.metas.order', Typecho_Db::SORT_ASC));
            $article['category'] = urlencode(current(Typecho_Common::arrayFlatten($article['categories'], 'slug')));
            $article['slug'] = urlencode($article['slug']);
            $article['date'] = new Typecho_Date($article['created']);
            $article['year'] = $article['date']->year;
            $article['month'] = $article['date']->month;
            $article['day'] = $article['date']->day;
            $routeExists = (NULL != Typecho_Router::get($type));
            $article['pathinfo'] = $routeExists ? Typecho_Router::url($type, $article) : '#';
            $article['permalink'] = Typecho_Common::url($article['pathinfo'], $options->index);
        }

和有后台页面mrasong的插件源码后

public static function config(Typecho_Widget_Helper_Form $form){
        preg_match("/^(http(s)?:\/\/)?([^\/]+)/i", Helper::options()->siteUrl, $matches);
        $domain = $matches[2] ? $matches[2] : '';
        $site = new Typecho_Widget_Helper_Form_Element_Text('site', NULL, $domain, _t('站点域名'), _t('站长工具中添加的域名'));
        $form->addInput($site->addRule('required', _t('请填写站点域名')));

        $token = new Typecho_Widget_Helper_Form_Element_Text('token', NULL, '', _t('准入密钥'), _t('更新密钥后，请同步修改此处密钥，否则身份校验不通过将导致数据发送失败。'));
        $form->addInput($token->addRule('required', _t('请填写准入密钥')));
    }

思路已经初步形成

首先需要获取网站的站点地图

配置路由页面

将站点地图以表格的形式列出

~~在后面添加检测是否在百度的php~~

// public function action(){
    //     function baidu_record($a) {
    //         //$url='http://'.$_SERVER['HTTP_HOST'].$_SERVER['REQUEST_URI']; 
    //         $url=$a;
    //         if(checkBaidu($url)==1) {
    //             echo "百度已收录";
    //         }
    //         else {
    //             echo "<a style=\"color:red;\" rel=\"external nofollow\" title=\"点击提交收录！\" target=\"_blank\" href=\"http://zhanzhang.baidu.com/sitesubmit/index?sitename=$url\">百度未收录</a>";
    //         }
    //     }
          
    //     function checkBaidu($url) { 
    //         $url = 'http://www.baidu.com/s?wd=' . urlencode($url); 
    //         $curl = curl_init(); 
    //         curl_setopt($curl, CURLOPT_URL, $url); 
    //         curl_setopt($curl, CURLOPT_RETURNTRANSFER, 1); 
    //         $rs = curl_exec($curl); 
    //         curl_close($curl); 
    //         if (!strpos($rs, '没有找到')) { //没有找到说明已被百度收录 
    //             return 1; 
    //         } else { 
    //             return -1; 
    //         }
    //     }

但是发现这个可能会对服务器ip造成不好的影响，比如，如果不设置一些header，百度就会禁止你浏览，而返回一个验证链接。甚至会被列入黑名单！

https://wappass.baidu.com/static/captcha/tuxing.html

然后在每条链接后面设置提交按钮

Typecho之BaiduSubmit插件（一）

2021-02-08T06:40:00.000Z

开始

在网上找了一圈都没有发现自己想要的插件功能

有的就是：后台每提交一次，发送一次

于是想自己开发一个插件

功能

后台页面提交链接
可以手动指定提交某些链接
支持新发文章提交链接
可以查看已提交和百度已收录的列表

链接	提交	收录
1	1	1
1	1	1

Windows10 蓝牙鼠标能连上动不了

2021-02-08T03:04:00.000Z

打开所有控制面板项窗口，点击窗口中的“疑难解答”图标。

在打开的疑难解答设置页面中，点击“硬件和声音”图标。

在打开的新窗口中，点击“蓝牙”一项的快捷链接。

这时会打开“解决并帮助解决计算机问题”的窗口，点击下一步按钮

一般这种情况，都是蓝牙收发器的问题

最后处理好后点完成，就可以正常愉快使用了

Linux 锁定文件

2021-01-22T12:09:00.000Z

Linux - 锁定文件

锁定关键的系统文件可以防止服务器提权后被篡改

对启动文件和账号密码文件进行加锁

1	[root@sch01ar ~]“# chattr +i /etc/passwd /etc/shadow /etc/group /etc/gshadow /etc/inittab

这些文件上锁后，任何用户都不能对这些文件进行修改和删除

root 用户强制保存退出也不行

如果想对这些文件进行操作的话，可以先对这些文件解锁，修改后再加锁

对这些文件解锁

1	[root@sch01ar ~]“# chattr -i /etc/passwd /etc/shadow /etc/group /etc/gshadow /etc/inittab

可以把 chattr 改名，防止被黑客利用

1	[root@sch01ar ~]“# mv /usr/bin/chattr /usr/bin/test

记一次被阿里云聆听平台采纳意见的过程

2021-01-22T07:25:00.000Z

原文

【需求场景】添加域名证书

【使用问题】

添加域名证书时，

①只能使用RSA的无法使用ECC加密算法（而阿里云云盾的证书支持ECC加密算法)

②添加RSA证书私钥时开头结尾必须

为

-----BEGIN RSA PRIVATE KEY-----

-----END RSA PRIVATE KEY-----

而不是

-----BEGIN PRIVATE KEY-----

-----END PRIVATE KEY-----

而目前SSL申请机构有较大一部分对于RSA的私钥格式是使用的下面这种格式

【改进建议】

①添加支持ECC证书的功能

②对证书格式和内容进行兼容或识别等

之后就有了某个邮件然后

Windows 10 调整虚拟键盘大小

2021-01-20T15:07:00.000Z

新建下列注册表键值，数字越大，键盘越小，设置40后大小如上图所示；重启电脑后生效。

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Scaling]
"MonitorSize"="40"

点击下载注册表文件

效果预览：

PHP中cURL的curl_getinfo函数返回的CURLINFO_HTTP_CODE是0

2021-01-20T13:28:00.000Z

PHP中cURL的curl_getinfo函数返回的CURLINFO_HTTP_CODE是0

分类专栏： PHP 文章标签： php curl httpCode 状态码

分析

在PHP中使用cURL获取网页时，可以通过函数curl_getinfo()来获取http状态码。

$httpCode = curl_getinfo($ch, CURLINFO_HTTP_CODE);1

我们期望的状态码是200，而且HTTP标准也对其它状态码做了一些定义。

总体范围	已定义类别	类别
100~199	100~101	信息
200~299	200~206	成功
300~399	300~305	重定向
400~499	400~415	客户端错误
500~599	500~505	服务端错误

但是curl_getinfo()有时候会给我们返回状态是0的状态码，原因如下，

如果你已经连接到服务器上了，那么你将会返回一个状态码；否则，将会失败并返回一个0。

所以，如果你连接到www.google.com/lksdfk时，你会收到一个400的状态码，如果你连接到google.com，你会收到一个302的状态码（如果继续访问的话，将会收到200的状态码，因为被重定向到了www.google.com.hk）,如果你访问googlecom，你会收到一个0状态码，并提示找不到host。

错误的详细原因可以通过函数curl_error()进行查询。

参考

PHP cURL HTTP CODE return 0
HTTP权威指南

(https://blog.csdn.net/u012314976) 2016-08-01 14:24:18

Windows显示时间秒数

2021-01-20T11:24:00.000Z

在注册表中定位到

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced

在空白处右击，选择新建

【DWORD（32位）值】

将新建值的名称改为

ShowSecondsInSystemClock

并双击编辑数值数据，将其改为 1，点击确定。重启生效

KodCloud使用阿里云oss的时候使用内网访问

2021-01-16T15:40:30.000Z

在./config/setting_user.php中配置参数，使上传下载都走服务器端（也就是实现走内网）

$config['settings']['ioFileOutServer'] = true;
$config['settings']['ioUploadServer'] = true;

搭建IE（IE8、IE9、IE10、IE11）兼容性测试环境

2021-01-16T12:11:00.000Z

搭建IE（IE8、IE9、IE10、IE11）兼容性测试环境

小鱼儿游啊悠 2016-11-10 13:23:18 21503 收藏

分类专栏：技术文章文章标签： ie 8 ie 9 ie 10 ie 11 兼容性测试

版权

背景

虽然IE的最后一个版本IE11已经发布了三年之久，且win10也默认了Edge浏览器，但现在IE的份额依然排在第二位，web开发不得不考虑几个版本IE的兼容性效果。
虽然一些浏览器插件支持模拟，也有类似IEtester之类的工具，但都算不上原汁原味的IE。

注：图片引自http://liulanmi.com/top/11618.html，2016年8月份的数据

方案

下面要说的是通过安装虚拟机来使用不同版本的IE。
每个虚拟机都是安装了某个IE版本的windows系统，所以要测试几个IE版本，就得下载几个虚拟机文件。

安装virtualbox：virtualbox官网
下载IE虚拟机：下载地址微软官网
导入虚拟机并使用：
- 打开virtualbox，点击管理-导入虚拟电脑
- 选择下载好的虚拟机文件（open virtual format archive格式）
- 不需要勾选（重新初始化所有网卡的MAC地址）
- 点击导入，等待几分钟，导入完成后，虚拟机便出现在列表中
- 选择并启动虚拟机即可。
注意点：虚拟机有使用期限，所以虚拟机文件注意有个原始的备份，一旦过期了再使用原始的虚拟机文件即可，这是微软官方的建议。

关于一次投诉钓鱼网站滥用域名的历程

2021-01-11T15:57:00.000Z

发件人:  abuse<abuse@west.cn>;

日期:  2021-01-11 (星期一) 10:00:49;

收件人:  Kylin<support@xyz.blue>;

------------------您好，

dfgdgf.top 域名已关停。

------------------ 原始邮件 ------------------

发件人:  Kylin<support@xyz.blue>;

日  期:  2021-01-10 (星期日) 12:51:44

收件人:  abuse<abuse@west.cn>;

主  题:  域名滥用投诉 dfgdgf.top

你好，成都西维数码科技有限公司：

贵公司注册的dfgdgf.top域名存在滥用情况，请处理！

Domain Name: dfgdgf.top

Registry Domain ID: D20201207G10001G_52900032-top

Registrar WHOIS Server: whois.west263.com

Registrar URL: www.west263.com

Updated Date:

Creation Date: 2020-12-07T07:13:02Z

Registry Expiry Date: 2021-12-07T07:13:02Z

Registrar: Chengdu west dimension digital

Registrar IANA ID: 1556

在其www.dfgdgf.top,jdkdj.dfgdgf.top等所有子域名页面为虚假腾讯邮箱登陆页面。

![虚假邮箱图片](images/2620202962.jpg)

存在 在电脑端引导用户输入QQ帐号密码; 在手机端存在引导用户输入手机号QQ密码的情况

提交 http://www.dfgdgf.top/ajax.php?u=QQ号&p=QQ密码&t=手机号

利用伪造的 Web 站点来进行网络诈骗活动，存在大量非法获得的公民个人信息。

希望贵公司处理

谢谢！

webdav适配调整: 允许http,文件大小限制50m变更为2G

2021-01-03T12:15:33.000Z

在KodCloud中发现

:: webdav适配调整: 允许http,文件大小限制50m变更为2G)
:: reg help: https://www.cnblogs.com/byron0918/p/4832556.html; 
:: change https://tool.oschina.net/hexconvert/;

@echo off
cls
echo 
echo change webdav(allow http,fileSizeLimit 50M to 2G)

net stop webclient
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters /f /v BasicAuthLevel /t reg_dword /d 2 
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters /f /v FileSizeLimitInBytes /t reg_dword /d 4294967295
net start webclient

mshta vbscript:msgbox("webdav apply success")(window.close)

一件修改WebDav文件

DzzOffice的Caddy文件备份

2021-01-02T12:11:00.000Z

cloud.xyz.blue {
    #reverse_proxy * localhost:5212
    header {
        Strict-Transport-Security "max-age=63072000; includeSubDomains; preload"
    }
    root * /www/wwwroot/cloud.xyz.blue
    tls /etc/caddy/tls/xyz.blue/fullchain.pem /etc/caddy/tls/xyz.blue/privkey.pem
    php_fastcgi * 127.0.0.1:11172
    file_server

    @key0 {
     not file 
     path_regexp key0 'wopi\/files\/(\w+)\/contents(.*)' 
    }
    rewrite @key0 core/api/wopi/index.php?action=contents&path={re.key0.1}&{re.key0.2}
    @key1 {
     not file 
     path_regexp key1 'wopi\/files\/(\w+)\/(lock|unlock)(.*)' 
    }
    rewrite @key1 core/api/wopi/index.php?action={re.key1.2}&path={re.key1.1}&{re.key1.3}
    @key2 {
     not file 
     path_regexp key2 'wopi\/files\/(\w+)(.*)' 
    }
    rewrite @key2 core/api/wopi/index.php?path={re.key2.1}&{re.key2.2}
    @key3 {
     not file 
     path_regexp key3 'wopi\/files\/(.*)' 
    }
    rewrite @key3 core/api/wopi/index.php?{re.key3.1}
    @key4 {
     not file 
     path_regexp key4 'dingredirect\/(\w+)' 
    }
    rewrite @key4 index.php?mod=dingtalk&op=dingredirect&url={re.key4.1}


}

Typecho生成静态首页文件，提高网站打开速度

2020-12-20T09:59:00.000Z

按照以下来操作
在网站的根目录下

<?php
$nowtime=time();
$pastsec = $nowtime - $_GET["t"];
if($pastsec<600)
{
exit; //10分钟更新一次，时间可以自己调整
}
ob_start(); //打开缓冲区
include("index.php");
$content = ob_get_contents(); //得到缓冲区的内容
$content .= "\n<script language=javascript src=\"jingtai.php?t=".$nowtime."\"></script>"; //加上调用更新程序的代码

file_put_contents("index.html",$content);
if (!function_exists("file_put_contents"))
{
function file_put_contents($fn,$fs)
{
$fp=fopen($fn,"w+");
fputs($fp,$fs);
fclose($fp);  
}
}
?>

并访问这个文件之后会生成一个 index.html 文件并在文件末尾出现 script 标签并附带一个时间戳,当访问同 index.html的时候会加载这个 script 标签并访向一次index.php这个访问时会获取一次当前时间,如果和传递进来的参数相比时间大于设置的600秒就会刷新一次

缺点:如果是将nginx/ Apache / caddy 的默认页面设置为html优先，通过首页点击文章页面无法正常跳转,无法配合 Handsome 的pjax

[collapse status=“false” title=“来自 SunPma”]

https://sunpma.com/484.html

介绍

最近感觉博客打开速度慢了不少，测试来看均值基本都在3秒以上，因为博客上有不少的 CSS和 JS加载速度也就慢了下来，并且本博客没有做图站分离，都是放在一起的，速度确实较慢；
于是给首页做了个静态 HTML，首页打开速度确实提升了数倍，需要的朋友也可以试试；
未做静态HTML前的打开测试

生成静态HTML后的打开测试

对比可以看出提升确实比较大，从均值3.5秒提升到了1秒以内，相当满意了；

开始

这里提供两个 PHP代码脚本，一个是不需要密码的，一个是需要密码的；
首先在网站根目录新建一个 php文件，文件命名为：jingtai.php
然后在其中写入需要的代码（不需要密码和需要密码的选择其中一个即可）
不需要密码的PHP脚本

<?php
$nowtime=time();
$pastsec = $nowtime - $_GET["t"];
if($pastsec<600)
{
exit; //10分钟更新一次，时间可以自己调整
}
ob_start(); //打开缓冲区
include("index.php");
$content = ob_get_contents(); //得到缓冲区的内容
$content .= "\n<script language=javascript src=\"jingtai.php?t=".$nowtime."\"></script>"; //加上调用更新程序的代码

file_put_contents("index.html",$content);
if (!function_exists("file_put_contents"))
{
function file_put_contents($fn,$fs)
{
$fp=fopen($fn,"w+");
fputs($fp,$fs);
fclose($fp);  
}
}
?>

需要要密码的PHP脚本

<?php
/**
 * 首页静态化脚本
 */
ini_set( 'date.timezone', 'PRC' );

/* 缓存过期时间 单位：秒 */
$expire = 600;
/* 主动刷新密码  格式：https://你的域名/jingtai.php?password=123456 */
$password = '123456';
$file_time = @filemtime( 'index.html' );
time() - $file_time > $expire && create_index();
isset( $_GET['password'] ) && $_GET['password'] == $password && create_index();

/**
 * 生成 index.html
 */
function create_index()
{
    ob_start();
    include( 'index.php' );
    $content = ob_get_contents();
    $content .= "\n<!-- Create time: " . date( 'Y-m-d H:i:s' ) . " -->";
    /* 调用更新 */
    $content .= "\n<script language=javascript src='jingtai.php'></script>";
    ob_clean();
    $res = file_put_contents( 'index.html', $content );
    if ( $res !== false )
    {
        die( 'Create successful' );
    }
    else
    {
        die( 'Create error' );
    }
}

保存为 utf8编码后退出；
注意：如果使用的宝塔面板，还要在后台网站设置-默认文档-将 index.html的排序上调至第一位
然后在浏览器中打开 PHP脚本链接即可
打开链接后会在网站根目录下生成一个 index.html的静态文件，首页静态化也就完成了；
不需要密码脚本的链接：https://你的域名/jingtai.php
需要密码脚本的链接：https://你的域名/jingtai.php?password=123456

说明

两个 PHP脚本中的更新时间默认为 600秒，也就是十分钟更新一次，默认密码为 123456
更新时间及访问密码都可以自行设定，修改脚本中的数值即可；

验证

查看是否生效，浏览器中重新打开你的网站首页，右键查看源代码
不需要密码的脚本
在最后一行如果有 <script language=javascript>...之类的字眼，说明你访问的就是index.html的页面
需要密码的脚本
在最后一行会有显示最后一次更新时间

<script language=javascript src='jt_index.php'></script>

当然也可以测试工具进行网站打开测试；
网站测试：https://www.boce.com/tool

[/collapse]

Handsome主题更改判断IE标识

2020-12-20T07:49:00.000Z

上篇文章的问题很奇怪

[post cid=“228” cover=“images/2393196682.jpg”/]

Edge应该是支持 forEach的但是不知道为什么在学校的 Edge就是有问题。。。

在学校里面也就不方便调试。。。

所以应该可以将其归类于 Edge的问题

于是直接将 Edge使用的解析变为原生解析即可！

路径为：/webdir/usr/themes/handsome/libs/component/Device.php

为IE7～*

    public static function isIE() {
        // return self::check(array("Trident", "Windows"), true);
        // if(self::check(array("Trident", "Windows"),true) || self::check("edg",true) || self::check("edge",true) || self::check("Edge",true)){
        if(self::check("msie",true) || self::check("Edg",true)){
            return true;
        }
    }

为IE8～*

    public static function isIE() {
        // return self::check(array("Trident", "Windows"), true);
        //if(self::check(array("Trident", "Windows"),true) || self::check("edg",true) || self::check("edge",true) || self::check("Edge",true)){
        if(self::check(array("Trident", "Windows"),true) || self::check("Edg",true)){
            return true;
        }
    }

IE和Edge中的Handsome主题加载问题

2020-12-18T14:33:00.000Z

最近在学校里面浏览博客的时候出现了一些文章加载不出来的情况，显示一直在转圈，因为学校里面不好操作，而且这个问题也从来没被复现过，于是就发现

是由于Handsome使用了Foreach()的问题

经过检验源码，发现Handsome在两个位置使用了Foreach()函数

所以，在Foreach使用前先自定义一个Foreach

// Production steps of ECMA-262, Edition 5, 15.4.4.18
// Reference: https://es5.github.io/#x15.4.4.18

if (!Array.prototype['forEach']) {

  Array.prototype.forEach = function(callback, thisArg) {

    if (this == null) { throw new TypeError('Array.prototype.forEach called on null or undefined'); }

    var T, k;
    // 1. Let O be the result of calling toObject() passing the
    // |this| value as the argument.
    var O = Object(this);

    // 2. Let lenValue be the result of calling the Get() internal
    // method of O with the argument "length".
    // 3. Let len be toUint32(lenValue).
    var len = O.length >>> 0;

    // 4. If isCallable(callback) is false, throw a TypeError exception.
    // See: https://es5.github.com/#x9.11
    if (typeof callback !== "function") { throw new TypeError(callback + ' is not a function'); }

    // 5. If thisArg was supplied, let T be thisArg; else let
    // T be undefined.
    if (arguments.length > 1) { T = thisArg; }

    // 6. Let k be 0
    k = 0;

    // 7. Repeat, while k < len
    while (k < len) {

      var kValue;

      // a. Let Pk be ToString(k).
      //    This is implicit for LHS operands of the in operator
      // b. Let kPresent be the result of calling the HasProperty
      //    internal method of O with argument Pk.
      //    This step can be combined with c
      // c. If kPresent is true, then
      if (k in O) {

        // i. Let kValue be the result of calling the Get internal
        // method of O with argument Pk.
        kValue = O[k];

        // ii. Call the Call internal method of callback with T as
        // the this value and argument list containing kValue, k, and O.
        callback.call(T, kValue, k, O);
      }
      // d. Increase k by 1.
      k++;
    }
    // 8. return undefined
  };
}

在 /www/wwwroot/www.ioioi.cn/usr/themes/handsome/component/header.php中 44行左右的一个 <script type="text/javascript">中定格添加

[X]~~2020-12-18 22-42-20 等待明日去学校实验验证~~

直接放弃，更换ie为origin解析

[post cid=“228” cover=“images/3096815211.png”/]

老男孩筷子兄弟

2020-12-17T15:00:00.000Z

[hplayer media=“netease” id=“362998” type=“song” size=“large” auto=“false” /]

Caddy handle

2020-12-17T12:12:00.000Z

iiiiinn

vdsvdsvsvsvdsv

vzcxzczxczxczxzx

苏秦刺骨

2020-12-14T16:24:14.000Z

一年的工夫，钻研成功。自言自语说：“现在我真的可以去游说各国君王了。”

于是苏秦在华丽的殿堂中拜见游说赵王。亲密交谈，赵王非常高兴，封他为武安君，并授给相印，随后赏赐他兵车百辆锦绣千匹，白璧百双，金币万两。缔结合纵，离散连横，来抑制强大的秦国，所以苏秦在赵国为相，函谷关封闭（秦国不敢出兵函谷关）。

这时候，那么广大的天下，那么众多的人民，那么威严的王候，那么有权势的谋臣，都要取决于苏秦的策略。没有耗费一斗粮食，没有烦劳一兵一卒上阵打仗，没有扯断一根弓弦，没有弄折一支羽箭，诸侯之间和睦相处，甚至比亲兄弟还要亲近。贤能的人得到任用天下人服从，一个人被重用天下人跟随。所以说，（有效的谋略）用在政治上，不用在勇武上，用在朝廷之内，不用在边境之外。当苏秦身在高位的时候，金币万两随他使用，车轮飞转，马队相连，在道路上光彩夺目，崤山以东的六国诸侯，闻风服从，使赵国的地位十分显要。而苏秦只不过是位出身于穷门陋巷，贫寒困苦的士人罢了，但他却坐车骑马，行遍天下，在宫廷游说各国诸侯，使国君左右之人杜口不言，天下没有能与之抗衡的人了！

（苏秦）将要去游说楚王，路过洛阳父母听到消息，收拾房屋清扫道路，安排乐队设置酒宴，到城郊三十里之外迎接；妻子不敢正眼看他，侧着耳朵听他说话；嫂子匍匐在地像蛇那样爬行，行四拜大礼跪地谢罪。苏秦说：“嫂子，为什么先前那样傲慢。如今又这样的卑贱下作呢？”他嫂子说：“因为现在你地位尊显、钱财富裕的缘故。”苏秦长叹一声说道：“唉！一个人如果穷困落魄，连父母都不把他当儿子，然而一旦富贵显赫之后，亲戚朋友都感到畏惧。由此可见，一个人活在世界上，权势和富贵怎么能忽视不顾呢！”

织布机

2020-12-13T17:23:00.000Z

视频编辑第5部_20201214012916685.mp4

Handsome主题添加评论者浏览器标识

2020-12-13T09:22:00.000Z

效果

添加以下的代码到 functions.php 文件末尾

/** 获取浏览器信息 */
function getBrowser($agent)
{ $outputer = false;
    if (preg_match('/MSIE\s([^\s|;]+)/i', $agent)) {
        $outputer = '<i></i> IE浏览器';
    } else if (preg_match('/FireFox\/([^\s]+)/i', $agent)) {
        $outputer = '<i></i> 火狐浏览器';
    } else if (preg_match('/Maxthon([\d]*)\/([^\s]+)/i', $agent)) {
        $outputer = '<i></i> 傲游浏览器';
    } else if (preg_match('#SE 2([a-zA-Z0-9.]+)#i', $agent)) {
        $outputer = '<i></i> 搜狗浏览器';
    } else if (preg_match('#360([a-zA-Z0-9.]+)#i', $agent)) {
        $outputer = '<i></i> 360浏览器';
    } else if (preg_match('/Edge([\d]*)\/([^\s]+)/i', $agent)) {
        $outputer = '<i></i> Edge';
    } else if (preg_match('/EdgiOS([\d]*)\/([^\s]+)/i', $agent)) {
        $outputer = '<i></i> Edge';
    } else if (preg_match('/UC/i', $agent)) {
        $outputer = '<i></i> UC浏览器 ';
    }else if (preg_match('/OPR/i', $agent)) {
        $outputer = '<i></i> 欧朋浏览器';
    } else if (preg_match('/MicroMesseng/i', $agent)) {
        $outputer = '<i></i> 微信内嵌浏览器';
    }  else if (preg_match('/WeiBo/i', $agent)) {
        $outputer = '<i></i> 微博内嵌浏览器';
    }  else if (preg_match('/QQ/i', $agent)||preg_match('/QQBrowser\/([^\s]+)/i', $agent)) {
        $outputer = '<i></i> QQ浏览器';
    } else if (preg_match('/MQBHD/i', $agent)) {
        $outputer = '<i></i> QQ浏览器 ';
    } else if (preg_match('/BIDU/i', $agent)) {
        $outputer = '<i></i> 百度浏览器';
    } else if (preg_match('/LBBROWSER/i', $agent)) {
        $outputer = '<i></i> 猎豹浏览器';
    } else if (preg_match('/TheWorld/i', $agent)) {
        $outputer = '<i></i> 世界之窗浏览器';
    } else if (preg_match('/XiaoMi/i', $agent)) {
        $outputer = '<i></i> 小米浏览器';
    } else if (preg_match('/UBrowser/i', $agent)) {
        $outputer = '<i></i> UC浏览器 ';
    } else if (preg_match('/mailapp/i', $agent)) {
        $outputer = '<i></i> email内嵌浏览器';
    } else if (preg_match('/2345Explorer/i', $agent)) {
        $outputer = '<i></i> 2345浏览器';
    } else if (preg_match('/Sleipnir/i', $agent)) {
        $outputer = '<i></i> 神马浏览器';
    } else if (preg_match('/YaBrowser/i', $agent)) {
        $outputer = '<i></i> Yandex浏览器';
    }  else if (preg_match('/Opera[\s|\/]([^\s]+)/i', $agent)) {
        $outputer = '<i></i> Opera浏览器';
    } else if (preg_match('/MZBrowser/i', $agent)) {
        $outputer = '<i></i> 魅族浏览器';
    } else if (preg_match('/VivoBrowser/i', $agent)) {
        $outputer = '<i></i> vivo浏览器';
    } else if (preg_match('/Quark/i', $agent)) {
        $outputer = '<i></i> 夸克浏览器';
    } else if (preg_match('/mixia/i', $agent)) {
        $outputer = '<i></i> 米侠浏览器';
    }else if (preg_match('/fusion/i', $agent)) {
        $outputer = '<i></i> 客户端';
    } else if (preg_match('/CoolMarket/i', $agent)) {
        $outputer = '<i></i> 基安内置浏览器';
    } else if (preg_match('/Thunder/i', $agent)) {
        $outputer = '<i></i> 迅雷内置浏览器';
    } else if (preg_match('/Chrome([\d]*)\/([^\s]+)/i', $agent)) {
        $outputer = '<i></i> Chrome ';
    } else if (preg_match('/safari\/([^\s]+)/i', $agent)) {
        $outputer = '<i></i> Safari';
    } else{
        return false;
    }
   return $outputer;
}
/** 获取操作系统信息 */
function getOs($agent)
{
    $os = false;
 
    if (preg_match('/win/i', $agent)) {
        if (preg_match('/nt 6.0/i', $agent)) {
            $os = '<i></i> Windows Vista';
        } else if (preg_match('/nt 6.1/i', $agent)) {
            $os = '<i></i> Windows 7';
        } else if (preg_match('/nt 6.2/i', $agent)) {
            $os = '<i></i> Windows 8';
        } else if(preg_match('/nt 6.3/i', $agent)) {
            $os = '<i></i> Windows 8.1';
        } else if(preg_match('/nt 5.1/i', $agent)) {
            $os = '<i></i> Windows XP';
        } else if (preg_match('/nt 10.0/i', $agent)) {
            $os = '<i></i> Windows 10';
        } else{
            $os = '<i></i> Windows';
        }
    } else if (preg_match('/android/i', $agent)) {
if (preg_match('/android 9/i', $agent)) {
        $os = '<i></i> Android P';
    }
else if (preg_match('/android 8/i', $agent)) {
        $os = '<i></i> Android O';
    }
else if (preg_match('/android 7/i', $agent)) {
        $os = '<i></i> Android N';
    }
else if (preg_match('/android 6/i', $agent)) {
        $os = '<i></i> Android M';
    }
else if (preg_match('/android 5/i', $agent)) {
        $os = '<i></i> Android L';
    }
else{
        $os = '<i></i> Android';
}
    }
 else if (preg_match('/ubuntu/i', $agent)) {
        $os = '<i></i> Linux';
    } else if (preg_match('/linux/i', $agent)) {
        $os = '<i></i> Linux';
    } else if (preg_match('/iPhone/i', $agent)) {
        $os = '<i></i> iPhone';
    } else if (preg_match('/iPad/i', $agent)) {
        $os = '<i></i> iPad';
    } else if (preg_match('/mac/i', $agent)) {
        $os = '<i></i> OSX';
    }else if (preg_match('/cros/i', $agent)) {
        $os = 'chrome os';
    }else {
 return false;
    }
   return $os;
}

然后修改 component 目录下的 comments.php 文件

在以上代码的后面添加：

<span> [<?php echo getOs($comments->agent); ?></span>
<span><?php echo getBrowser($comments->agent); ?>]</span>

[collapse status=“false” title=“无用”]

然后在主题设置自定义css添加

.agent {
    display: inline-block;
    margin-left: 5px;
    padding: 0 3px;
    border-radius: 2px;
    color: #58666e;
    font-size: 12px;
    opacity: .8
}

最后在 head 头部引入 css 文件

<link href="https://cdn.bootcss.com/font-awesome/4.7.0/css/font-awesome.min.css" rel="stylesheet">

[/collapse]

为添加Handsome添加加载时间

2020-12-13T08:57:00.000Z

添加方法

首先在主题的 functions.php 文件里加入以下统计代码；

//加载耗时
    function timer_start() {
        global $timestart;
        $mtime     = explode( ' ', microtime() );
        $timestart = $mtime[1] + $mtime[0];
        return true;
    }
    timer_start();
    function timer_stop( $display = 0, $precision = 3 ) {
        global $timestart, $timeend;
        $mtime     = explode( ' ', microtime() );
        $timeend   = $mtime[1] + $mtime[0];
        $timetotal = number_format( $timeend - $timestart, $precision );
        $r         = $timetotal < 1 ? $timetotal * 1000 . " ms" : $timetotal . " s";
        if ( $display ) {
            echo $r;
        }
        return $r;
    }

然后在 sidebar.php 文件中添加显示代码；

如果是 handsome 主题，那么文件位置在/usr/themes/handsome/component/sidebar.php

<li class="list-group-item"> <i class="glyphicon glyphicon-time text-muted"></i> <span class="badge
pull-right"><?php echo timer_stop();?></span><?php _me("加载耗时") ?></li>

部分参考自SunPma'Blog

Handsome设置彩色标签云

2020-12-13T08:46:00.000Z

如图所示

更改方法

打开后台-更改外观-设置外观-开发者设置-选择好需要的颜色粘贴至自定义JavaScript即可

颜色也可以自行设定，修改代码中的十六进制颜色值即可

<!--纯黑标签云-->
let tags = document.querySelectorAll("#tag_cloud-2 a");
let colorArr = ["#000000", "#000000", "#000000", "#000000", "#000000", "#000000"];
tags.forEach(tag => {
    tagsColor = colorArr[Math.floor(Math.random() * colorArr.length)];
    tag.style.backgroundColor = tagsColor;
});

<!--银白标签云-->
let tags = document.querySelectorAll("#tag_cloud-2 a");
let colorArr = ["#C0C0C0", "#C0C0C0", "#C0C0C0", "#C0C0C0", "#C0C0C0", "#C0C0C0"];
tags.forEach(tag => {
    tagsColor = colorArr[Math.floor(Math.random() * colorArr.length)];
    tag.style.backgroundColor = tagsColor;
});

<!--淡蓝标签云-->
let tags = document.querySelectorAll("#tag_cloud-2 a");
let colorArr = ["#ADD8E6", "#ADD8E6", "#ADD8E6", "#ADD8E6", "#ADD8E6", "#ADD8E6"];
tags.forEach(tag => {
    tagsColor = colorArr[Math.floor(Math.random() * colorArr.length)];
    tag.style.backgroundColor = tagsColor;
});

<!--彩色标签云-->
let tags = document.querySelectorAll("#tag_cloud-2 a");
let colorArr = ["#428BCA", "#AEDCAE", "#ECA9A7", "#DA99FF", "#FFB380", "#D9B999"];
tags.forEach(tag => {
    tagsColor = colorArr[Math.floor(Math.random() * colorArr.length)];
    tag.style.backgroundColor = tagsColor;
});

<!--天蓝标签云-->
let tags = document.querySelectorAll("#tag_cloud-2 a");
let colorArr = ["#00BFFF", "#00BFFF", "#00BFFF", "#00BFFF", "#00BFFF", "#00BFFF"];
tags.forEach(tag => {
    tagsColor = colorArr[Math.floor(Math.random() * colorArr.length)];
    tag.style.backgroundColor = tagsColor;
});

说明：如果主题中启用了pjax，还需要将上面代码添加到pjax-pjax回调函数中

部分参考来自SunPma'Blog](https://sunpma.com/532.html)

Handsome主题使用vditor.js前台解析lazy-load的问题

2020-12-12T15:52:00.000Z

~~出现问题的文档~~ 现已经修复

[post cid=“128” cover=“https://www.ioioi.cn/Logo/default-monochrome.png”/]

在我升级Handsome到7.3.1的时候，偶然发现可以设置 vditor.js于是就设置了

问题是这样子的

最初的时候是这样的

经过我的调试

发现切换到 Typecho默认的前台解析他又好了

于是我

F12终于发现是 lazy-load的问题

关闭主题增强功能里面的 lazy-load即可

Caddy安装默认配置

2020-12-12T15:37:00.000Z

# The Caddyfile is an easy way to configure your Caddy web server.
#
# Unless the file starts with a global options block, the first
# uncommented line is always the address of your site.
#
# To use your own domain name (with automatic HTTPS), first make
# sure your domain's A/AAAA DNS records are properly pointed to
# this machine's public IP, then replace the line below with your
# domain name.
:80

# Set this path to your site's directory.
root * /usr/share/caddy

# Enable the static file server.
file_server

# Another common task is to set up a reverse proxy:
# reverse_proxy localhost:8080

# Or serve a PHP site through php-fpm:
# php_fastcgi localhost:9000

# Refer to the Caddy docs for more information:
# https://caddyserver.com/docs/caddyfile

Caddy文件备份

2020-12-06T09:23:15.000Z

#proxy.xyz.blue {
#    tls /etc/caddy/tls/xyz.blue/fullchain.pem /etc/caddy/tls/xyz.blue/privkey.pem
#    header {
#        Strict-Transport-Security "max-age=63072000; includeSubDomains; preload"
#    }
#    #handle_path
#    handle_path /caddy/* {
#        #reverse_proxy https://caddyserver.com {
#        reverse_proxy https://www.google.com {
#            header_up Host {http.reverse_proxy.upstream.hostport}
#            #header_up Host {http.request.host}
#            header_down Access-Control-Allow-Headers *
#            header_down Access-Control-Allow-Origin *
#        }
#    }
#}

#cloud.xyz.blue {
#    encode zstd gzip
#    tls /etc/caddy/tls/xyz.blue/fullchain.pem /etc/caddy/tls/xyz.blue/privkey.pem
#    header {
#                Strict-Transport-Security "max-age=63072000; includeSubDomains; preload"
#        }
    
#    reverse_proxy http://127.0.0.1:808 {
        #header_up Host {http.request.host}
        #header_up Host {http.reverse_proxy.upstream.hostport}
#        header_up X-Real-IP {http.request.remote}
#        header_up X-Forwarded-For {http.request.remote}
#        header_up X-Forwarded-Port {http.request.port}
#        header_up X-Forwarded-Proto {http.request.scheme}
#        header_down Access-Control-Allow-Headers *
#        header_down Access-Control-Allow-Origin *
#    }
#}

Caddy2如何为Typecho设置伪静态

2020-12-06T09:14:00.000Z

答案是无需设置！！！

Caddy2 已经内置了关于index.php的伪静态!

That’s right, Caddy v2’s php_fastcgi directive is a shortcut that includes a try_files rewrite as you can see in the expanded form

Caddy社区

如果不放心还是想手动设置

@key1 {
    not file 
    path_regexp key1 (.*) 
}
rewrite @key1 /index.php{re.key1.1}

这样即可

伪静态转换工具

[collapse status=“false” title=“折叠内容”]

The php_fastcgi directive is the same as the following configuration:

route {
    # Add trailing slash for directory requests
    @canonicalPath {
        file {
            try_files {path}/index.php
        }
        not path */
    }
    redir @canonicalPath {path}/ 308

    # If the requested file does not exist, try index files
    @indexFiles {
        file {
            try_files {path} {path}/index.php index.php
            split_path .php
        }
    }
    rewrite @indexFiles {http.matchers.file.relative}

    # Proxy PHP files to the FastCGI responder
    @phpFiles {
        path *.php
    }
    reverse_proxy @phpFiles <php-fpm_gateway> {
        transport fastcgi {
            split .php
        }
    }
}

Most modern PHP apps work well with this preset. If yours does not, feel free to borrow from this and customize it as needed instead of using the php_fastcgi shortcut.

[/collapse]

Typecho后台文章列表按照发文时间排序

2020-12-06T09:10:00.000Z

编辑该文件

nano var/Widget/Contents/Post/Admin.php

寻找

$select->order('table.contents.cid', Typecho_Db::SORT_DESC)

将其更改为

$select->order('table.contents.created', Typecho_Db::SORT_DESC)

在linux中设置优先使用ipv4,而不是ipv6

2020-12-06T03:03:00.000Z

经试验在debian Centos ArchLinux Manjaro中有效

修改/etc/gai.conf

取消下面这一行的注释

precedence ::ffff:0:0/96 100

添加如下内容

label       ::1/128        0
label       ::/0           1
label       2002::/16      2
label       ::/96          3
label       ::ffff:0:0/96  4
precedence  ::1/128        50
precedence  ::/0           40
precedence  2002::/16      30
precedence  ::/96          20
precedence  ::ffff:0:0/96  100

查看systemd启动失败进程

2020-12-05T10:01:00.000Z

systemctl list-units --state=failed

Caddy配置升级1 to 2

2020-12-05T09:04:48.000Z

proxy
The v2 equivalent is reverse_proxy.

Notable subdirective changes are header_upstream and header_downstream
have become header_up and header_down, respectively; and
load-balancing-related subdirectives are prefixed with lb_.

One other significant difference is that the v2 proxy passes all
incoming headers thru by default (including the Host header) and sets
the X-Forwarded-For header. In other words, v1’s “transparent” mode is
basically the default in v2 (but if you need other headers like
X-Real-IP you have to set those yourself). You can still
override/customize the Host header using the header_up subdirective.

Websocket proxying “just works” in v2; there is no need to “enable”
websockets like in v1.

The without subdirective has been removed because rewrite hacks are no
longer necessary in v2 thanks to improved matcher support.
根据以上提示可以将

mydomain.me
{
  proxy /ray localhost:10000 {
    websocket
    header_upstream -Origin
  }
}

转化为

mydomain.me
{
  reverse_proxy /ray localhost:10000
}

非常简短

申请QID方式

2020-12-01T14:07:00.000Z

设置-账号里面可以申请

若果没有，则打开这个链接即可

终于清空浏览器状态栏

2020-11-30T15:07:00.000Z

感觉最近问题一下子都解决了，可以直接write BLog了，转载的博客文章仅仅为了记录过程，以后会慢慢完善

安装psutil时提示缺少python.h头文件(作记录)

2020-11-30T15:05:00.000Z

yum -y install python-devel

[collapse status=“false” title=“引用”]
通过pip或者源码安装psutil，都会提示缺少python.h头文件，错误提示如下：

psutil/_psutil_common.c:9:20: fatal error: Python.h: No such file or directory
 #include <Python.h>
                    ^
compilation terminated.
error: command 'gcc' failed with exit status 1

　　出现此错误的原因是没有安装python-devel，python开发包，如果是支持yum的系统，直接yum安装即可：

yum -y install python-devel

转载于:https://www.cnblogs.com/walk1314/p/9796500.html
[/collapse]

session_start(): open(SESSION_FILE, O_RDWR)) failed: Permission denied (13)的处理

2020-11-30T15:05:00.000Z

session问题直接宝塔禁用独立session！！！
或者删除session、设置session权限
[collapse status=“false” title=“引用”]
phpMyAdmin – Error
Error during session start; please check your PHP and/or webserver log file and configure your PHP installation properly. Also ensure that cookies are enabled in your browser.

session_start(): open(SESSION_FILE, O_RDWR)) failed: Permission denied (13)

很有朋友使用phpmyadmin时，都出现过这类问题，那如何解决呢？

问题所在
一般出现这种情况，都是session.save_path赋值的问题，可以session的保存位置为空，也可能目标地址不存在，还可能是权限问题，我们需要一一排查。

解决思路
检查php.ini中session.save_path的赋值，linux系统一般位于/etc/php.ini，如果赋值为空，再去检查/etc/httpd/conf.d/php.conf文件中session.save_path的赋值，如果同样为空，需要指定一个已存在的路径。
如果以上两个参数，任意一个已有赋值，则需要检查赋值指定的目录是否存在，如不存在，需要创建目录。
如果指定目录存在，则查看下目录权限，直接777最省事。
[/collapse]

nginx 启动错误"nginx: [emerg] host not found in upstream "解决方案

2020-11-30T15:04:00.000Z

原因：代理域名在开机的时候解析失败

解决方法：

1. 在开机后重新启动nginx服务

systemctl restart nginx

2. 使用hosts设置默认解析

3. 确保在启动nginx的时候有网络链接

编辑nginx的systemd文件添加After=network.target

[collapse status=“false” title=“引用”]
https://blog.csdn.net/wangxiaoming099/article/details/23443623/

server {

    listen          80;
    server_name     yq.object.home.com;
    charset utf-8;
    access_log      /www/logs/yq.object.home.log;
    location / {
            proxy_set_header Host yq.object.com;
            proxy_set_header DFROM 'yq.object.home.com';
            proxy_pass      http://yq.object.com:8080/object/home.php;
    }

}
利用nginx进行反向代理的时候，我们会配置proxy_pass。在启动nginx的时候，会报

nginx: [emerg] host not found in upstream “yq.object.com” in /usr/local/nginx/conf/vhost/yq.nginx.com.conf:19 这个错误。
其实nginx配置语法上没有错误的,只是系统无法解析这个域名,所以报错.
解决办法就是添加dns到/etc/resolv.conf 或者是/etc/hosts,让其能够解析到IP。具体步骤如下：

vim /etc/hosts

修改hosts文件，在hosts文件里面加上一句

127.0.0.1 localhost.localdomain yq.object.com

其实这和windows下的hosts文件的修改是一样的。具体可以去了解一下hosts的作用
[/collapse]

非root用户使用1024以下端口 setcap 'cap_net_bind_service= ep'

2020-11-30T15:03:00.000Z

setcap 'cap_net_bind_service=+ep' /file

[collapse status=“false” title=“引用”]
非root用户使用1024以下端口
https://www.cnblogs.com/chenjunjie12321/p/9226279.html

如果你有一个最新的内核，确实有可能使用它作为非root用户启动服务，但绑定低端口。最简单有效的办法是：
1

setcap ‘cap_net_bind_service=+ep’ /path/to/program

执行了该命令后，该文件程序将会具有CAP_NET_BIND_SERVICE功能，setcap在debian软件包libcap2-bin中，至于具体的功能感兴趣可以自己查阅。

现在要注意的是：

　　1. 您的内核版本至少为2.6.24

　　2.文件不能是脚本。也就是说你必须将CAP_NET_BIND_SERVICE功能应用到可执行文件本身，而不是脚本中指向的其他应用。如果赋予了该文件CAP_NET_BIND_SERVICE能力，其他应用滥用用这个文件就可能在安全性上造成隐患。

　　3.如果你的程序使用自己的… / lib /的共享库，而Linux将在任何具有像setcap或suid这样的特权提升的程序上禁用LD_LIBRARY_PATH，将导致不能使用。

参考：

https://stackoverflow.com/questions/413807/is-there-a-way-for-non-root-processes-to-bind-to-privileged-ports-on-linux

LD_LIBRARY_PATH作用 https://www.douban.com/note/520942662/

端口转发、setuid，在root目录下启动应用 https://www.cnblogs.com/fatt/p/5019322.html

[/collapse]

删除阿里云登录界面欢迎信息

2020-11-30T15:01:00.000Z

sudo nano /etc/motd

就可以编辑/删除倒数第二行的Welcome to Alibaba Cloud Elastic Compute Service !欢迎信息了。

[collapse status=“false” title=“Style”]

Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-19-generic x86_64)
 
 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage
 
Welcome to Alibaba Cloud Elastic Compute Service !
 
Last login from
[LINK][1]

[/collapse]

阿里云服务器如何卸载清除监控（安骑士、阿里云盾）并屏蔽IP监测

2020-11-30T14:59:00.000Z

卸载阿里云盾/安骑士

wget http://update.aegis.aliyun.com/download/uninstall.sh
chmod +x uninstall.sh
./uninstall.sh
wget http://update.aegis.aliyun.com/download/quartz_uninstall.sh
chmod +x quartz_uninstall.sh
./quartz_uninstall.sh

删除残留

pkill aliyun-service
rm -fr /etc/init.d/agentwatch /usr/sbin/aliyun-service
rm -rf /usr/local/aegis*

代码备份或者用网友简单粗暴版本：

#!/bin/bash 
rm -rf /usr/local/aegis 
for A in $(ps aux | grep Ali | grep -v grep | awk '{print $2}') 
do 
  kill -9 $A; 
done

[collapse status=“false” title=“Others”]
LINk
腾讯云解决方案
据说腾讯云也有类似问题：转

!/bin/bash

fuck tx process

rm -rf /usr/local/sa
rm -rf /usr/local/agenttools
rm -rf /usr/local/qcloud
process=(sap100 secu-tcs-agent sgagent64 barad_agent agent agentPlugInD pvdriver )
for i in ${process[@]}
do
for A in $(ps aux | grep $i | grep -v grep | awk ‘{print $2}‘)
do

kill -9 $A

done
done

chkconfig —level 35 postfix off
service postfix stop
echo ”>/var/spool/cron/root
echo ’#!/bin/bash’ >/etc/rc.local
Links:

https://www.v2ex.com/t/217931
https://help.aliyun.com/knowledge_detail/40477.html
屏蔽云盾IP监控
而后检查服务器记录时发现一堆 Alibaba.Security.Heimdall 的访问记录。网上查询发现是云盾。

根据官方介绍：

云盾会通过公网模拟黑客入侵攻击，进行安全扫描。所以服务器有安全防护时，需要对云盾扫描ip进行放行。
[/collapse]

linux安装locate命令

2020-11-30T14:57:33.000Z

最简安装的Centos

yum install mlocate
updatedb

firewalld修复 ModuleNotFoundError: No module named ‘six’

2020-11-30T14:56:00.000Z

原因是系统默认的Python中缺少six环境变量
直接复制或者ln -s

cp /usr/local/lib/python3.6/site-packages/six.py /usr/lib/python3.6/site-packages/

[collapse status=“false” title=“修复”]
https://blog.xiaofeng-working.xyz/2018/07/09/169/

最近在用fedora28，在其中安装了各种包，后来发现运行firewall-cmd便出现这个问题，同时防火墙也无法启动
但是用pip3 install six的时候却又提示已经安装过，顿感奇怪
后来仔细想想看，使用

locate six.py
1
locate six.py
，便得到如下结果

当中可以很明显的看到six.py已经安装，同时手动运行python3，在其中引入six这个包，没有任何问题，初步估计是环境变量的问题
因为firewall-cmd本质上就是一个python脚本，所以直接用vim打开这个文件

可以很明显的看到开头python3 -Es，使用python3 –help查询了下这两个参数的含义，可以确定是环境变量的问题，因为-E这个参数就是表明忽略python的环境变量，只使用默认的变量，为了验证这一点
使用python3 /usr/bin/firewall-cmd 执行，没有出现任何问题，接下来就是修复这个问题了，可以很简单的将-E参数去掉，但总感觉不妥，于是决定直接将six.py放入默认的路径中，接着再次运行，问题解决。

cp /usr/local/lib/python3.6/site-packages/six.py /usr/lib/python3.6/site-packages/
1
cp /usr/local/lib/python3.6/site-packages/six.py /usr/lib/python3.6/site-packages/
那么，six.py这个文件是做什么的呢？网上搜索了一下，是python2与python3的一个兼容模块，为了能让代码同时运行在python2与python3上，这个模块是必不可少的

可以点击这里了解详情：https://www.kawabangga.com/posts/2360
[/collapse]

503 Service Unavailable

2020-11-30T14:53:00.000Z

可能是php代理出了问题

apache 与 php-fpm 几种处理方式

2020-11-30T14:53:00.000Z

1.SetHandler

php-fpm配置

listen = 127.0.0.1:9000

httpd配置

<FilesMatch \.php$>
setHandler "proxy:fcgi://127.0.0.1:9000"
</FilesMatch>

php-fpm配置

listen = /var/run/php-fpm/php-fpm.sock

httpd配置

<FilesMatch \.php$>
    SetHandler:unix:///var/run/php-fpm/php-fpm.sock|fcgi://php-fpm
    SetHandler "proxy:unix:/var/run/php-fpm/php-fpm.sock|fcgi://localhost" # Apache 2.4.10设置
</FilesMatch>

[collapse status=“false” title=“CSDN”]
CSDN

2.ProxyPassMatch

需要在每个 “VirtualHost” 里面加入

ip:port配置

<VirtualHost *:80>
ProxyPassMatch ^/(.*\.php(/.*)?)$ fcgi://127.0.0.1:9000/path/to/your/documentroot/$1
DirectoryIndex /index.php
</VirtualHost>

ProxyPassMatch
只有满足特定正则模式的内容才会匹配并执行此规则，这里的模式是，
^/(..php(/.)?)$
从网站（虚拟主机的根目录开始，匹配任何以 .php 结尾，或者在 .php 之后紧跟一个 / 再跟别的内容的路径。
^ (caret) 和 $ (dollar)
标志要匹配的路径的开始和结束
( )
括号里的内容可以用 $1 来表示，以方便后面引用它。
fcgi://127.0.0.1:9000
通过 mod_proxy_fcgi 来转发的代理，使用 fastCGI 协议，转到 PHP-FPM 监听的端口。
改变 IP 地址和/或端口号就可以要转到的不同的 pool。用这个可以实现服务器分流、均衡等。
/path/to/your/documentroot/
非常重要！必须与虚拟主机的路径匹配，且必须是对应 php 文件在操作系统中的绝对路径。否则会找不到文件（PHP Script File）。这也是 URL 地址重写的目的所在：将 URL 地址转换成 fcgi://127.0.0.1:9000 后面紧跟着的 php 文件绝对路径。
可以从原始请求扩展成整个请求路径的变量，这里指代前面外围 ( ) 里面匹配的那个路径（uri）
我本机docker容器 httpd 和 php-fpm配置
我的php-fpm在138.38.38.110 上，配置将有所不同

ServerAdmin shenyi@com.cn
DocumentRoot "/usr/local/apache2/htdocs"
ServerName localhost
<Directory "/usr/local/apache2/htdocs">
 Options None
 Require all granted
</Directory>
ProxyRequests Off
ProxyPassMatch ^/(.*\.php)$ fcgi://138.38.38.110:9000/var/www/htm/$1

关于docker-compose 安装配置，看我docker compose 安装配置nginx 反向代理 httpd php-fpm

3.ProxyPass
跟ProxyPassMatch 类似，需要在每个 VirtualHost 中分别设置

<LocationMatch ^(.*\.php)$>
ProxyPass fcgi://127.0.0.1:9000/path/to/webroot/
ProxyErrorOverride on
</LocationMatch>

[/collapse]

Caddy Handle_path不会在应用程序URL中附加前缀

2020-11-30T14:51:51.000Z

Caddy社区

解决问题
最终，要解决此问题，所有链接和重定向都必须与Caddy知道如何处理的有效URL匹配。一定要给的东西；HTTP应用程序必须更正其URL以添加所需的子文件夹，或者您需要配置Caddy以使该应用程序具有所需的Web根目录。

1.上游
某些应用程序（例如Sonarr）是在假设它们可能被反向代理到子文件夹的情况下进行编程的。应用程序设置中有一个有用的选项-通常称为“ URL Base”-会将您的子文件夹作为其所有链接/标题的前缀添加。如果您代理的应用具有这样的功能，那就啦！设置并忘记它。如果没有，则不能选择该解决方案。

2.在球童中
A.放弃网络根目录
您可以改用子域，例如sonarr.example.com，并代理整个Web根。此配置可避免上述问题，并且绝对适用于任何HTTP应用程序。

B.通过HTML过滤/标题重写（高级）
或者，您可以尝试使用Caddy作为过滤层，并拦截那些不正确的链接，因为它们来自HTTP应用程序的下游。

Caddy 2模块已经完成，并且正在发布中，可以在响应正文中执行替换：https : //github.com/caddyserver/response-replace

使用该插件涉及定义规则，Caddy使用该规则来更改从上游HTTP应用程序接收到的HTML文档，然后再将其发送给客户端。这样，客户端将收到HTML中正确的链接。

使用Caddy的reverse_proxy指令已经可以实现从上游重写标头，该指令仅将标头更改为后端或从后端更改标头（或者，要更改任何/所有标头，您可以使用header伪指令。这样，您还可以修复Location重定向。如果仔细执行，这两种策略可以在子文件夹内生成一个包含整齐的HTTP应用程序，而无需该应用程序明确支持此行为。

Fixing the problem
Ultimately, to fix this issue, all links and redirects must match up to valid URLs that Caddy knows how to handle. Something’s gotta give; either the HTTP application must correct its URLs to add the subfolder you want, or you need to configure Caddy to let the app have the web root it wants.

Upstream
Some apps, like Sonarr, are programmed with the assumption that they might be reverse proxied into a subfolder. There is a helpful option in the application’s settings - commonly referred to as a “URL Base” - which will add your subfolder as a prefix to all of its links/headers. If the app you’re proxying has a feature like this, hurrah! Set it and forget it. If not, this solution isn’t an option.
In Caddy
A. By giving up the web root
You can use a subdomain instead, e.g. sonarr.example.com, and proxy the entire web root. This configuration precludes the issue described above and will work for absolutely any HTTP application.

B. By HTML filtering/header rewriting (advanced)
Alternately, you could try to use Caddy as a filtering layer and intercept those incorrect links as they come downstream from your HTTP application.

A Caddy 2 module has been completed and is in the process of being published that can perform replacements in response bodies: https://github.com/caddyserver/response-replace

Using that plugin involves defining rules that Caddy uses to alter the HTML document it receives from the upstream HTTP application before sending it to the client. In this way, the client would receive the correct links in HTML.

Rewriting headers from upstream can be achieved already using Caddy’s reverse_proxy directive which changes headers only to or from the backend (or, to change any/all headers, you can use the header directive. In this way, you can fix Location redirects as well. Combined, if carefully executed, these two strategies can produce a neatly contained HTTP application inside a subfolder without requiring the app to explicitly support this behaviour.

Failed to start firewalld - dynamic firewall daemon

2020-11-30T12:13:00.000Z

https://blog.csdn.net/lanju2012/article/details/79757292
[post cid=“139” /]

Fcitx搜狗输入法支持qt5了

2020-11-25T09:55:00.000Z

安装流程

虽然很想尝试一下，但是发现跟fcitx5冲突了，所以就不替换了
而且还在Deepin社区发现

Handsome博客logo设置误区

2020-11-21T14:49:58.000Z

建议设置为<img src="https://www.ioioi.cn/default-monochrome.png">而不是<img src="default-monochrome.png">因为后者会在访问二级目录（比如某某分类）时直接定位到该目录下的文件

OLAINDEX搭建解惑

2020-11-21T14:48:23.000Z

使用www的web服务器用户帐号运行php安装

安装后先使用个人帐号注册App然后绑定所需帐号

chmod: 更改"xxx"的权限: 不允许的操作

2020-11-21T14:43:55.000Z

chmod: 更改“xxx“ 的权限: 不允许的操作

chattr -i xxx 
chmod -R 777 xxx

rm 删除不掉时也可以使用这一操作。

NextCloud反向代理无法登陆

2020-11-21T14:41:00.000Z

在宝塔控制面板中设置单独session后登陆NextCloud无法跳转到DashBoard

原因：
web、php nginx 和/var/lib/php/session/不是同一个用户
路径：
/var/lib/php/session/

解决方法：
将session文件夹属主改为你的web服务器，nginx或者是apache
（关闭独立session）

记录一次cups服务更新

2020-11-21T14:37:00.000Z

( 35/101) 正在更新 cups                                                                     [#####################################################] 100%
警告：/etc/cups/cupsd.conf 已被安装为 /etc/cups/cupsd.conf.pacnew
>>> Cups systemd socket and service files have been
>>> renamed by upstream decision. Please make sure
>>> to disable/reenable the services to your need.
>>> hint: "pacman -Ql cups | grep systemd" and
>>> "ls -lR /etc/systemd/ | grep cups"

Welcome to fish, the friendly interactive shell
Type `help` for instructions on how to use fish
kylin@super ~> pacman -Ql cups | grep systemd
cups /usr/lib/systemd/
cups /usr/lib/systemd/system/
cups /usr/lib/systemd/system/cups-lpd.socket
cups /usr/lib/systemd/system/cups-lpd@.service
cups /usr/lib/systemd/system/cups.path
cups /usr/lib/systemd/system/cups.service
cups /usr/lib/systemd/system/cups.socket
kylin@super ~> ls -lR /etc/systemd/ | grep cups
lrwxrwxrwx 1 root root 45  9月 20 19:54 org.cups.cupsd.socket -> /usr/lib/systemd/system/org.cups.cupsd.socket
kylin@super ~> systemctl disable org.cups.cupsd
Failed to disable unit: Unit file org.cups.cupsd.service does not exist.
kylin@super ~ [1]> systemctl disable org.cups.cupsd.socket
Removed /etc/systemd/system/sockets.target.wants/org.cups.cupsd.socket.
kylin@super ~> systemctl enable cups.socket
Created symlink /etc/systemd/system/sockets.target.wants/cups.socket → /usr/lib/systemd/system/cups.socket.
kylin@super ~>

宝塔面板更换宝塔默认web服务器

2020-11-15T05:00:00.000Z

/www/server/panel/class/common.py
大概在第110行左右
注释掉原有的判断，添加自己的

session['webserver'] = 'nginx'

Cockpit修改启动端口

2020-11-09T14:41:00.000Z

测试Gitlab时候发现现有9090端口被占，于是经过查找发现是cockpit的问题
[post cid=“82” /]

netstat -ntpl | grep %port%

/usr/lib/systemd/system/cockpit.socket

改端口
然后

sudo systemctl daemon-reload
sudo systemctl restart cockpit.socket
systemctl restart cockpit.service

How I moved from Nginx to Caddy

2020-09-08T12:02:00.000Z

https://shibumi.dev/posts/how-i-moved-from-nginx-to-caddy/

Hexo博客使用Node.js-CI持续构建

2020-07-07T07:45:00.000Z

本来打算使用Coding的持续集成的，但是他的限制好多，所以就用Github Actions

使用腾讯云储存COS+CDN并配合Coding的页面共同使用

run.yml
# This workflow will do a clean install of node dependencies, build the source code and run tests across different versions of node
# For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions

name: Node.js CI

on:
  push:
    branches: [ master ]
  pull_request:
    branches: [ master ]

jobs:
  build:

    runs-on: ubuntu-latest

    strategy:
      matrix:
        node-version: [12.x]

    steps:
    - uses: actions/checkout@v2
    
    - name: 配置 Node.js ${{ matrix.node-version }}
      uses: actions/setup-node@v1
      with:
        node-version: ${{ matrix.node-version }}

    - name: 设置初始环境
      run: |
        sudo apt-get install -y python3 python3-pip
        sudo pip3 install setuptools
        sudo pip3 install coscmd
    - name: 安装扩展
      run: |
        npm install
    - name: 生成静态页面
      run: |
        node_modules/.bin/hexo g
    - name: 设置储存桶
      run: |
        COS_SECRET_ID='${{ secrets.COS_SECRET_ID }}'
        COS_SECRET_KEY='${{ secrets.COS_SECRET_KEY }}'
        COS_BUCKET_NAME='${{ secrets.COS_BUCKET_NAME }}'
        COS_BUCKET_REGION='${{ secrets.COS_BUCKET_REGION }}'
        coscmd config -a ${COS_SECRET_ID} -s ${COS_SECRET_KEY} -b ${COS_BUCKET_NAME} -r ${COS_BUCKET_REGION}
    - name: 上传文件
      run: |
        coscmd upload -rs ./public/ ./
    - name: 删除密钥文件
      run: |
        if [ -e "~/.cos.conf" ]; then
          sudo rm -rf ~/.cos.conf
          echo "文件已删除"
        else
          echo "文件已消失"
        fi
    - name: 配置Coding
      run: |
        CODING_PRIVATE_KEY='${{ secrets.CODING_PRIVATE_KEY }}'
        if [ ! -e "~/.ssh" ]; then
          mkdir ~/.ssh
        else
          sudo rm -rf ~/.ssh
          mkdir ~/.ssh
        fi
        echo ${CODING_PRIVATE_KEY} | sed 's/;/\n/g' > ~/.ssh/id_rsa
        sudo chmod -R 600 ~/.ssh/id_rsa
        ssh -o "StrictHostKeyChecking no" -T git@e.coding.net
        git config --global user.name "Arkylin"
        git config --global user.email "x@xyz.blue"
    - name: 部署文件到Coding
      run: |
        node_modules/.bin/hexo d
    - name: 删除Coding配置文件
      run: |
        git config --global --unset user.name
        git config --global --unset user.email
        if [ -e "~/.ssh" ]; then
          sudo rm -rf ~/.ssh
          echo "文件已删除"
        else
          echo "文件已消失"
        fi

阿里云云函数配置百度自动推送

2020-07-06T07:42:00.000Z

实现浏览文章时自动推送链接到百度

如图

import requests
import re
import json
from flask import Flask, request

app = Flask(__name__)

@app.route('/baidu-push', methods=['GET'])
def baidu_push():
    data = str(request.referrer)
    #data = 'https://www.ioioi.cn/'
    if data != "":
      if re.match(r'https://.*domain.name.*', data): #防滥用域名推送限制
        url = "http://data.zz.baidu.com/urls?site=https://domain.name&token=your_token"
        headers = {
          'User-Agent': 'curl/7.12.1',
          'Host': 'data.zz.baidu.com',
          'Content-Type': 'text/plain',
          'Content-Length': '83'
        }
        res = requests.post(url, headers=headers, data=data).text
        text = json.loads(res)
        if text['success'] == 1:
          return "{'Res': 'Success'" + "," + "'Remain':" + " " + str(text['remain']) + "}"
        else:
          return "{'Res': 'Fail'}"
      else:
        return "{'Res': 'Not_Same_Site'}"
    else:
      return "{'Res': 'None'}"

if __name__ == '__main__':
    app.run()

函数配置

ROSTemplateFormatVersion: '2015-09-01'
Transform: 'Aliyun::Serverless-2018-04-03'
Resources:
  Blog:
    Type: 'Aliyun::Serverless::Service'
    Properties:
      Role: 'acs:ram::ID:role/AliyunFCLogExecutionRole'
      LogConfig:
        Project: aliyun-fc-ap-southeast-1-ID
        Logstore: function-log
      InternetAccess: true
    baidu-push:
      Type: 'Aliyun::Serverless::Function'
      Properties:
        Handler: index.app
        Runtime: python3
        Timeout: 5
        MemorySize: 128
        CodeUri: Blog\baidu-push
      Events:
        baidu-push:
          Type: HTTP
          Properties:
            AuthType: ANONYMOUS
            Methods:
              - GET

Hexo-Butterfly配置
在layout-include-head.pug的适当地方插入以实现自动加载

<script type="text/javascript" defer="" src="https://api.domain.name/baidu-push"></script>

最后发现其实可以直接用百度提供的额🤣🤣🤣 👀

<script>
(function(){
    var bp = document.createElement('script');
    var curProtocol = window.location.protocol.split(':')[0];
    if (curProtocol === 'https'){
   bp.src = 'https://zz.bdstatic.com/linksubmit/push.js';
  }
  else{
  bp.src = 'http://push.zhanzhang.baidu.com/push.js';
  }
    var s = document.getElementsByTagName("script")[0];
    s.parentNode.insertBefore(bp, s);
})();
</script>

阿里云函数计算配合表格储存制作网页统计工具

2020-07-05T07:42:00.000Z

表格储存

import os
from tablestore import *
import time

OTS_ID = "ID"
OTS_SECRET = "SEC"
OTS_ENDPOINT = "ENDPOINT"
OTS_INSTANCE = "NAME"
#OTS_STS_TOKEN = os.getenv('OTS_TEST_STS_TOKEN')

table_name = 'visitor_count'
primary_key = [('urls', '/1/1/1')]
columns_to_get = ['numbers']

client = OTSClient(OTS_ENDPOINT, OTS_ID, OTS_SECRET, OTS_INSTANCE)

consumed, return_row, next_token = client.get_row(table_name, primary_key, columns_to_get)
if return_row != None:
    print(return_row.attribute_columns[0][1])

函数计算

from flask import Flask, request

app = Flask(__name__)

@app.route('/', methods=['GET'])
def register():
    #a = request.args.get("1")
    b = str(request.referrer)
    return b

if __name__ == '__main__':
    app.run()

Python博客小助手 (STOP)

2020-06-26T07:40:00.000Z

做了一个python的博客助手可以方便写文章

1.比如可以省略hexo new
2.可以直接在文件选择框中选择文件并一键添加到附件目录
3.程序采用Python Tkinter写成

main.py
import tkinter as tk
import tkinter.filedialog as tkf
import tkinter.messagebox as msg
import os
import re
import shutil
import win32con
import win32clipboard
#from googletrans import Translator
from subprocess import Popen, PIPE

#配置
#box.geometry("500x300")

static_path='C:/Users/Kylin/Desktop/Blog/source/_posts/'
os.chdir(static_path)

run_path='C:/Users/Kylin/Desktop/快速博客/'

win = tk.Tk()
win.title("博客小助手")
win.iconbitmap(run_path + "box.ico")
#translator = Translator()
main_title = ""
#title_tran = ""

#Function
def hexo_new(get_title):
    global main_title
    #global title_tran
    if get_title.replace(" ", "") != "":
        #os_command_origin="powershell -command "
        #poweshell部分文字输入不进去好像有“”等
        os_command_origin = "cmd /c "
        hexo_new_posts = 'hexo new '+get_title
        #os.system(os_command_origin+hexo_new_posts)
        #print(os_command_origin+hexo_new_posts)
        #changed_title=os.popen(os_command_origin+hexo_new_posts).read().decode('utf-8')
        changed_title = Popen(os_command_origin+hexo_new_posts, shell=True,stdout=PIPE, stderr=PIPE).stdout.read().decode('utf-8')
        get_true_title_re = re.compile(r'INFO  Created: ~\\Desktop\\Blog\\source\\_posts\\(.*?)\.md')
        true_title = get_true_title_re.findall(changed_title)[0]
        #赋值
        main_title = true_title #实际文件名
        #title_tran = translator.translate(get_title).text #翻译名
        #写入翻译，弃用tran插件
        #f_t = open(true_title+".md")
        #f_data = f_t.read().replace("translate_title:", "translate_title: " + title_tran)
        #f_t.close()
        #with open(true_title+".md", "w") as f_tt:
        #    f_tt.write(f_data)
    else:
        msg.showinfo("提示", "请输入标题！")

def s_files(def_filenames, def_string_filename):
    global static_path
    global main_title
    cho_msg = ""
    get_the_last = ""
    #应该不会把md文档当作附件用的。。。
    if len(def_filenames) != 0:
        g_main_t = def_filenames[0].replace(static_path, "")
        get_main_title_re = re.compile(r'(.*?)\.md')
        gmtre = get_main_title_re.findall(g_main_t)
        if len(gmtre) != 0:
            main_title = gmtre[0].replace(" ", "")
            msg.showinfo("提示", main_title)
            get_the_last = g_main_t.replace(main_title, "")

        if get_the_last != ".md":
            if main_title != "":
                cho_msg = msg.askokcancel('提示', '需要移动文件到文章附件目录吗？')
                if cho_msg:
                    for i in range(0,len(def_filenames)):
                        def_string_filename.append(def_filenames[i])
                        #get_data["text"]=str(def_string_filename)
                        shutil.move(def_filenames[i], static_path + main_title)
                        get_fujian_re = re.compile(r'[^\\\?\/\*\|<>:"]+?\..*')
                        get_fj = get_fujian_re.findall(def_filenames[i])[0]
                        get_clip_re = re.compile(r'\..*')
                        get_clip = get_clip_re.findall(get_fj)[0]
                        final_clip = "<img src=\""+get_fj+"\" width=\"100%\" alt=\""+get_fj.replace(get_clip,"")+"\">"
                        win32clipboard.OpenClipboard()
                        win32clipboard.EmptyClipboard()
                        win32clipboard.SetClipboardData(win32con.CF_UNICODETEXT, final_clip)
                        win32clipboard.CloseClipboard()
                    #if main_title == "" and msg.askokcancel('提示', '是否需要选择目录？'):
            else:
                #if main_title == "" and len(def_filenames) != 0:
                #    msg.showinfo("提示", "请新建文章！")
                #elif main_title != "" and len(def_filenames) == 0 or main_title == "" and len(def_filenames) == 0:
                    #msg.showinfo("提示", "请选择文件！")
                #elif main_title != "" and cho_msg != True:
                #    msg.showinfo("提示", "请同意！")
                pass

        elif get_the_last == ".md":
            pass

def shell_files():
    #global main_title
    filenames = tkf.askopenfilenames()
    string_filename = []
    s_files(filenames, string_filename)

def select_o():
    #win.destroy()

    box = tk.Tk()
    box.title("新建文章")
    box.iconbitmap(run_path + "box.ico")

    title = tk.Entry(box, text='文章标题', width=20)
    title.grid(row=1, column=2, padx=10, pady=10)

    post_title = tk.Button(box, text='生成文章', width=7, height=1, command=lambda:hexo_new(title.get()))
    post_title.grid(row=1, column=6, padx=10, pady=10)

    select_files = tk.Button(box, text='选择...', width=7, height=1, command=shell_files)
    select_files.grid(row=2, column=6, padx=10, pady=10)

    get_data = tk.Label(box)
    get_data.grid(row=2, column=2)

    box.mainloop()

def select_t():
    box = tk.Tk()
    box.title("修改图片")
    box.iconbitmap(run_path + "box.ico")

    select_filemd = tk.Button(box, text="选择Markdown文件", command=shell_files)
    select_filemd.grid(row=1, column=1, padx=15, pady=10)

    select_filemd_fujian = tk.Button(box, text="选择附件", command=shell_files)
    select_filemd_fujian.grid(row=2, column=1, padx=10, pady=10)

    box.mainloop()

def get_main_d():
    global main_title
    msg.showinfo("提示", main_title)

#Main

select_one = tk.Button(win, text="新建文章", width=7, height=1, command=select_o)
select_one.grid(row=1, column=1, padx=10, pady=10)

select_l = tk.Label(win, text="OR", width=2, height=1)
select_l.grid(row=1, column=2, padx=5, pady=5)

select_two = tk.Button(win, text="修改图片", width=7, height=1, command=select_t)
select_two.grid(row=1, column=3, padx=10, pady=10)

get_main_t = tk.Button(win, text="Main Title", width=10, height=1, command=get_main_d)
get_main_t.grid(row=2, column=2, padx=0, pady=5)

#v = tk.IntVar()
#r1 = tk.Radiobutton(win, text="one", value=1, variable=v)
#r1.grid(row=3, column=2, padx=0, pady=10)
#if v.get() == 1:
#    clip()

win.mainloop()

Hexo阿里云OSS上传插件（支持校验MD5）

2020-05-15T07:37:00.000Z

这个 Github 里面有 NPM 里面也有，觉得原版hexo-deployer-ali-oss每次都要上传全部文件就自己做了一个，有时间更新

做这个之前属于完全没学习过nodejs，完全面向浏览器编程。该项目制作修改时间2020-05-15 19:45~2020-05-15 22:53

名称叫这个

hexo-deployer-aliyun-oss

预览

hexo-deployer-aliyun-oss部署器使用说明

源项目：https://github.com/wertycn/hexo-deployer-ali-oss
该项目：https://github.com/arkylin/hexo-deployer-aliyun-oss

本项目在源项目的基础上增加了MD5校验工具，这样就可以避免上传重复文件耗时了，本地计算MD5的时间如果不是什么大文件，基本可以忽略不计，后续也可能会加入其他功能。例如：文件排除项、时间或文件大小比对等

在hexo项目下执行安装命令：

npm install hexo-deployer-aliyun-oss --save

在hexo项目配置文件_config.yml中添加如下配置：

deploy:
  type: ali-oss
  region: <您的oss 区域代码>
  accessKeyId: <您的oss  accessKeyId>
  accessKeySecret: <您的oss accessKeySecret>
  bucket: <您的bucket name>

就这么简单然后执行部署命令：

hexo g

hexo d

即可将项目部署到oss中，默认情况下，将文件上传到bucket的根目录下，如果需要部署到其他目录，请在deploy下添加remotePath选项进行指定

remotePath:<您要部署的目录>

安装Arch-Linux记录

2020-04-19T07:35:00.000Z

判定为UEFI设备

Surface Pro 2017

连接WIFI

wifi-menu

设置时间同步

timedatectl set-ntp true

设置分区

fdisk /dev/nvme0n1

（以实际情况为主fdisk -l查看）

设置为gpt磁盘格式

EFI分区64M 建议：260–512 MiB（大概只能用到6M多一点不到7M）

/主分区剩下全部

格式化分区
格式化EFI分区

fdisk: Create a partition with partition type EFI System.
见WIKI：https://wiki.archlinux.org/index.php/EFI_system_partition

格式化主分区，这里使用ext4格式

mkfs.ext4 /dev/nvme0n1p2

SWAP最后再用文件设置，可见我的另一篇博客

其实分区还是文件效果其实差不多的

而且文件还可以随时更改大小不像分区那样麻烦还得扩大缩小，搞不好数据都没了还得重装

挂载分区

mount /dev/nvme0n1p2 /mnt

（挂载目录随意）

你说为啥p2先挂载，因为你的目录得要在/里面

mount /dev/nvme0n1p1 /mnt/efi

(目录随意大小写随意，最后只需在Grub里面设置即可)

安装

更改镜像源地址

默认的源地址为源地址列表的第一个，而连接超时则再试第二个，所以会很慢，而且内置的中文源在好后面…

所以得换源
首先安装nano，不过好像有内置你想用vi或者vim也可以不过我个人感觉nano好用

nano /etc/pacman.d/mirrorlist

在第几行（[ ]标志的后面）那里加入

Server = http://mirrors.tuna.tsinghua.edu.cn/archlinux/$repo/os/$arch

[archlinuxcn]
Server = http://mirrors.tuna.tsinghua.edu.cn/archlinuxcn/$arch

或者

Server = http://mirrors.aliyun.com/archlinux/$repo/os/$arch

[archlinuxcn]
Server = http://mirrors.aliyun.com/archlinuxcn/$arch

或者

Server = http://mirrors.zju.edu.cn/archlinux/$repo/os/$arch

[archlinuxcn]
Server = http://mirrors.zju.edu.cn/archlinuxcn/$arch

Ctrl+O保存

Ctrl+X退出

安装基本包

注：安装时出现报错

perl: warning: Setting locale failed.

perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory

解决方案1：

nano /root/.bashrc

在最底部添加上一句

export LC_ALL=C

或者直接运行

echo "export LC_ALL=C" >> /root/.bashrc

然后执行一下：

source /root/.bashrc

2
When you install/update linux kernel you can see these missing firmware warnings. These drivers are not necessary to run your system, at some point they where excluded from kernel. If these errors disturb you then you can get them from user repositories. The wd719x is a driver for “Western Digital WD7193, WD7197 and WD7296 SCSI cards” and aic94xx is the driver for “Adaptec SAS 44300, 48300, 58300 Sequencer”.

解决方案2：

# Download the missing firmware using your favourite AUR package manager.
yay -S aic94xx-firmware wd719x-firmware
 
# When you run kernel install again, you should not see the error any more.
yay -
S linux

安装上面这些你添加Arch Linux中文源也可以直接用pacman安装
3

解决方案2中的yay安装问题

由于yay为第三方包管理器，所以在安装环境中并没有内置所以得自行安装

git clone https://aur.archlinux.org/yay.git
cd yay
makepkg -si

由于yay不支持在root环境在运行，你还得新建一个账户不过这个好像得在arch-chroot之后进行（捂脸哭/(ㄒoㄒ)/~~）

说明文件（见下）两种都可以，但是yay就是不支持在root环境在运行，而且你用pacstrap也不行啊，我突然想到

To install other packages or package groups, append the names to the pacstrap command above (space separated) or use pacman while chrooted into the new system. For comparison, packages available in the live system can be found in packages.x86_64.

安装

pacstrap -i /mnt base base-devel linux linux-firmware

（-i给你有选择的权利，不过还是默认的好，如有特俗需求可以改）

配置系统

Fstab启动配置文件

genfstab -U /mnt >> /mnt/etc/fstab

Chroot

切换root环境目录

arch-chroot /mnt

设置时区

ln -sf /usr/share/zoneinfo/Asia/Shanghai /etc/localtime

同步系统时钟到硬件

这对某些程序来说很好

hwclock --systohc

更改镜像源地址

见上

配置语言

nano /etc/locale.gen

在文件中找到zh_CN.UTF-8 UTF-8 zh_HK.UTF-8 UTF-8 zh_TW.UTF-8 UTF-8 en_US.UTF-8 UTF-8这四行，去掉行首的#号，保存并退出。

执行

locale-gen

nano /etc/locale.conf

加入

LANG=en_US.UTF-8

如果用中文在某些tty界面会乱码（可以从deepin中学习一下这种配置）

设置主机名

nano /etc/hostname

设置hosts

nano /etc/hosts

如下

127.0.0.1   localhost.localdomain    localhost
::1         localhost.localdomain    localhost
127.0.1.1   myhostname.localdomain myhostname

If the system has a permanent IP address, it should be used instead of 127.0.1.1.

Initramfs

Creating a new initramfs is usually not required, because mkinitcpio was run on installation of the kernel package with pacstrap.

For LVM, system encryption or RAID, modify mkinitcpio.conf(5) and recreate the initramfs image:

mkinitcpio -P

好像在安装时会自动执行然后这里就应该会复现pacstrap的问题3,请解决

设置root密码

passwd

安装你熟悉的常用软件

KDE:https://wiki.archlinux.org/index.php/KDE

DDE:https://wiki.archlinux.org/index.php/Deepin_Desktop_Environment

UEFI systems
Note:
It is recommended to read and understand the Unified Extensible Firmware Interface, Partitioning#GUID Partition Table and Arch boot process#Under UEFI pages.
When installing to use UEFI it is important to boot the installation media in UEFI mode, otherwise efibootmgr will not be able to add the GRUB UEFI boot entry. Installing to the fallback boot path will still work even in BIOS mode since it does not touch the NVRAM.
To boot from a disk using UEFI, an EFI system partition is required. Follow EFI system partition#Check for an existing partition to find out if you have one already, otherwise you need to create it.
Installation
Note:
UEFI firmwares are not implemented consistently across manufacturers. The procedure described below is intended to work on a wide range of UEFI systems but those experiencing problems despite applying this method are encouraged to share detailed information, and if possible the workarounds found, for their hardware-specific case. A GRUB/EFI examples article has been provided for such cases.
The section assumes you are installing GRUB for x86_64 systems. For IA32 (32-bit) UEFI systems (not to be confused with 32-bit CPUs), replace x86_64-efi with i386-efi where appropriate.
First, install the packages grub and efibootmgr: GRUB is the bootloader while efibootmgr is used by the GRUB installation script to write boot entries to NVRAM.

Then follow the below steps to install GRUB:

Mount the EFI system partition and in the remainder of this section, substitute esp with its mount point.
Choose a bootloader identifier, here named GRUB. A directory of that name will be created in esp/EFI/ to store the EFI binary and this is the name that will appear in the UEFI boot menu to identify the GRUB boot entry.
Execute the following command to install the GRUB EFI application grubx64.efi to esp/EFI/GRUB/ and install its modules to /boot/grub/x86_64-efi/.

grub-install --target=x86_64-efi --efi-directory=esp --bootloader-id=GRUB

After the above install completed the main GRUB directory is located at /boot/grub/. Note that grub-install also tries to create an entry in the firmware boot manager, named GRUB in the above example.

Remember to #Generate the main configuration file after finalizing the configuration.

Tip: If you use the option —removable then GRUB will be installed to esp/EFI/BOOT/BOOTX64.EFI (or esp/EFI/BOOT/BOOTIA32.EFI for the i386-efi target) and you will have the additional ability of being able to boot from the drive in case EFI variables are reset or you move the drive to another computer. Usually you can do this by selecting the drive itself similar to how you would using BIOS. If dual booting with Windows, be aware Windows usually places an EFI executable there, but its only purpose is to recreate the UEFI boot entry for Windows.
Note:
—efi-directory and —bootloader-id are specific to GRUB UEFI, —efi-directory replaces —root-directory which is deprecated.
You might note the absence of a device_path option (e.g.: /dev/sda) in the grub-install command. In fact any device_path provided will be ignored by the GRUB UEFI install script. Indeed, UEFI bootloaders do not use a MBR bootcode or partition boot sector at all.
Make sure to run the grub-install command from the system in which GRUB will be installed as the boot looader. That means if you are booting from the live installation environment, you need to be inside the chroot when running grub-install. If for some reason it is necessary to run grub-install from outside of the installed system, append the —boot-directory= option with the path to the mounted /boot directory, e.g —boot-directory=/mnt/boot.
See UEFI troubleshooting in case of problems. Additionally see GRUB/Tips and tricks#UEFI further reading.

人人通APP的惨痛经历

2020-04-09T07:34:00.000Z

当你看到这篇文章的时候我应该已经好多了
真的，我今天写完卷子后几分钟交卷然后就提示不让交了
好吧，虽然试卷应该按时交，但是我还是很烦
甚至作文都是手打的，然后提交了后提示时间过来，不让补交，我真的勺了哎
那个惨状是没录视频，不然。。。。。。
还不知道怎么办，好吧幸亏只是模拟考试，不过我的作文还是没了
当时看着这个一闪而过的红色惊叹号我都。。。

别说了别说了，痛苦
这好像是我第一次没交卷子👀😢
好吧，希望我以后还是按照时间早点交卷，别交迟了
欸，老师看在只有26个同学交了的份上又新建了一张答题卡
哈，希望是第一次也是最后一次，有些事还是早做完好，别拖！
一定要遵守时间

Typecho迁移Hexo的Python脚本

2020-04-09T07:27:00.000Z

最近换博客Typecho感觉还是有点臃肿。。好吧虽然相比WordPress好多了
所以就换了Hexo，而且在本地也支持方便迁移，哈
脚本如下，按照自己的修改

import requests
import os
import shutil
import re
from subprocess import Popen, PIPE 
from bs4 import BeautifulSoup

for i in range(0,123):
    url='https://your.domain/admin/write-post.php?cid='
    url=url+str(i)

    cookies_text=r'你的cookies'

    cookies = {}
    for line in cookies_text.split(';'):
        key, value = line.split('=', 1)
        cookies[key] = value

    resp = requests.get(url,cookies=cookies)
    #<Response [404]>
    #<Response [200]>
    if str(resp) == '<Response [200]>':
        get_text=resp.text
        html=BeautifulSoup(get_text,'html.parser')
        get_title=html.find('input',id='title')["value"]
        get_title_translate=html.find('input',id='slug')["value"]
        get_data=html.find('textarea',id='text').text
        get_time=html.find('input',id='date')["value"]+":00"        

        check_1=html.find('input',id='category-1').attrs#常用配置
        check_2=html.find('input',id='category-2').attrs#技巧
        check_3=html.find('input',id='category-3').attrs#生活随笔
        check_4=html.find('input',id='category-4').attrs#学习
        check_10=html.find('input',id='category-10').attrs#Android Develop

        #替换标题中文件夹禁用字符
        get_title_replace=get_title
        get_title_replace=get_title_replace.replace("\\","")
        get_title_replace=get_title_replace.replace("/","")
        get_title_replace=get_title_replace.replace(":","：")
        get_title_replace=get_title_replace.replace("*","")
        get_title_replace=get_title_replace.replace("?","？")
        get_title_replace=get_title_replace.replace("\"","")
        get_title_replace=get_title_replace.replace("<","《")
        get_title_replace=get_title_replace.replace(">","》")
        get_title_replace=get_title_replace.replace("|","")
        #Hexo规则
        get_title_replace=get_title_replace.replace(" ","-")

        if "checked" in check_1:
            check_1_status=check_1["checked"]
            check_1_name="常用配置"
        else:
            check_1_status="false"
            check_1_name=""

        if "checked" in check_2:
            check_2_status=check_2["checked"]
            check_2_name="技巧"
        else:
            check_2_status="false"
            check_2_name=""

        if "checked" in check_3:
            check_3_status=check_3["checked"]
            check_3_name="生活随笔"
        else:
            check_3_status="false"
            check_3_name=""

        if "checked" in check_4:
            check_4_status=check_4["checked"]
            check_4_name="学习"
        else:
            check_4_status="false"
            check_4_name=""

        if "checked" in check_10:
            check_10_status=check_10["checked"]
            check_10_name="Android Develop"
        else:
            check_10_status="false"
            check_10_name=""

        #写入hexo
        os.chdir('C:\/Users\/Kylin\/Desktop\/Blog\/source\/_posts')
        #os_command_origin="powershell -command "
        #poweshell部分文字输入不进去好像有“”等
        os_command_origin="cmd /c "
        hexo_new_posts='hexo new '+get_title_replace
        #os.system(os_command_origin+hexo_new_posts)
        #print(os_command_origin+hexo_new_posts)
        #changed_title=os.popen(os_command_origin+hexo_new_posts).read().decode('utf-8')
        changed_title=Popen(os_command_origin+hexo_new_posts, shell=True,stdout=PIPE, stderr=PIPE).stdout.read().decode('utf-8')
        get_true_title_re=re.compile(r'INFO  Created: ~\\Desktop\\Blog\\source\\_posts\\(.*?)\.md')
        true_title=get_true_title_re.findall(changed_title)[0]

        #图片标签
        #re_img=u'!\[(.*?)\]\[([1-9]*)\]'
        #re_img_get_name=re.search(re_img,get_data)[1]
        #re_img_get_num=re.search(re_img,get_data)[2]
        #img_src_stick='<img src=\"'+'\" width="100%" alt=\"'+'\">'

        #查找写入配置
        #搜寻图片
        get_img_name_re=re.compile(r'!\[(.*?)\]\[[0-9]*\]')
        get_img_url_name_re=re.compile(r'\[[0-9]*\]: https://www\.xyz\.blue/wp-content/uploads/[0-9]*/[0-9]*/([0-9]*?\.png)')
        get_img_name_lists=get_img_name_re.findall(get_data)
        get_img_url_lists=get_img_url_name_re.findall(get_data)
        #替换图片文本
        get_data=re.sub(get_img_url_name_re,"",get_data)
        if len(get_img_name_lists) == len(get_img_url_lists) and get_img_name_lists != []:
            for j in range(0,len(get_img_name_lists)):
                img_src="<img src=\""+get_img_name_lists[j]+"\" width=\"100%\" alt=\""+get_img_name_lists[j].replace(".png","")+"\">"
                get_data=get_data.replace("!["+get_img_name_lists[j]+"]"+"["+str(j+1)+"]",img_src)#![poste.png][1]
                #移动图片
                if not os.path.isfile(true_title+'/'+get_img_name_lists[j]):
                    shutil.move('uploads/'+get_img_url_lists[j],true_title+'/'+get_img_name_lists[j])
                    print(true_title+'/'+get_img_name_lists[j])
        else:
            print("图片匹配出错")

        if get_img_name_lists != []:
            get_top_img='/'+get_time[0:4]+'/'+get_time[5:7]+'/'+get_time[8:10]+'/'+get_title_translate+'/'+get_img_name_lists[0]
        else:
            get_top_img=''
            print("cid:",i,"未找到图片")

        #合成写入内容
        ha_temp_main=['---\n']
        ha_temp_main.append('title: '+get_title+'\n')#'title: 使用docker搭建邮件服务器\n'
        #设置分类
        ha_temp_main.append('categories:\n')
        if check_1_status == "true":
            ha_temp_main.append('  - ['+check_1_name+']\n')#'  - []\n'
        if check_2_status == "true":
            ha_temp_main.append('  - ['+check_2_name+']\n')#'  - []\n'
        if check_3_status == "true":
            ha_temp_main.append('  - ['+check_3_name+']\n')#'  - []\n'
        if check_4_status == "true":
            ha_temp_main.append('  - ['+check_4_name+']\n')#'  - []\n'
        if check_10_status == "true":
            ha_temp_main.append('  - ['+check_10_name+']\n')#'  - []\n'
        #标签不知道怎么加，而且之前也没设置过标签，以后自己慢慢加吧
        ha_temp_main.append('tags:\n')
        ha_temp_main.append('')#'  - []\n'
        ha_temp_main.append('date: '+get_time+'\n')#date: 2020-04-02 23:12:09\n
        ha_temp_main.append('translate_title: '+get_title_translate+'\n')#'translate_title:\n'
        #翻译不同会让头图404
        #ha_temp_main.append('translate_title:\n')#'translate_title:\n'
        ha_temp_t_1=['keywords:\n', 'description:\n',]
        ha_temp_main.append(ha_temp_t_1)
        ha_temp_main.append('top_img: '+get_top_img+'\n')#'top_img:\n'
        ha_temp_t_2=['toc:\n', 'toc_number:\n', 'copyright:\n', 'mathjax:\n', 'katex:\n', 'hide:\n', 'top:\n', '---\n']
        ha_temp_main.append('comments:\n')
        ha_temp_main.append('cover: '+get_top_img+'\n')#'cover:\n'
        ha_temp_main.append(ha_temp_t_2)
        ha_temp_main.append(get_data)
        #写入文件
        f=open(true_title+".md","w",encoding='utf-8')
        for lines in ha_temp_main:
            f.writelines(lines)
        f.close()
        print('转移cid:',i,"成功")

    else:
        print('cid:',i,"找不到")

代码下载

静态页面跳转代码留存

2020-04-04T07:25:00.000Z

静态页面跳转代码一

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="viewport" content="width=device-width">
<meta name="robots" content="noindex, nofollow" />
<meta charset="UTF-8">
<title>页面加载中,请稍候...</title>
<style>
body{margin:0;padding:0;background-image: url(//www.ioioi.cn/arv/img/index.jpg);background-repeat:no-repeat;font-family:Arial,'微软雅黑','宋体',sans-serif}.main{position:absolute;left:calc(50% - 200px);top:calc(50% - 13em)}.alert-box{display:none;position:relative;margin:auto;padding:18px 85px 22px;border-radius:10px 10px 0 0;background-color:rgba(255,255,255,.75);box-shadow:5px 9px 17px rgba(102,102,102,.75);width:286px;color:#FFF;text-align:center}.alert-box p{margin:0}.alert-head{color:#242424;font-size:28px}.alert-btn{display:block;border-radius:10px;background-color:#4AB0F7;height:55px;line-height:55px;width:286px;color:#FFF;font-size:20px;text-decoration:none;letter-spacing:2px}.alert-btn:hover{background-color:#6BC2FF}
</style>
</head>
<body>
<div class="main">
    <div id="js-alert-box" class="alert-box" style="display:block">
            <div id="js-alert-head" class="alert-head">
                点击前往 Kylin's Blog</div>
            </br>
            <a id="js-alert-btn" class="alert-btn" href="https://www.ioioi.cn/">立即前往</a>
    </div>
</div>
</body>
</html>

效果图

下载预览链接

如何对Hexo进行标题翻译

2020-03-22T07:22:00.000Z

下载hexo-translate-title即可

npm install hexo-translate-title-unchange --save

个人开发，可能有问题，暂不更新
请使用原版

npm install hexo-translate-title --save

如何对部分文章不进行翻译或者进行手动翻译，以后再出教程

Hexo分类解释

2020-03-22T07:21:00.000Z

在Hexo的_config.yaml里面设置category_map和tags_map
下面这个是例子

{
  学习: Study,
  生活随笔: Life,
  常用配置: common,
  技巧: skill,
  代码: Code,
  安卓开发: android_develop
}

all-maps.png

安卓文本操作菜单相关说明

2020-03-12T09:44:00.000Z

关于具体情况我已经发帖到了花粉俱乐部
经过一些简单的探究，第一个搜索可能是安卓或者华为系统自身内嵌的一个搜索，之后第二个搜索为华为自带浏览器的搜索，当存在华为浏览器的时候第一个搜索默认指向为华为浏览器。
现象还原：在设置-应用里面把华为浏览器给禁用了，那么第二个搜索就会消失，第一个搜索回提示你要你选择默认打开的软件。
实现原理：见简书社区简名的文章
后续也有可能按照他的方式去做一些软件，学习一下这个，希望这个刚挖的坑不要太大(ฅ´ω`ฅ)
然后了解到还有一些其他鬼软件为了流量或者为了方便快捷等因素会把其跳转插入到这个长按的位置上，比如网易新闻，新浪新闻，并且没有关闭的位置
建议华为系统能够增加长按文本操作菜单的管理设置

你好，世界！ (Hexo)

2020-03-12T07:08:00.000Z

开始从Typecho转到Hexo，文章会逐步迁移过来的

现在又用回去了 2020-12-06

关于生成手写字体

2020-03-10T07:25:45.000Z

网站
http://flexifont.com/
其配置为
Apache/2.2.21 (Win64) PHP/5.3.8 mod_wsgi/3.5 Python/2.7.6

做个记录
手写字体生成
基于GAN的字体风格迁移

风格迁移在图像应用

https://github.com/LDOUBLEV/style_transfer-perceptual_loss

基于风格迁移的手写字体生成

http://www.dataguru.cn/article-11281-1.html

论文：http://www.doc88.com/p-8058499366708.html

关于暂停AS-Kotlin学习的说明

2020-03-10T05:41:09.000Z

暂停AS-Kotlin学习，改为Java
理由：网络上面好多程序都是由Java写成的，方便初学者参考，而Kotlin属于新的东西。给予的参考类型太少，对初学者不友好，所以转为学习Java，如果等熟练的话再转学Kotlin吧

Android目标一：XML输出（正在进行中）

2020-03-07T16:36:00.000Z

创建空白Hello World项目
进入res/layout/activity_main.xml
可以看见

<?xml version="1.0" encoding="utf-8"?>
<androidx.constraintlayout.widget.ConstraintLayout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    xmlns:tools="http://schemas.android.com/tools"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    tools:context=".MainActivity">

    <TextView
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:text="Hello World!"
        app:layout_constraintBottom_toBottomOf="parent"
        app:layout_constraintLeft_toLeftOf="parent"
        app:layout_constraintRight_toRightOf="parent"
        app:layout_constraintTop_toTopOf="parent" />

</androidx.constraintlayout.widget.ConstraintLayout>

其中不谈上面一部分
看下面一部分

android:layout_width="wrap_content"

这个为文字宽度随文本长度变化二变化

android:layout_height="wrap_content"

同理这个也是

android:text="Hello World!"

这个就是显示内容

app:layout_constraintBottom_toBottomOf="parent"
app:layout_constraintLeft_toLeftOf="parent"
app:layout_constraintRight_toRightOf="parent"
app:layout_constraintTop_toTopOf="parent"

这个就应该是定位显示内容，都为继承父配置

当你试着去重新手动设置一个的时候会显示

会提示

This view is not constrained. It only has designtime positions, so it will jump to (0,0) at runtime unless you add the constraints  The layout editor allows you to place widgets anywhere on the canvas, and it records the current position with designtime attributes (such as layout_editor_absoluteX). These attributes are not applied at runtime, so if you push your layout on a device, the widgets may appear in a different location than shown in the editor. To fix this, make sure a widget has both horizontal and vertical constraints by dragging from the edge connections.  Issue id: MissingConstraints

此视图不受约束。它只有设计时位置，因此它将在运行时跳转到（0,0），除非您添加约束，否则布局编辑器允许您将小部件放置在画布上的任何位置，并且它使用设计时属性（例如布局编辑器绝对值）记录当前位置。这些属性在运行时不应用，因此如果您在设备上推送布局，小部件可能会出现在与编辑器中显示的位置不同的位置。要解决此问题，请通过从边缘连接拖动来确保小部件同时具有水平和垂直约束。问题id:缺少约束

Hardcoded string "test", should use @string resource  Hardcoding text attributes directly in layout files is bad for several reasons:  * When creating configuration variations (for example for landscape or portrait) you have to repeat the actual text (and keep it up to date when making changes)  * The application cannot be translated to other languages by just adding new translations for existing string resources.  There are quickfixes to automatically extract this hardcoded string into a resource lookup.  Issue id: HardcodedText

硬编码字符串“test”，应该在布局文件中直接使用@string资源硬编码文本属性有几个原因：*创建配置变体（例如横向或纵向）时，必须重复实际文本（并在进行更改时保持最新）*仅添加新的现有字符串资源的翻译。有一些快速修复程序可以自动将此硬编码字符串提取到资源查找中。问题id:HardcodedText

对于下面这个我们点fix it

则会添加值到res/value/strings里面去

添加约束
本来不会的不过幸好AS提供图形界面可以直接拖动，真的对初学者很友好
那么我们就知道了它的道理
以左上角为原点，往右下增到

app:layout_constraintHorizontal_bias="1.0"

这个可以说为X轴当到最右边就为1.0

app:layout_constraintVertical_bias="0.0"

这个就可以说是Y轴到最下边就是1.0

android:layout_marginStart="84dp"

MarginStart指的是控件距离开头View部分的间距大小
我们在写layout布局的时候，我们会发现有这样几个比较相似的属性：

MarginStart   MarginLeft
MarginEnd    MarginRight

这些属性的区别是什么? 根据api注释，我们得知MarginStart指的是控件距离开头View部分的间距大小，MarginLeft则指的是控件距离左边View部分的间距大小，MarginEnd和MarginRight同理。

一般情况下，View开始部分就是左边，但是有的语言目前为止还是按照从右往左的顺序来书写的，例如阿拉伯语，在Android 4.2系统之后，Google在Android中引入了RTL布局，更好了支持了由右到左文字布局的显示，为了更好的兼容RTL布局，google推荐使用MarginStart和MarginEnd来替代MarginLeft和MarginRight，这样应用可以在正常的屏幕和由右到左显示文字的屏幕上都保持一致的用户体验。

准备开始新篇章 -- Android Studio

2020-03-07T16:33:00.000Z

准备开始新篇章 — Android Studio
近日想做做安卓App
语言选择~~Kotlin~~Java

目标
总. 制作一个能够调用“今日诗词”API的软件，数据示例如下

{"status":"success","data":{"id":"5b8b9572e116fb3714e6fba1","content":"谁家玉笛暗飞声，散入春风满洛城。","popularity":607000,"origin":{"title":"春夜洛城闻笛 / 春夜洛阳城闻笛","dynasty":"唐代","author":"李白","content":["谁家玉笛暗飞声，散入春风满洛城。","此夜曲中闻折柳，何人不起故园情。"],"translate":["是谁家精美的笛子暗暗地发出悠扬的笛声。随着春风飘扬，传遍洛阳全城。","就在今夜的曲中，听到故乡的《折杨柳》，哪个人的思乡之情不会因此而油然而生呢？"]},"matchTags":["春","风"],"recommendedReason":"","cacheAt":"2020-03-08T00:28:56.013294"},"token":"Uz2/+bh5Dt+n7INLEr/iYzpclPxy7Rzg","ipAddress":"27.18.69.224","warning":null}

1. 完成Hello World项目，研究输出TextView
开始时间：2020/03/07
结束时间：？？？
[post cid=“107” /]
2. 列表项目
3. 列表项目

WSL修改默认用户

2020-03-06T08:52:00.000Z

以管理员的方式打开PowerShell或者cmd
①：如果你是在Microsoft Store里面安装的，则切换到C:\Users\Kylin\AppData\Local\Microsoft\WindowsApps目录下
②：如果你是在GitHub等其他位置通过源码安装的请切换到你的源码目录

注：一下fedoraremix可以更换为ubuntu、debian等已安装的发行版

输入下面这个查看帮助

./fedoraremix --help

由于用Microsoft Store安装的已经预先设置好了环境变量所以可以不加./
输入下面这个修改默认用户

fedoraremix config  --default-user root

你喝的水 --水的三相点

2020-03-05T07:52:00.000Z

如何一键删除微博

2020-03-01T13:21:51.000Z

浏览器代码

// ==UserScript==
// @name Weibored.js
// @namespace http://vito.sdf.org
// @version 0.1
// @description 删除所有微博
// @author Vito Van
// @match http://weibo.com/p/*
// @grant none
// ==/UserScript==
'use strict';
var s = document.createElement("script");
s.setAttribute("src","https://lib.sinaapp.com/js/jquery/2.0.3/jquery-2.0.3.min.js ");
s.onload = function(){
for(var i=0;i<100;i++){
setTimeout(function(){
$('a[action-type="fl_menu"]')[0].click();
$('a[title="删除此条微博"]')[0].click();
$('a[action-type="ok"]')[0].click();
},1000*i);
}
}
document.head.appendChild(s);

网络收集，侵权联系删除

Windows Server 2012 将我的电脑放到桌面

2020-02-25T23:34:44.000Z

WIN+R

rundll32.exe shell32.dll,Control_RunDLL desk.cpl,,0

Caddy_V2 Websocket说明

2020-02-17T15:29:25.000Z

https://caddy.community/t/unrecognized-subdirective-websocket/6493

header_up Connection {http.request.header.Connection}
header_up Upgrade {http.request.header.Upgrade}

In v2, you do not need to do anything to enable websockets.
Websockets should work with v2’s reverse proxy by default.

树莓派更改IP地址为静态地址 --测试版

2020-02-13T13:54:00.000Z

树莓派更改IP地址为静态地址，方便端口映射

首先，官方镜像的树莓派是基于Debian系统，所以命令会宇它有类似

那么更改IP也是一样

注意：未经过测试可能出现连不上网的情况
恢复方法

sudo rm -rf /etc/dhcpcd.conf
sudo cp /etc/dhcpcd.conf.bak /etc/dhcpcd.conf
systemctl restart dhcpcd

一：明确网络连接方式，及网卡名称
如通过网线连接会出现eth0网卡或ens0网卡
WiFi连接则出现wlan0等

ifconfig

如果提示command not found则需要安装net-tools包

sudo apt-get install net-tools -y

第一个为Docker虚拟网卡不管
第二个则为真实网卡
二：修改配置
复制来备份配置文件

sudo cp /etc/dhcpcd.conf /etc/dhcpcd.conf.bak

sudo nano /etc/dhcpcd.conf

如果提示command not found则需要安装nano包,当然你也可以用vi或者vim

sudo apt-get install nano -y

再末尾添加配置
请勿直接复制

interface eth0
static ip_address=192.168.0.10/24    
static routers=192.168.0.1
static domain_name_servers=192.168.0.1 8.8.8.8

或者

interface wlan0
static ip_address=192.168.0.10/24    
static routers=192.168.0.1
static domain_name_servers=192.168.0.1 8.8.8.8

eth0或wlan0为你真实网卡的名称
ip_address就是静态IP , 后面要接/24 , 最好往后设一点
routers是网关
static domain_name_servers是DNS
Ctrl+o 回车保存 Ctrl+x退出编辑，当然你用vi或者vim也可以

systemctl restart dhcpcd

重启dhcpcd网络
三：登录路由器查看IP地址

PHP编译选项--with和--enable的区别

2020-02-02T07:05:39.000Z

enable多代表不依赖外部库便可以直接编译
with大多需要依赖于第三方的lib

"/usr/share/cracklib/pw_dict.pwd: No such file or directory"解决方法

2020-02-01T07:52:55.000Z

在Linux下修改用户密码

1.直接运行 passwd 用户名,输入新密码，再确认一遍，重启生效

2.如果出现以下错误：

/usr/share/cracklib/pw_dict.pwd: No such file or directory

原因是缺少cracklib库

解决办法：安装cracklib-dicts

Fedora

dnf -y install cracklib-dicts

Docker内安装Mysql/Mariadb提示"服务器和客户端上指示的 HTTPS 之间不匹配"解决方案

2020-01-30T05:05:36.000Z

使用docker安装phpmyadmin，启动成功登录，出现提示：服务器和客户端上指示的 HTTPS 之间不匹配。这可能导致 phpMyAdmin 无法正常工作或存在安全风险。请修复您的服务器配置以正确指示 HTTPS。

以前phpmyadmin是直接安装在nginx里的，没有这个问题。现在用caddy做为代理。外部访问使用https，内部用http。

解决方法是修改参数：

$cfg['PmaAbsoluteUri'] = 'https://pma.xxx.com';

或者

在docker中启动，可以在启动时指定环境参数（该参数在官方文档里没有但是有效）：

-e PMA_ABSOLUTE_URI=https://pma.xxx.com

阿里云运维编排实用配置

2020-01-28T11:49:00.000Z

当你使用便宜的的竞价云服务器时，肯定会担心数据问题那么，一下就可以帮你解决问题。
具体为：定时任务-关机-创建镜像-恢复镜像-开机-邮件提醒
后续可能会更新
请关注我的Github：https://github.com/arkylin/Aliyun_OOS_Backup_ECS
此文未经本人允许，禁止转载！
框架如下

FormatVersion: OOS-2019-06-01
Description:
  en: Regularly create ECS images.
  zh-cn: 定时创建ECS镜像。
  name-en: Regularly-create-ECS-images
  name-zh-cn: 定时创建ECS镜像
Parameters:
  targets:
    Type: Json
    AssociationProperty: Targets
    AssociationPropertyMetadata:
      ResourceType: 'ALIYUN::ECS::Instance'
  instanceId:
    Description:
      en: The ID of ECS instance.
      zh-cn: ECS实例ID。
    Type: String
  Imagesbasic:
    Description:
      en: The ID of Imagees.
      zh-cn: 基本镜像ID。
    Type: String
  cron:
    Description:
      en: 'The cron expression, refer them here: https://www.alibabacloud.com/help/zh/faq-detail/64769.htm. The minimum interval is one minute.'
      zh-cn: 'cron表达式，详情参考：https://www.alibabacloud.com/help/zh/faq-detail/64769.htm'
    Type: String
    AssociationProperty: Cron
    Default: 0 0 12 ? * *
  endDate:
    Description:
      en: 'The end date of time trigger. Format: yyyy-MM-ddThh:mm:ssZ.'
      zh-cn: '时间触发器结束时间。格式：yyyy-MM-ddThh:mm:ssZ'
    Type: String
    AssociationProperty: DateTime
    AssociationPropertyMetadata:
      Format: 'YYYY-MM-DDThh:mm:ssZ'
  rateControl:
    Description:
      en: Concurrency ratio of task execution.
      zh-cn: 任务执行的并发比率。
    Type: Json
    AssociationProperty: RateControl
    Default:
      Mode: Concurrency
      MaxErrors: 0
      Concurrency: 10
  OOSAssumeRole:
    Description:
      en: The RAM role to be assumed by OOS.
      zh-cn: OOS扮演的RAM角色。
    Type: String
    Default: OOSServiceRole
RamRole: '{{ OOSAssumeRole }}'


Tasks:

  - Name: timerTrigger
    Action: 'ACS::TimerTrigger'
    Description:
      en: Triggers a task as scheduled by specifying Cron expression.
      zh-cn: 通过指定Cron表达式按计划触发任务。
    Properties:
      Type: cron
      Expression: '{{ cron }}'
      EndDate: '{{ endDate }}'

  - Name: getInstance
    Description:
      en: Views the ECS instances.
      zh-cn: 获取ECS实例。
    Action: 'ACS::SelectTargets'
    Properties:
      ResourceType: 'ALIYUN::ECS::Instance'
      Filters:
        - '{{ targets }}'
    Outputs:
      instanceIds:
        Type: List
        ValueSelector: 'Instances.Instance[].InstanceId'

  - Name: StopInstance
    Action: 'ACS::ECS::StopInstance'
    Description: Stops an ECS instance.
    Properties:
      instanceId: '{{ ACS::TaskLoopItem }}'
    OnError: 'ACS::NEXT'
    Loop:
      RateControl: '{{ rateControl }}'
      Items: '{{ getInstance.instanceIds }}'

  - Name: createImage
    Action: 'ACS::ECS::CreateImage'
    Description:
      en: Create new image with the specified image name and instance ID.
      zh-cn: 通过指定实例ID和镜像名称创建新的镜像。
    Properties:
      instanceId: '{{ ACS::TaskLoopItem }}'
      imageName: 'Auto_{{ ACS::ExecutionId }}_{{ ACS::TaskLoopItem }}'
    Loop:
      Items: '{{ getInstance.instanceIds }}'
      RateContral: '{{ rateControl }}'
      Outputs:
        imageIds:
          AggregateType: 'Fn::ListJoin'
          AggregateField: imageId
    OnError: ReplaceSystemDiskBasic
    Outputs:
      imageId:
        ValueSelector: imageId
        Type: String

  - Name: ReplaceSystemDisk
    Action: 'ACS::ECS::ReplaceSystemDisk'
    Description: Replaces the system disk of an ECS instance.
    Properties:
      instanceId: '{{ instanceId }}'
      imageId: '{{ ACS::TaskLoopItem }}'
    OnError: ReplaceSystemDiskBasic
    OnSuccess: NotifyByMailYES
    Loop:
      Items: '{{ createImage.ImageIds }}'
      Outputs:
        ImageIds:
          AggregateType: 'Fn::ListJoin'
          AggregateField: ImageId

  - Name: ReplaceSystemDiskBasic
    Action: 'ACS::ECS::ReplaceSystemDisk'
    Description: Replaces the system disk of an ECS instance.
    OnError: NotifyByMailNONO
    OnSuccess: NotifyByMailNO
    Properties:
      instanceId: '{{ instanceId }}'
      imageId: '{{ Imagesbasic }}'

  - Name: NotifyByMailNONO
    Action: ACS::Notify
    Properties:
        NotifyType: Mail
        Mail:
            Host: hwsmtp.exmail.qq.com
            Port: 465
            Username: notify@xyz.blue
            Password: XXXXXXXXXXXXXXX
            Subject: BIG Error Auto Images
            Body: Unable return to Basic
            From: notify@xyz.blue
            To:  [123456789@qq.com,987654321@qq.com]
    OnSuccess: 'ACS::END'
    OnError: 'ACS::END'

  - Name: NotifyByMailNO
    Action: ACS::Notify
    Properties:
        NotifyType: Mail
        Mail:
            Host: hwsmtp.exmail.qq.com
            Port: 465
            Username: notify@xyz.blue
            Password: XXXXXXXXXXXXXXX
            Subject: Error Auto Images
            Body: Return to Basic
            From: notify@xyz.blue
            To:  [123456789@qq.com,987654321@qq.com]
    OnSuccess: 'ACS::END'
    OnError: 'ACS::END'

  - Name: NotifyByMailYES
    Action: ACS::Notify
    Properties:
        NotifyType: Mail
        Mail:
            Host: hwsmtp.exmail.qq.com
            Port: 465
            Username: notify@xyz.blue
            Password: XXXXXXXXXXXXXXX
            Subject: YES Auto Images
            Body: YES TO MAKE
            From: notify@xyz.blue
            To:  [123456789@qq.com,987654321@qq.com
    OnSuccess: 'ACS::END'
    OnError: 'ACS::END'

Outputs:
  imageIds:
    Type: List
    Value: '{{ createImage.imageIds }}'

非交互式修改SSH密码

2020-01-28T11:39:00.000Z

方式1：

echo "password" | passwd testuser --stdin > /dev/null 2>&1

方式2：

echo testuser:password|chpasswd

在shell脚本和Dockerfile中请使用方式2

阿里云Nas加密和非加密区别以及实机评测

2020-01-28T09:27:00.000Z

什么是文件存储NAS
阿里云文件存储（Network Attached Storage，简称 NAS）是面向阿里云 ECS 实例、E-HPC 和容器服务等计算节点的文件存储服务。

定义
阿里云文件存储 NAS 是一个可共享访问、弹性扩展、高可靠以及高性能的分布式文件系统。它基于 POSIX 文件接口，天然适配原生操作系统，提供共享访问，同时保证数据一致性和锁互斥。

NAS 提供了简单的可扩展文件存储以供与 ECS 配合使用，多个ECS实例可以同时访问 NAS 文件系统，并且存储容量会随着您添加和删除文件而自动弹性增长和收缩，为在多个实例或服务器上运行的工作负载和应用程序提供通用数据源。

NAS 支持丰富的应用场景，详情请参见应用场景。

NAS 提供了容量型、性能型以及极速型存储类型，更多详情请参见存储类型。

产品优势
NAS 在成本、安全、简单、可靠性以及性能上都具有自身的优势。

成本
一个 NAS 文件系统可以同时挂载到多个计算节点上，由这些节点共享访问，从而节约大量拷贝与同步成本。
单个 NAS 文件系统的性能能够随存储容量线性扩展，使用户无需购买高端的文件存储设备，大幅降低硬件成本。
使用 NAS文件存储，您只需为文件系统使用的存储空间付费，不需要提前配置存储，并且不存在最低费用或设置费用。更多详情，请参见计量项和计费说明。
NAS 的高可靠性能够降低数据安全风险，从而大幅节约维护成本。
简单
一键创建文件系统，无需部署维护文件系统。

安全
基于 RAM 实现的资源访问控制，基于VPC实现的网络访问隔离，结合文件存储 NAS 的传输加密与存储加密特性，保障数据不被窃取或篡改。

高可靠性
NAS 提供 99.999999999% 的数据可靠性，能够有效降低数据安全风险。

高性能
基于分布式架构文件系统，随着容量的增长性能线性扩展，提供远高于传统存储的性能。

兼容性
NAS 文件存储提供良好的协议兼容性，支持 NFS 和 SMB 协议方案，兼容POSIX 文件系统访问语义，提供强大的数据一致性和文件锁定。
在 NAS 中，任何文件修改成功后，用户都能够立刻看到修改结果，便于用户实时修改存储内容。

test1为加密，test2为非加密

test1 随机读IOPS设置

[root@super /]# fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=4K -size=1G -time_based -runtime=60 -name=Fio -directory=/test1
Fio: (g=0): rw=randread, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=128
fio-3.17
Starting 1 process
Fio: Laying out IO file (1 file / 1024MiB)
Jobs: 1 (f=1): [r(1)][100.0%][r=97.8MiB/s][r=25.0k IOPS][eta 00m:00s]
Fio: (groupid=0, jobs=1): err= 0: pid=1482: Mon Jan 27 23:33:22 2020
  read: IOPS=24.1k, BW=94.3MiB/s (98.9MB/s)(5659MiB/60006msec)
    slat (nsec): min=1871, max=4225.7k, avg=8454.96, stdev=17814.51
    clat (usec): min=1150, max=66695, avg=5291.30, stdev=1830.86
     lat (usec): min=1157, max=66711, avg=5299.96, stdev=1830.83
    clat percentiles (usec):
     |  1.00th=[ 2409],  5.00th=[ 2933], 10.00th=[ 3294], 20.00th=[ 3785],
     | 30.00th=[ 4228], 40.00th=[ 4621], 50.00th=[ 5080], 60.00th=[ 5473],
     | 70.00th=[ 5997], 80.00th=[ 6587], 90.00th=[ 7504], 95.00th=[ 8455],
     | 99.00th=[10683], 99.50th=[11994], 99.90th=[17171], 99.95th=[19268],
     | 99.99th=[35914]
   bw (  KiB/s): min=87160, max=104926, per=99.98%, avg=96554.23, stdev=3373.87, samples=120
   iops        : min=21790, max=26231, avg=24138.51, stdev=843.44, samples=120
  lat (msec)   : 2=0.13%, 4=24.57%, 10=73.71%, 20=1.56%, 50=0.03%
  lat (msec)   : 100=0.01%
  cpu          : usr=5.74%, sys=15.74%, ctx=800135, majf=0, minf=137
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1%
     issued rwts: total=1448757,0,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=128

Run status group 0 (all jobs):
   READ: bw=94.3MiB/s (98.9MB/s), 94.3MiB/s-94.3MiB/s (98.9MB/s-98.9MB/s), io=5659MiB (5934MB), run=60006-60006msec

test2不随机读IOPS设置

[root@super /]# fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=4K -size=1G -time_based -runtime=60 -name=Fio -directory=/test2
Fio: (g=0): rw=randread, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=128
fio-3.17
Starting 1 process
Fio: Laying out IO file (1 file / 1024MiB)
Jobs: 1 (f=1): [r(1)][100.0%][r=104MiB/s][r=26.5k IOPS][eta 00m:00s] 
Fio: (groupid=0, jobs=1): err= 0: pid=1494: Mon Jan 27 23:35:30 2020
  read: IOPS=25.7k, BW=100MiB/s (105MB/s)(6023MiB/60005msec)
    slat (nsec): min=1848, max=1328.1k, avg=8603.01, stdev=21240.04
    clat (usec): min=1126, max=152365, avg=4971.28, stdev=2067.07
     lat (usec): min=1132, max=152368, avg=4980.10, stdev=2067.06
    clat percentiles (usec):
     |  1.00th=[ 2245],  5.00th=[ 2671], 10.00th=[ 2999], 20.00th=[ 3458],
     | 30.00th=[ 3884], 40.00th=[ 4293], 50.00th=[ 4752], 60.00th=[ 5145],
     | 70.00th=[ 5669], 80.00th=[ 6259], 90.00th=[ 7111], 95.00th=[ 7963],
     | 99.00th=[10290], 99.50th=[11731], 99.90th=[17957], 99.95th=[22676],
     | 99.99th=[40633]
   bw (  KiB/s): min=86856, max=111976, per=99.98%, avg=102751.36, stdev=3685.76, samples=120
   iops        : min=21714, max=27994, avg=25687.74, stdev=921.31, samples=120
  lat (msec)   : 2=0.28%, 4=32.38%, 10=66.15%, 20=1.11%, 50=0.06%
  lat (msec)   : 100=0.01%, 250=0.01%
  cpu          : usr=5.96%, sys=15.47%, ctx=789134, majf=0, minf=138
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1%
     issued rwts: total=1541761,0,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=128

Run status group 0 (all jobs):
   READ: bw=100MiB/s (105MB/s), 100MiB/s-100MiB/s (105MB/s-105MB/s), io=6023MiB (6315MB), run=60005-60005msec

test1随机写IOPS设置

[root@super /]# fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=4K -size=1G -time_based -runtime=60 -name=Fio -directory=/test1
Fio: (g=0): rw=randwrite, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=128
fio-3.17
Starting 1 process
Jobs: 1 (f=1): [w(1)][100.0%][w=75.7MiB/s][w=19.4k IOPS][eta 00m:00s]
Fio: (groupid=0, jobs=1): err= 0: pid=1498: Mon Jan 27 23:37:40 2020
  write: IOPS=18.2k, BW=71.2MiB/s (74.7MB/s)(4282MiB/60113msec); 0 zone resets
    slat (usec): min=2, max=616, avg= 7.55, stdev= 6.92
    clat (msec): min=2, max=232, avg= 7.01, stdev= 7.15
     lat (msec): min=2, max=232, avg= 7.02, stdev= 7.15
    clat percentiles (msec):
     |  1.00th=[    4],  5.00th=[    4], 10.00th=[    5], 20.00th=[    5],
     | 30.00th=[    5], 40.00th=[    6], 50.00th=[    6], 60.00th=[    7],
     | 70.00th=[    7], 80.00th=[    8], 90.00th=[   10], 95.00th=[   12],
     | 99.00th=[   36], 99.50th=[   47], 99.90th=[  116], 99.95th=[  140],
     | 99.99th=[  197]
   bw (  KiB/s): min=48336, max=85600, per=100.00%, avg=73062.90, stdev=7091.42, samples=120
   iops        : min=12084, max=21400, avg=18265.67, stdev=1772.83, samples=120
  lat (msec)   : 4=9.40%, 10=82.41%, 20=6.18%, 50=1.56%, 100=0.30%
  lat (msec)   : 250=0.14%
  cpu          : usr=5.55%, sys=14.95%, ctx=735321, majf=0, minf=10
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1%
     issued rwts: total=0,1096310,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=128

Run status group 0 (all jobs):
  WRITE: bw=71.2MiB/s (74.7MB/s), 71.2MiB/s-71.2MiB/s (74.7MB/s-74.7MB/s), io=4282MiB (4490MB), run=60113-60113msec

test2随机写IOPS设置

[root@super /]# fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=4K -size=1G -time_based -runtime=60 -name=Fio -directory=/test2
Fio: (g=0): rw=randwrite, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=128
fio-3.17
Starting 1 process
Jobs: 1 (f=1): [w(1)][100.0%][w=79.6MiB/s][w=20.4k IOPS][eta 00m:00s]
Fio: (groupid=0, jobs=1): err= 0: pid=1503: Mon Jan 27 23:39:14 2020
  write: IOPS=19.1k, BW=74.5MiB/s (78.1MB/s)(4468MiB/60007msec); 0 zone resets
    slat (nsec): min=1997, max=791752, avg=7377.43, stdev=6986.23
    clat (msec): min=2, max=281, avg= 6.71, stdev= 7.43
     lat (msec): min=2, max=281, avg= 6.71, stdev= 7.43
    clat percentiles (msec):
     |  1.00th=[    4],  5.00th=[    4], 10.00th=[    4], 20.00th=[    5],
     | 30.00th=[    5], 40.00th=[    6], 50.00th=[    6], 60.00th=[    6],
     | 70.00th=[    7], 80.00th=[    8], 90.00th=[    9], 95.00th=[   11],
     | 99.00th=[   36], 99.50th=[   47], 99.90th=[  121], 99.95th=[  157],
     | 99.99th=[  220]
   bw (  KiB/s): min=46232, max=89360, per=99.99%, avg=76228.64, stdev=7455.48, samples=120
   iops        : min=11558, max=22340, avg=19057.13, stdev=1863.88, samples=120
  lat (msec)   : 4=11.69%, 10=81.90%, 20=4.37%, 50=1.60%, 100=0.31%
  lat (msec)   : 250=0.13%, 500=0.01%
  cpu          : usr=6.16%, sys=14.79%, ctx=714669, majf=0, minf=10
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1%
     issued rwts: total=0,1143725,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=128

Run status group 0 (all jobs):
  WRITE: bw=74.5MiB/s (78.1MB/s), 74.5MiB/s-74.5MiB/s (78.1MB/s-78.1MB/s), io=4468MiB (4685MB), run=60007-60007msec

test1随机读吞吐

[root@super /]# fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=1M -size=1G -time_based -runtime=60 -name=Fio -directory=/test1
Fio: (g=0): rw=randread, bs=(R) 1024KiB-1024KiB, (W) 1024KiB-1024KiB, (T) 1024KiB-1024KiB, ioengine=libaio, iodepth=128
fio-3.17
Starting 1 process
Jobs: 1 (f=1): [r(1)][100.0%][r=1024KiB/s][r=1 IOPS][eta 00m:00s] 
Fio: (groupid=0, jobs=1): err= 0: pid=1511: Mon Jan 27 23:41:49 2020
  read: IOPS=119, BW=119MiB/s (125MB/s)(7292MiB/61170msec)
    slat (usec): min=54, max=3004, avg=163.83, stdev=196.42
    clat (msec): min=10, max=2494, avg=1072.78, stdev=189.89
     lat (msec): min=10, max=2495, avg=1072.94, stdev=189.86
    clat percentiles (msec):
     |  1.00th=[  241],  5.00th=[  902], 10.00th=[  961], 20.00th=[ 1028],
     | 30.00th=[ 1053], 40.00th=[ 1070], 50.00th=[ 1083], 60.00th=[ 1099],
     | 70.00th=[ 1116], 80.00th=[ 1133], 90.00th=[ 1200], 95.00th=[ 1250],
     | 99.00th=[ 1754], 99.50th=[ 2005], 99.90th=[ 2198], 99.95th=[ 2265],
     | 99.99th=[ 2500]
   bw (  KiB/s): min= 2048, max=247808, per=99.33%, avg=121252.40, stdev=27860.84, samples=121
   iops        : min=    2, max=  242, avg=118.36, stdev=27.22, samples=121
  lat (msec)   : 20=0.16%, 50=0.08%, 100=0.29%, 250=0.48%, 500=1.54%
  lat (msec)   : 750=0.37%, 1000=12.53%, 2000=84.01%, >=2000=0.53%
  cpu          : usr=0.08%, sys=1.19%, ctx=16345, majf=0, minf=32778
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.2%, 32=0.4%, >=64=99.1%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1%
     issued rwts: total=7292,0,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=128

Run status group 0 (all jobs):
   READ: bw=119MiB/s (125MB/s), 119MiB/s-119MiB/s (125MB/s-125MB/s), io=7292MiB (7646MB), run=61170-61170msec

test2随机读吞吐

[root@super /]# fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=1M -size=1G -time_based -runtime=60 -name=Fio -directory=/test2
Fio: (g=0): rw=randread, bs=(R) 1024KiB-1024KiB, (W) 1024KiB-1024KiB, (T) 1024KiB-1024KiB, ioengine=libaio, iodepth=128
fio-3.17
Starting 1 process
Jobs: 1 (f=1): [r(1)][100.0%][r=11.0MiB/s][r=11 IOPS][eta 00m:00s]
Fio: (groupid=0, jobs=1): err= 0: pid=1514: Mon Jan 27 23:43:58 2020
  read: IOPS=119, BW=119MiB/s (125MB/s)(7304MiB/61174msec)
    slat (usec): min=52, max=5598, avg=183.95, stdev=270.59
    clat (msec): min=146, max=2256, avg=1071.05, stdev=171.09
     lat (msec): min=146, max=2257, avg=1071.23, stdev=171.04
    clat percentiles (msec):
     |  1.00th=[  317],  5.00th=[  902], 10.00th=[  961], 20.00th=[ 1020],
     | 30.00th=[ 1053], 40.00th=[ 1070], 50.00th=[ 1083], 60.00th=[ 1099],
     | 70.00th=[ 1116], 80.00th=[ 1133], 90.00th=[ 1200], 95.00th=[ 1234],
     | 99.00th=[ 1636], 99.50th=[ 1989], 99.90th=[ 2140], 99.95th=[ 2265],
     | 99.99th=[ 2265]
   bw (  KiB/s): min= 2048, max=288768, per=99.35%, avg=121466.95, stdev=25110.94, samples=121
   iops        : min=    2, max=  282, avg=118.60, stdev=24.52, samples=121
  lat (msec)   : 250=0.21%, 500=2.01%, 750=0.77%, 1000=13.81%, 2000=82.79%
  lat (msec)   : >=2000=0.41%
  cpu          : usr=0.09%, sys=1.19%, ctx=16454, majf=0, minf=32778
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.2%, 32=0.4%, >=64=99.1%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1%
     issued rwts: total=7304,0,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=128

Run status group 0 (all jobs):
   READ: bw=119MiB/s (125MB/s), 119MiB/s-119MiB/s (125MB/s-125MB/s), io=7304MiB (7659MB), run=61174-61174msec

test1随机写吞吐

[root@super /]# fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=1M -size=1G -time_based -runtime=60 -name=Fio -directory=/test1
Fio: (g=0): rw=randwrite, bs=(R) 1024KiB-1024KiB, (W) 1024KiB-1024KiB, (T) 1024KiB-1024KiB, ioengine=libaio, iodepth=128
fio-3.17
Starting 1 process
Jobs: 1 (f=1): [w(1)][100.0%][w=28.0MiB/s][w=28 IOPS][eta 00m:00s]
Fio: (groupid=0, jobs=1): err= 0: pid=1522: Mon Jan 27 23:48:33 2020
  write: IOPS=127, BW=127MiB/s (134MB/s)(7771MiB/61014msec); 0 zone resets
    slat (usec): min=104, max=941, avg=172.70, stdev=37.40
    clat (msec): min=55, max=2021, avg=1004.46, stdev=156.46
     lat (msec): min=55, max=2021, avg=1004.64, stdev=156.46
    clat percentiles (msec):
     |  1.00th=[  150],  5.00th=[  986], 10.00th=[ 1011], 20.00th=[ 1020],
     | 30.00th=[ 1020], 40.00th=[ 1020], 50.00th=[ 1020], 60.00th=[ 1020],
     | 70.00th=[ 1020], 80.00th=[ 1028], 90.00th=[ 1028], 95.00th=[ 1045],
     | 99.00th=[ 1401], 99.50th=[ 1720], 99.90th=[ 1972], 99.95th=[ 2005],
     | 99.99th=[ 2022]
   bw (  KiB/s): min= 2048, max=370688, per=99.19%, avg=129364.72, stdev=25090.44, samples=121
   iops        : min=    2, max=  362, avg=126.29, stdev=24.51, samples=121
  lat (msec)   : 100=0.23%, 250=1.90%, 500=0.48%, 750=0.50%, 1000=3.53%
  lat (msec)   : 2000=93.31%, >=2000=0.05%
  cpu          : usr=1.07%, sys=1.22%, ctx=8135, majf=0, minf=9
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.2%, 32=0.4%, >=64=99.2%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1%
     issued rwts: total=0,7771,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=128

Run status group 0 (all jobs):
  WRITE: bw=127MiB/s (134MB/s), 127MiB/s-127MiB/s (134MB/s-134MB/s), io=7771MiB (8148MB), run=61014-61014msec

test2随机写吞吐

[root@super /]# fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=1M -size=1G -time_based -runtime=60 -name=Fio -directory=/test2
Fio: (g=0): rw=randwrite, bs=(R) 1024KiB-1024KiB, (W) 1024KiB-1024KiB, (T) 1024KiB-1024KiB, ioengine=libaio, iodepth=128
fio-3.17
Starting 1 process
Jobs: 1 (f=1): [w(1)][100.0%][w=28.0MiB/s][w=28 IOPS][eta 00m:00s]
Fio: (groupid=0, jobs=1): err= 0: pid=1533: Mon Jan 27 23:51:47 2020
  write: IOPS=127, BW=127MiB/s (134MB/s)(7772MiB/61020msec); 0 zone resets
    slat (usec): min=101, max=1754, avg=173.58, stdev=42.61
    clat (msec): min=52, max=2019, avg=1004.43, stdev=161.16
     lat (msec): min=52, max=2019, avg=1004.60, stdev=161.16
    clat percentiles (msec):
     |  1.00th=[  133],  5.00th=[  894], 10.00th=[ 1003], 20.00th=[ 1011],
     | 30.00th=[ 1020], 40.00th=[ 1020], 50.00th=[ 1020], 60.00th=[ 1020],
     | 70.00th=[ 1020], 80.00th=[ 1028], 90.00th=[ 1028], 95.00th=[ 1070],
     | 99.00th=[ 1401], 99.50th=[ 1720], 99.90th=[ 1972], 99.95th=[ 2005],
     | 99.99th=[ 2022]
   bw (  KiB/s): min= 2048, max=371992, per=99.20%, avg=129375.29, stdev=26928.24, samples=121
   iops        : min=    2, max=  363, avg=126.30, stdev=26.28, samples=121
  lat (msec)   : 100=0.39%, 250=1.71%, 500=0.49%, 750=0.46%, 1000=5.96%
  lat (msec)   : 2000=90.97%, >=2000=0.03%
  cpu          : usr=1.31%, sys=0.98%, ctx=8027, majf=0, minf=10
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.2%, 32=0.4%, >=64=99.2%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1%
     issued rwts: total=0,7772,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=128

Run status group 0 (all jobs):
  WRITE: bw=127MiB/s (134MB/s), 127MiB/s-127MiB/s (134MB/s-134MB/s), io=7772MiB (8150MB), run=61020-61020msec

可以看出还是非加密好一点😁😁😁

关于Mariadb和Mysql高版本的本地登录无需密码问题及说明

2020-01-08T11:57:00.000Z

MariaDB [mysql]> show grants for 'root'@'localhost';

输入命令

GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost' IDENTIFIED VIA mysql_native_password USING '*那一坨东西' WITH GRANT OPTION;

查询正在使用的端口

2020-01-01T11:40:00.000Z

netstat -tunlp | grep 端口号

-t (tcp) 仅显示tcp相关选项
-u (udp)仅显示udp相关选项
-n 拒绝显示别名，能显示数字的全部转化为数字
-l 仅列出在Listen(监听)的服务状态
-p 显示建立相关链接的程序名

一键传附件脚本

2019-12-30T12:17:00.000Z

额，学校搞了个一体机，嗯，所以。。。
懒见我的Github：https://github.com/arkylin/Mail-Files-Tools

Newest_lamp项目

2019-12-26T12:11:00.000Z

Newest_lamp

我的Github：https://github.com/arkylin/Newest_lamp
我的Docker Hub：https://hub.docker.com/r/arkylin/newest_lamp

docker pull arkylin/newest_lamp:v0.1.6

此项目旨在创建一个通用的lamp安装脚本，来使那些“特别想用新版本，但又不会自己编译安装或者不想自己花时间去弄”的人得到方便

后续可能也可能会推出一些其他环境来弄或者一些有意思的软件

安装脚本

一、添加目录

mkdir -p /data/{ssl,vhost/apache,mysql,wwwroot,wwwroot/default,wwwlogs}

mkdir -p /data/{ssl,vhost/apache,wwwroot,wwwroot/default,wwwlogs}

二、运行

docker run -itd --name super --hostname super.xyz.blue --net host --restart always --privileged -v /data:/data -v /data/mysql:/var/lib/mysql arkylin/newest_lamp:latest /usr/sbin/init

docker run -itd --name super --hostname super.xyz.blue --net host --restart always --privileged -v /data:/data arkylin/newest_lamp:latest /usr/sbin/init

三、初始化Mysql

mysql_secure_installation

注：-V 冒号”:“前面的目录是宿主机目录，后面的目录是容器内目录。

Apache配置命令

cp -f /app/apache/conf/vhost/0.conf /data/vhost/apache

mkdir /data/vhost/apache

domain=super.xyz.blue

Apache_fcgi=$(echo -e "<Files ~ (\\.user.ini|\\.htaccess|\\.git|\\.svn|\\.project|LICENSE|README.md)\$>\n    Order allow,deny\n    Deny from all\n  </Files>\n  <FilesMatch \\.php\$>\n    SetHandler \"proxy:unix:/dev/shm/php-cgi.sock|fcgi://localhost\"\n  </FilesMatch>")

Apache_log="CustomLog \"/data/wwwlogs/${domain}_apache.log\" common"

cat > /data/vhost/apache/${domain}.conf << EOF
<VirtualHost *:88>
  ServerAdmin admin@xyz.blue
  DocumentRoot /data/wwwroot/${domain}
  ServerName ${domain}
  # ServerAlias xyz.blue
  SSLEngine on
  SSLCertificateFile /data/ssl/my.crt
  SSLCertificateKeyFile /data/ssl/my.key
  ErrorLog /data/wwwlogs/${domain}_error_apache.log
  ${Apache_log}
  ${Apache_fcgi}
<Directory /data/wwwroot/${domain}>
  SetOutputFilter DEFLATE
  Options FollowSymLinks ExecCGI
  Require all granted
  AllowOverride All
  Order allow,deny
  Allow from all
  DirectoryIndex index.html index.php
</Directory>
</VirtualHost>
EOF

使Apache生效

apachectl -t

apachectl -k graceful

USELESS

cat >> /root/.bashrc <<EOF
systemctl restart php-fpm
systemctl restart httpd
systemctl restart mariadb
EOF

博客配置

<VirtualHost *:88>
  ServerAdmin admin@xyz.blue
  DocumentRoot /data/wwwroot/www.ioioi.cn
  ServerName www.ioioi.cn
  ServerAlias xyz.blue
  #SSLEngine on
  #SSLCertificateFile /data/ssl/my.crt
  #SSLCertificateKeyFile /data/ssl/my.key
  ErrorLog /data/wwwlogs/www.ioioi.cn_error_apache.log
  
  <Files ~ (\.user.ini|\.htaccess|\.git|\.svn|\.project|LICENSE|README.md)$>
    Order allow,deny
    Deny from all
  </Files>
  <FilesMatch \.php$>
    SetHandler "proxy:unix:/dev/shm/php-cgi.sock|fcgi://localhost"
  </FilesMatch>
<Directory /data/wwwroot/www.ioioi.cn>
  SetOutputFilter DEFLATE
  Options FollowSymLinks ExecCGI
  Require all granted
  AllowOverride All
  Order allow,deny
  Allow from all
  DirectoryIndex index.html index.php
</Directory>
</VirtualHost>

前端用Caddy

/app/caddy/c* start --config /app/caddy/C

{
http_port 80
https_port 443
experimental_http3
}
xyz.blue www.ioioi.cn {
tls /data/ssl/my.crt /data/ssl/my.key
header Strict-Transport-Security "max-age=15552000; includeSubDomains; preload"
reverse_proxy 127.0.0.1:88
}

分享一个Nextcloud/Owncloud的Caddy 2前端配置文件

aaa.com {
tls /data/ssl/my.crt /data/ssl/my.key
header Strict-Transport-Security "max-age=15552000; includeSubDomains; preload"
reverse_proxy / 127.0.0.1:88 {
header_up Host {http.request.host}
header_up X-Real-IP {http.request.remote.host}
header_up X-Forwarded-For {http.request.remote.host}
header_up X-Forwarded-Port {http.request.port}
header_up X-Forwarded-Proto {http.request.scheme}
}
redir /.well-known/carddav /remote.php/carddav 301
redir /.well-known/caldav /remote.php/caldav 301
}

请关注我的博客 https://www.ioioi.cn

Whcms开启SSL提示重定向次数过多[ERR_TOO_MANY_REDIRECTS]

2019-12-07T15:22:33.000Z

问题描述：

环境：Linux+Nginx

WHMCS系统配置SSL证书，安装都正常，并且https也可以访问。然后做了301跳转，将原来的域名http转到https上，均正常。

之后到后台设置网站连接为https://xxx.com，网站直接挂掉。提示错误。

Chrome提示： ERR_TOO_MANY_REDIRECTS

IE提示错误: INET_E_REDIRECT_FAILED

问题解决：

多方排查，包括重装whmcs，均无法解决。联系官方也无法给出更多的答案。唯独可以通过https访问网站，但是无法在后台设置连接为https。这样带来的问题是https可以访问，但是用户无法注册和验证Email连接等操作。

最终解决方案为：在configuration.php的文件中，加入一条：

$_SERVER['HTTPS'] = 'On';

然后重启Nginx。在后台设置https后，问题得到解决。

阿里云开启安全组并在服务器内开启防火墙还是访问不了的解决方案

2019-10-02T07:44:02.000Z

将软件的监听地址改为0.0.0.0

Redis开启unix socket

2019-10-02T07:42:33.000Z

unixsocket /tmp/redis.sock
unixsocketperm 777

docker从容器里面拷文件到宿主机或从宿主机拷文件到docker容器里面

2019-10-02T07:39:00.000Z

1、从容器里面拷文件到宿主机？

假设容器名为testtomcat,要从容器里面拷贝的文件路为：/usr/local/tomcat/webapps/test/js/test.js, 现在要将test.js从容器里面拷到宿主机的/opt路径下面，那么命令应该怎么写呢？

docker cp testtomcat：/usr/local/tomcat/webapps/test/js/test.js /opt

2、从宿主机拷文件到容器里面

假设容器名为testtomcat,现在要将宿主机/opt/test.js文件拷贝到容器里面的/usr/local/tomcat/webapps/test/js路径下面，那么命令该怎么写呢？

docker cp /opt/test.js testtomcat：/usr/local/tomcat/webapps/test/js

解决申请 HSTS 时 Warning: Unnecessary HSTS header over HTTP 的方法

2019-10-01T17:26:00.000Z

Nginx
修改配置文件为如下所示：

map $scheme $hsts_header {
    https   "max-age=31536000; includeSubDomains; preload";
    }
server {
......(others)
  add_header Strict-Transport-Security $hsts_header;
......(others)
}

修改后重启Nginx。

Apache
修改配置文件为如下所示：

<VirtualHost *:443>
......(others)
    Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
......(others)
</VirtualHost>

修改后重启Apache。

https://websistent.com/add-the-hsts-header-only-for-https-requests-nginx/

搭建drawio

2019-10-01T17:22:00.000Z

搭建drawio
draw.io的github地址在https://github.com/jgraph/drawio，可以在release下载正式版本，我们此次下载的是源码版本。

git clone https://github.com/jgraph/drawio.git

编译的话，需要安装ant等环境。

yum install -y ant java-1.8.0-openjdk-devel

接下来，就是需要编译了。

cd etc/build && ant

如果需要生成war包的话，则如下编译

cd etc/build && ant war

编译成功后，war包会生成在drawio/build/draw.war，如果你有tomcat或java的服务环境，可以使用war包部署。整体来说，还是不用war的方便一些，只要有Apache或Nginx就可以搞定了。

安装LDAP-php扩展

2019-10-01T17:20:04.000Z

LDAP
−−with-ldap=DIR Include LDAP support
−−with-ldap-sasl=DIR LDAP: Include Cyrus SASL support
Debian/Ubuntu 需安装 libldap-2.4-2, libldap2-dev 依赖包。
Redhat/CentOS 需安装 openldap, openldap-devel 依赖包。

NextCloud上传失败或删除失败解决方法

2019-09-21T15:34:00.000Z

#!/bin/bash
php /你的网站目录/occ maintenance:mode --on

mysql -u数据库账号 -p你的数据库密码 -e "
use 数据库名称;
DELETE FROM oc_file_locks WHERE 1;
exit"

php /你的网站目录/occ maintenance:mode --off

将以上保存为.sh脚本
在你的网站目录下面新建.php文件

<?php
        passthru("bash 上面你的脚本名称.sh");
?>

那么访问这个php文件就会运行之前的那个脚本
会比每次在SSH中输入会简便很多运行程序的目录是你的网站目录，如需修改请使用绝对路径

注意：在php.ini中删除禁用函数passthru()

在NextCloud中添加应用—那个自定义链接的

Annie视频下载感觉很好

2019-09-21T15:23:00.000Z

https://github.com/iawia002/annie

运行Python-bilibili脚本视频出现的问题

2019-09-21T15:12:00.000Z

[post cid=“62” /]
Imageio: ‘ffmpeg-linux64-v3.3.1’ was not found on your computer; downloading it now.

在使用Python的moviepy模块的时候，报出以下错误：

Imageio: 'ffmpeg.linux64' was not found on your computer; downloading it now.
Error while fetching file: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:726)>.
Error while fetching file: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:726)>.
Error while fetching file: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:726)>.
Error while fetching file: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:726)>.
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/me/anaconda2/lib/python3.7/site-packages/imageio/plugins/ffmpeg.py", line 73, in download
    force_download=force_download)
  File "/home/me/anaconda2/lib/python3.7/site-packages/imageio/core/fetching.py", line 127, in get_remote_file
    _fetch_file(url, filename)
  File "/home/me/anaconda2/lib/python3.7/site-packages/imageio/core/fetching.py", line 183, in _fetch_file
    os.path.basename(file_name))
IOError: Unable to download 'ffmpeg.linux64'. Perhaps there is a no internet connection? If there is, please report this problem.

错误原因：
imageio模块下载ffmpeg的时候，无法连接网络。
下载的路径可以参看:
./site-packages/imageio/core/fetching.py:63
./site-packages/imageio/plugins/ffmpeg.py:70

wget https://github.com/imageio/imageio-binaries/raw/master/ffmpeg/ffmpeg.linux64

mv ffmpeg.linux64 ~/.imageio/ffmpeg/

使用python脚本下载bilibili视频

2019-09-21T15:09:00.000Z

Github地址：https://github.com/Henryhaohao/Bilibili_video_download
这个下载很耗服务器资源小CPU|RAM就别用了用下面这个
[post cid=“65” cover=“images/3014905791.png”/]

#下载静态文件
wget https://github.com/q3aql/aria2-static-builds/releases/download/v1.34.0/aria2-1.34.0-linux-gnu-64bit-build1.tar.bz2
#解压文件并进入文件夹
tar jxvf aria2-*.tar.bz2 && rm -rf aria2-*.tar.bz2 && cd aria2-*
#开始安装
make install

如果安装的时候提示-bash: make: command not found错误，需要先运行命令：
Debian/Ubuntu系统：apt install make -y
CentOS系统：yum install make -y

安装Python3

apt-get install python3-pip -y

Centos百度
安装ffmpeg

apt-get install ffmpeg

Centos百度

git clone https://github.com/Henryhaohao/Bilibili_video_download.git

进入安装

pip3 install -r requirements.txt

按照提示输入即可

问题
[post cid=“63” /]

apache 反向代理的时候，通过域名访问是，出现跳转到ip或者无权访问的情况

2019-09-19T13:28:00.000Z

在配置反向代理的时候加上一行：

ProxyPreserveHost On

例如：
ProxyPass / http://202.112.0.1/
ProxyPassReverse / http://202.112.0.1/
ProxyPreserveHost On #在这里加上就行

为NextCloud中的OnlyOffice配置中文访问

2019-09-18T13:24:00.000Z

感觉他那个自带的自动识别网站语言有问题
所以进行了修改
进入

修改两项内容
下面这个是指新建文档时默认进入编辑页面的中英文

下面这个是指编辑文档时默认进入编辑页面的中英文

代码跟之前的一样
[post cid=“37” /]

        if(!empty($_SERVER['HTTP_ACCEPT_LANGUAGE'])){
            $lang = substr($_SERVER['HTTP_ACCEPT_LANGUAGE'],0,4);
            if(preg_match("/zh-c/i",$lang)){
                $langConfig = "zh-CN";
            }
            elseif(preg_match("/en/i",$lang)){
                $langConfig = "en";
            }
            else{
                $langConfig = "en";
            }
        }
        else{
            $langConfig = 'en';
        }

        $lang = $langConfig;

Typecho 文章链接转外链

2019-08-30T14:36:00.000Z

用JS

<script>window.location.href = "https://www.baidu.com"</script>

其他的方法见
https://paugram.com/coding/typecho-article-links-external.html

Typecho在使用CDN的情况下获取真实IP

2019-08-30T14:19:00.000Z

当我的文章或页面被评论时，网站后台会看到他们发评论的IP地址

那么如何在使用CDN的情况下获取用户的真实IP呢？
其实很简单
在config.inc.php末尾添加即可

if(isset($_SERVER['HTTP_X_FORWARDED_FOR'])){
    $list = explode(',',$_SERVER['HTTP_X_FORWARDED_FOR']);
    $_SERVER['REMOTE_ADDR'] = $list[0];
}

效果

让你的网站文字“抖”起来

2019-08-30T13:52:00.000Z

点击以查看效果
点我！

直接在文章编辑器里面输入即可

<style>@keyframes shake-it{0%{text-shadow:0 0 rgba(0,255,255,.5),0 0 rgba(255,0,0,.5)}25%{text-shadow:-2px 0 rgba(0,255,255,.5),2px 0 rgba(255,0,0,.5)}50%{text-shadow:-5px 0 rgba(0,255,255,.5),3px 0 rgba(255,0,0,.5)}100%{text-shadow:3px 0 rgba(0,255,255,.5),5px 0 rgba(255,0,0,.5)}}</style>

<button class="btn small" id="shake-it">抖！</button>

<script>var text_obj=[document.body,document.getElementById("shake-it")];
    text_obj[1].onclick=function(){
    text_obj[0].style="animation: shake-it .5s reverse infinite cubic-bezier(0.68, -0.55, 0.27, 1.55);";
    setTimeout(function(){
        text_obj[0].style=""
        },13000)
    };
</script>

如果需要在抖的时候添加音乐

<style>@keyframes shake-it{0%{text-shadow:0 0 rgba(0,255,255,.5),0 0 rgba(255,0,0,.5)}25%{text-shadow:-2px 0 rgba(0,255,255,.5),2px 0 rgba(255,0,0,.5)}50%{text-shadow:-5px 0 rgba(0,255,255,.5),3px 0 rgba(255,0,0,.5)}100%{text-shadow:3px 0 rgba(0,255,255,.5),5px 0 rgba(255,0,0,.5)}}</style>
<style>@keyframes shake-it{0%{text-shadow:0 0 rgba(0,255,255,.5),0 0 rgba(255,0,0,.5)}25%{text-shadow:-2px 0 rgba(0,255,255,.5),2px 0 rgba(255,0,0,.5)}50%{text-shadow:-5px 0 rgba(0,255,255,.5),3px 0 rgba(255,0,0,.5)}100%{text-shadow:3px 0 rgba(0,255,255,.5),5px 0 rgba(255,0,0,.5)}}</style>

<script>var text_obj=[document.body,document.getElementById("shake-it")];

text_obj[1].onclick=function(){
    text_obj[0].style="animation: shake-it .5s reverse infinite cubic-bezier(0.68, -0.55, 0.27, 1.55);";
    setTimeout(function(){
        text_obj[0].style=""
        },13000)
    };
</script>
<script>var text_obj=[document.body,document.getElementById("shake-it")];
text_obj[1].onclick=function(){
    text_obj[0].style="animation: shake-it .5s reverse infinite cubic-bezier(0.68, -0.55, 0.27, 1.55);";
    setTimeout(function(){
        text_obj[0].style=""
        },13000)
    };
</script>

根据https://paugram.com/coding/shake-your-text.html修改

Typecho配置多语言

2019-08-21T10:00:00.000Z

[post cid=“37” cover=“images/1378905739.png”/]
更新一下，上次的那个方法太复杂。
增加en站点，就是重新搭建一个博客，数据库还是同一个不过数据库前缀可以修改
如果分开数据库的话对Sqlite不友好，Mysql随意
编辑config.inc.php
禁止直接复制，具体内容需要修改为你自己的数据库
Mysql的话对照你原来的配置修改，大体框架不变

/** 定义数据库参数 */
#$db = new Typecho_Db('Pdo_SQLite', '');
#$db->addServer(array (
#  'file' => '/home/wwwroot/www.ioioi.cn/usr/.db',
#), Typecho_Db::READ | Typecho_Db::WRITE);
#Typecho_Db::set($db);
if(!empty($_SERVER['HTTP_ACCEPT_LANGUAGE'])){
  $lang = substr($_SERVER['HTTP_ACCEPT_LANGUAGE'],0,4);
  if(preg_match("/zh-c/i",$lang)){
      $db = new Typecho_Db('Pdo_SQLite', '');
      $db->addServer(array (
      'file' => '/home/wwwroot/www.ioioi.cn/usr/.db',
      ), Typecho_Db::READ | Typecho_Db::WRITE);
      Typecho_Db::set($db);
  }
  elseif(preg_match("/en/i",$lang)){
      $db = new Typecho_Db('Pdo_SQLite', 'en_');
      $db->addServer(array (
      'file' => '/home/wwwroot/www.ioioi.cn/usr/.db',
      ), Typecho_Db::READ | Typecho_Db::WRITE);
      Typecho_Db::set($db);
  }
  else{
      $db = new Typecho_Db('Pdo_SQLite', 'en_');
      $db->addServer(array (
      'file' => '/home/wwwroot/www.ioioi.cn/usr/.db',
      ), Typecho_Db::READ | Typecho_Db::WRITE);
      Typecho_Db::set($db);
  }
}
else{
  $db = new Typecho_Db('Pdo_SQLite', 'en_');
      $db->addServer(array (
      'file' => '/home/wwwroot/www.ioioi.cn/usr/.db',
      ), Typecho_Db::READ | Typecho_Db::WRITE);
      Typecho_Db::set($db);
}

上面这个就是以你访客的浏览器的第一语言为参考来调用不同数据库来实现多语言

使用Handsome主题遇到的问题

2019-08-21T09:55:00.000Z

wrong.png

主题作者：
第一个错误不用管你要是想消除就在外观设置速度优化选择公共cdn 不要选择百度
第二个是全剧播放器暂时不要用QQ音乐换个平台试试

确定问题：使用了自定义歌单没配置内容或者使用了云解析歌单
解决方法：如果使用了自定义歌单，那么就按照说明添加，如果云解析歌单，就暂时把歌单链接删掉。或者直接关闭音乐解析

解决之后

如何使用typecho输出有颜色的字

2019-08-21T09:51:00.000Z

typecho输出html教程
只需要用!!!包裹html即可实现！
用法

!!!
<font color="red">这里是红色</font>
!!!

color颜色代码大全：

1 白颜色 #FFFFFF 2 红颜色 #FF0000 3 绿颜色 #00FF00 4 蓝颜色 #0000FF 5 牡丹红 #FF00FF 6 青颜色 #00FFFF 7 黄颜色 #FFFF00 8 黑颜色 #000000 9 海颜蓝 #70DB93 10 巧克力色 #5C3317 11 蓝紫色 #9F5F9F 12 黄铜色 #B5A642 13 亮金色 #D9D919 14 棕色 #A67D3D 15 青铜色 #8C7853 16 2号青铜色 #A67D3D 17 士官服蓝色 #5F9F9F 18 冷铜色 #D98719 19 铜色 #B87333 20 珊瑚红 #FF7F00 21 紫蓝色 #42426F 22 深棕 #5C4033 23 深绿 #2F4F2F 24 深铜绿色 #4A766E 25 深橄榄绿 #4F4F2F 26 深兰花色 #9932CD 27 深紫色 #871F78 28 深石板蓝 #6B238E 29 深铅灰色 #2F4F4F 30 深棕褐色 #97694F 32 深绿松石色 #7093DB 33 暗木色 #855E42 34 淡灰色 #545454 35 土灰玫瑰红色#856363 36 长石色 #D19275 37 火砖色 #8E2323 38 森林绿 #238E23 39 金色 #CD7F32 40 鲜黄色 #DBDB70 41 灰色 #C0C0C0 42 铜绿色 #527F76 43 青黄色 #93DB70 44 猎人绿 #215E21 45 印度红 #4E2F2F 46 土黄色 #9F9F5F 47 浅蓝色 #C0D9D9 48 浅灰色 #A8A8A8 49 浅钢蓝色 #8F8FBD 59 浅木色 #E9C2A6 60 石灰绿色 #32CD32 61 桔黄色 #E47833 62 褐红色 #8E236B 63 中海蓝色 #32CD99 64 中蓝色 #3232CD 65 中森林绿 #6B8E23 66 中鲜黄色 #EAEAAE 67 中兰花色 #9370DB 68 中海绿色 #426F42 69 中石板蓝色 #7F00FF 70 中春绿色 #7FFF00 71 中绿松石色 #70DBDB 72 中紫红色 #DB7093 73 中木色 #A68064 74 深藏青色 #2F2F4F 75 海军蓝 #23238E 76 霓虹篮 #4D4DFF 77 霓虹粉红 #FF6EC7 78 新深藏青色 #00009C 79 新棕褐色 #EBC79E 80 暗金黄色 #CFB53B 81 橙色 #FF7F00 82 橙红色 #FF2400 83 淡紫色 #DB70DB 84 浅绿色 #8FBC8F 85 粉红色 #BC8F8F 86 李子色 #EAADEA 87 石英色 #D9D9F3 88 艳蓝色 #5959AB 89 鲑鱼色 #6F4242 90 猩红色 #BC1717 91 海绿色 #238E68 92 半甜巧克力色#6B4226 93 赭色 #8E6B23 94 银色 #E6E8FA 95 天蓝 #3299CC 96 石板蓝 #007FFF 97 艳粉红色 #FF1CAE 98 春绿色 #00FF7F 99 钢蓝色 #236B8E 100 亮天蓝色 #38B0DE 101 棕褐色 #DB9370 102 紫红色 #D8BFD8 103 石板蓝色 #ADEAEA 104 浓深棕色 #5C4033 105 淡浅灰色 #CDCDCD 106 紫罗兰色 #4F2F4F 107 紫罗兰红色 #CC3299 108 麦黄色 #D8D8BF 109 黄绿色 #99CC

typecho文章界面设置多国语言-Handsome主题

2019-08-19T09:36:00.000Z

手动切换英文需要在浏览器语言中把英文挪到最前

此文章内容自动生成
主要适配handsome，其他主题稍微修改

[collapse status=“false” title=“0.0.1”]
无
[/collapse]
[collapse status=“false” title=“0.0.2”]
替换原有@为不易输入的字符&
为避免输入麻烦将原有&zh_CN&改为&CN&
[/collapse]
[collapse status=“false” title=“0.0.3”]
使首页标题，浏览器标题支持多语言
[/collapse]
[collapse status=“false” title=“0.0.4”]
更新代码

if(!empty($_SERVER['HTTP_ACCEPT_LANGUAGE'])){
                    $lang = substr($_SERVER['HTTP_ACCEPT_LANGUAGE'],0,4);
                    if(preg_match("/zh-c/i",$lang)){
                        $langConfig = "CN";
                    }
                    elseif(preg_match("/en/i",$lang)){
                        $langConfig = "US";
                    }
                    else{
                        $langConfig = "US";
                    }
                }
                else{
                    $langConfig = 'US';
                }

0.0.4修改只取前4位，这样只判断最优先的语言。如果取前5位，可能出现en,zh的情况，影响判断。
[/collapse]
[collapse status=“false” title=“0.0.5”]
使侧栏热门文章、随机文章支持多语言
前
后
方法
在/libs/Content.php中添加

随机文章同理
[/collapse]
[collapse status=“false” title=“0.0.6”]
使文章内引用文章支持多语言
方法
在/libs/Content.php中添加
更改quoteOtherPostCallback函数

[/collapse]
[collapse status=“false” title=“0.0.7”]
使归档支持多语言
方法
在/files.php中更改
大约55行的位置

效果

[/collapse]

0.0.3教程开始
在主题的functions.php末尾增加两段函数

function getLang($content, $lang){
    preg_match_all('%&'.$lang.'.*?&(.*?)&/'.$lang.'&%si',$content,$match);
    return(str_replace("&/$lang&" , "",str_replace("&$lang&" , "",str_replace("&$lang&<br>" ,"" ,$match[0][0]))));
}

以上函数可自定义修改
如$pa = '%@'.$lang.'.*?@(.*?)@/'.$lang.'@%si';中的@(.*?)@。
(.*?)匹配任意长度的任意字符非贪婪模式遇到/字符停止

function _lan($content){
    if(!empty($_SERVER['HTTP_ACCEPT_LANGUAGE'])){
        $lang = $_SERVER['HTTP_ACCEPT_LANGUAGE'];
        if(preg_match("/zh-cn/i",$lang)){ #此处见0.0.4更新
            $langConfig = "CN";
        }
        else{
            $langConfig = "US";#此处见0.0.4更新
        }
    }
    else{
        $langConfig = 'US';
    }
    print(getLang($content, $langConfig));
}

在post.php中找到

<?php echo Content::postContent($this,$this->user->hasLogin());?>

改为

<?php echo _lan(Content::postContent($this,$this->user->hasLogin()));?>

在libs目录下找到Content.php

这个是为了更改摘要显示
更改为以下

if(!empty($_SERVER['HTTP_ACCEPT_LANGUAGE'])){
    $lang = $_SERVER['HTTP_ACCEPT_LANGUAGE'];
        if(preg_match("/zh-cn/i",$lang)){#此处见0.0.4更新
            $langConfig = "CN";
            }
        else{
            $langConfig = "US";#此处见0.0.4更新
            }
    }
    else{
        $langConfig = 'US';
        }
        $content = getLang($content, $langConfig);

由于$langConfig为局部变量，所以就把程序复制了一份

标题设置多国语言
在主题functions.php中添加两段函数

function getLanPi($content, $lang){
    preg_match_all($lang,$content,$match);
    if($lang == "CN"){
        preg_match_all ('/`.*`/', $content,$match);
        return(str_replace("`" , "",$match[0][0]));
    }
    else{
        preg_match_all ('/~.*~/', $content,$match);
        return(str_replace("~" , "",$match[0][0]));
    }
    
}

function _lanPi($content){
    if(!empty($_SERVER['HTTP_ACCEPT_LANGUAGE'])){
        $lang = $_SERVER['HTTP_ACCEPT_LANGUAGE'];
        if(preg_match("/zh-cn/i",$lang)){#此处见0.0.4更新
            $langConfig = "CN";
            #$langConfig = "en_US";
        }
        else{
            $langConfig = "US";#此处见0.0.4更新
        }
    }
    else{
        $langConfig = 'US';
    }
    return(getLanPi($content, $langConfig));
}

中文用`标题`,英文用标题隔开
然后
在/var/Widget/Archive.php中添加如图

以修改archiveTitle()
然后
在主题pages.php中修改文章页面标题
如图

然后
在主题libs/Content.php修改echoPostList()来修改首页标题
如图

实现方法

&CN&
你好，世界！
&/CN&
&US&
Hello,World!
&/US&

标题
\`中文\`
~英文~

后台界面，（如果看不下去，以后可能会修改）。

然后问题就是针对AMP/MIP的插件还需要修改
Handsome阅读模式出现全部内容显示，还需修改
~~Handsome引用文章页面出现全部内容显示，还需修改~~ 已解决见0.0.6
以后会配置typecho后台文章界面显示单语言
~~侧栏热门文章出现全标题，还需修改~~ 已解决见0.0.5
以后会添加其他功能如可以手动切换语言等
~~文章归档页面出现全标题，还需修改~~ 已解决见0.0.7

nftables一些常用配置文件

2019-08-18T09:27:00.000Z

[post cid=“23” cover=“images/3488367350.png”/]

table inet filter {
    chain input {
        type filter hook input priority 0; policy drop;

        # established/related connections
        ct state established,related accept

        # invalid connections
        ct state invalid drop
        
        # loopback interface
        iif lo accept

        # ICMP & IGMP
        ip6 nexthdr icmpv6 icmpv6 type { destination-unreachable, packet-too-big, time-exceeded, parameter-problem, mld-listener-query, mld-listener-report, mld-listener-reduction, nd-router-solicit, nd-router-advert, nd-neighbor-solicit, nd-neighbor-advert, ind-neighbor-solicit, ind-neighbor-advert, mld2-listener-report } accept
        ip protocol icmp icmp type { destination-unreachable, router-solicitation, router-advertisement, time-exceeded, parameter-problem } accept
        ip protocol igmp accept

        # SSH (port 22)
        tcp dport ssh accept

        # HTTP (ports 80 & 443)
        tcp dport { http, https } accept
    }

    chain forward {
        type filter hook forward priority 0; policy drop;
    }

    chain output {
        type filter hook output priority 0; policy accept;
    }

}

ssh限流

table inet filter {
    chain input {
        type filter hook input priority 0; policy drop;

        ct state invalid drop

        iif lo accept

        # no ping floods:
        ip protocol icmp icmp type echo-request limit rate over 10/second burst 4 packets  drop
        ip6 nexthdr icmpv6 icmpv6 type echo-request limit rate over 10/second burst 4 packets drop

        ct state established,related accept

        # ICMP & IGMP
        ip6 nexthdr icmpv6 icmpv6 type { destination-unreachable, packet-too-big, time-exceeded, parameter-problem, mld-listener-query, mld-listener-report, mld-listener-reduction, nd-router-solicit, nd-router-advert, nd-neighbor-solicit, nd-neighbor-advert, ind-neighbor-solicit, ind-neighbor-advert, mld2-listener-report } accept
        ip protocol icmp icmp type { destination-unreachable, router-solicitation, router-advertisement, time-exceeded, parameter-problem } accept
        ip protocol igmp accept

        # avoid brute force on ssh限流15次/分钟:
        tcp dport ssh ct state new limit rate 15/minute accept

    }

    chain forward {
        type filter hook forward priority 0; policy drop;
    }

    chain output {
        type filter hook output priority 0; policy accept;
    }

}

要分TCP、UDP的话使用tcp、udp参数即可
详情可见：https://wiki.debian.org/nftables

如何使用firewall、ufw、iptables的替代品nftables

2019-08-18T09:25:00.000Z

更改默认设置

# update-alternatives --set iptables /usr/sbin/iptables-nft
# update-alternatives --set ip6tables /usr/sbin/ip6tables-nft
# update-alternatives --set arptables /usr/sbin/arptables-nft
# update-alternatives --set ebtables /usr/sbin/ebtables-nft

清空当前规则集：

# nft flush ruleset

添加一个表：

# nft add table inet filter

添加input、forward和output三个基本链。input和forward的默认策略是drop。output的默认策略是accept。

# nft add chain inet filter input { type filter hook input priority 0 \; policy drop \; }
# nft add chain inet filter forward { type filter hook forward priority 0 \; policy drop \; }
# nft add chain inet filter output { type filter hook output priority 0 \; policy accept \; }

添加两个与TCP和UDP关联的常规链：

# nft add chain inet filter TCP
# nft add chain inet filter UDP

related和established的流量会accept：

# nft add rule inet filter input ct state related,established accept

loopback接口的流量会accept：

# nft add rule inet filter input iif lo accept

无效的流量会drop：

# nft add rule inet filter input ct state invalid drop

新的echo请求（ping）会accept：

# nft add rule inet filter input ip protocol icmp icmp type echo-request ct state new accept

新的UDP流量跳转到UDP链：

# nft add rule inet filter input ip protocol udp ct state new jump UDP

新的TCP流量跳转到TCP链：

# nft add rule inet filter input ip protocol tcp tcp flags \& \(fin\|syn\|rst\|ack\) == syn ct state new jump TCP

未由其他规则处理的所有通信会reject：

# nft add rule inet filter input ip protocol udp reject
# nft add rule inet filter input ip protocol tcp reject with tcp reset
# nft add rule inet filter input counter reject with icmp type prot-unreachable

此时，应决定对传入连接打开哪些端口，这些由TCP和UDP链处理。例如，要打开web服务器的连接端口，添加：

# nft add rule inet filter TCP tcp dport 80 accept

要打开web服务器HTTPS连接端口443：

# nft add rule inet filter TCP tcp dport 443 accept

允许SSH连接端口22：

# nft add rule inet filter TCP tcp dport 22 accept

允许传入DNS请求：

# nft add rule inet filter TCP tcp dport 53 accept
# nft add rule inet filter UDP udp dport 53 accept

确保更改是永久的（写入到文件）。

# nft list ruleset > /etc/nftables.conf

参考：https://wiki.archlinux.org/index.php/Nftables_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)

Linux网络重装Centos，Fedora

2019-08-17T09:23:00.000Z

wget -O /boot/initrd.img http://mirror.centos.org/centos/7/os/x86_64/images/pxeboot/initrd.img
wget -O /boot/vmlinuz http://mirror.centos.org/centos/7/os/x86_64/images/pxeboot/vmlinuz
cp /boot/initrd.img /
cp /boot/vmlinuz /

nano /etc/grub.d/40_custom

menuentry "InstallCentOS7" {
    set root='(hd0,msdos1)'
    linux /vmlinuz repo=http://mirror.centos.org/centos/7/os/x86_64/ ip=45.129.2.183 netmask=255.255.254.0 gateway=45.129.2.1 nameserver=1.1.1.1
    initrd /initrd.img
}

ip可以直接写ip=dhcp也可以，如果是用dncp的话

grub2-mkconfig --output=/boot/grub2/grub.cfg
grub2-set-default InstallCentOS7

或

grub-mkconfig --output=/boot/grub/grub.cfg
grub-set-default InstallCentOS7

Fedora同理

wget -O /boot/initrd.img https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/images/pxeboot/initrd.img
wget -O /boot/vmlinuz https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/images/pxeboot/vmlinuz
cp /boot/initrd.img /
cp /boot/vmlinuz /

nano /etc/grub.d/40_custom

menuentry "InstallFedora30" {
    set root='(hd0,msdos1)'
    linux /vmlinuz repo=https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/ ip=dhcp
    initrd /initrd.img
}

注：这是rawhide版，也就相当于测试版，如需正式版，自己找

grub2-mkconfig --output=/boot/grub2/grub.cfg
grub2-set-default InstallFedora30

如果系统是grub的话

grub-mkconfig --output=/boot/grub/grub.cfg
grub-set-default InstallCentOS7

即可

在开启selinux的情况下更换ssh端口

2019-08-13T09:22:00.000Z

semanage port -a -t ssh_port_t -p tcp 22122

Fedora中设置开机脚本，并配置he-ipv6

2019-08-13T09:22:00.000Z

sudo touch /etc/rc.d/rc.local
sudo nano /etc/rc.d/rc.local

#!/bin/bash
sh /mycmd/getipv6.sh

chmod +x /etc/rc.d/rc.local
sudo nano /usr/lib/systemd/system/rc-local.service

[Install]
WantedBy=multi-user.target
sudo systemctl enable rc-local.service

使用docker搭建邮件服务器

2019-08-10T09:21:00.000Z

使用Poste.io搭建

docker run -d \
    --net=host \
    -v /etc/localtime:/etc/localtime:ro \
    -v /poste/data:/data \
    --name "mailserver" \
    --privileged=true \
    --restart=always \
    -h "mail.xyz.blue" \
    -t analogic/poste.io

具体见官网：https://poste.io

小内存服务器设置swap虚拟内存，及优化参数

2019-08-08T09:18:00.000Z

避免应用程序内存不足错误的最简单方法之一是为服务器添加一些Swap空间。Swap分区在系统的物理内存不够用的时候，把物理内存中的一部分空间释放出来，以供当前运行的程序使用。那些被释放的空间可能来自一些很长时间没有什么操作的程序，这些被释放的空间被临时保存到Swap分区中，等到那些程序要运行时，再从Swap分区中恢复保存的数据到内存中。

注意：虽然我们建议对使用传统机械硬盘驱动器的系统进行交换，但对于SSD来说，使用Swap可能会导致硬件随着时间的推移而出现问题。出于这种考虑，我们不建议在任何其他使用SSD存储上启用Swap。这样做会影响底层硬件的可靠性。本教程更建议采用传统机械硬盘的用户使用。

速通版

sudo fallocate -l 1G /swapfile
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile
echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab

第一步、检查系统的交换信息
我们可以先来检查一下系统是否已经有可用的Swap空间。我们可以有多个Swap文件或Swap分区，但通常来讲一个便足够了。

我们可以通过输入以下内容来查看系统是否已配置Swap：

sudo swapon --show

如果您没有收到任何输出，这意味着您的系统当前没有可用的Swap空间。

您可以使用free命令证有没有活动的swap：

free -h
total        used        free      shared  buff/cache   available
Mem:           985M         84M        222M        680K        678M        721M
Swap:            0B          0B          0B

正如您在输出的Swap行中所看到的，系统上没有正在活动的swap。

第二步、检查硬盘驱动器分区上的可用空间
在我们创建swap文件之前，我们将检查当前的磁盘使用情况，以确保我们有足够的空间。通过输入：

df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            481M     0  481M   0% /dev
tmpfs            99M  656K   98M   1% /run
/dev/vda1        25G  1.4G   23G   6% /
tmpfs           493M     0  493M   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           493M     0  493M   0% /sys/fs/cgroup
/dev/vda15      105M  3.4M  102M   4% /boot/efi
tmpfs            99M     0   99M   0% /run/user/1000

Mounted on列中的/dev/vda1是我们的磁盘。在这个例子中我们有足够的空间（仅有1.4G被使用）。

对swap空间的适当大小实际上取决于您的个人偏好和您的应用程序要求。通常，等于或双倍于系统内存的量是一个很好的选择。如果您只是将其用作RAM后备，那么你的swap分区尽可能不要超过4G。

第三步、创建Swap分区文件
我们可以在文件系统上创建一个swap分区。我们将在根/目录中分配我们想要调用的swap大小的文件swapfile。

创建交换文件的最佳方法是使用fallocate。此命令将创建指定大小的文件。

由于我们示例中的服务器具有1G的RAM，因此我们将在本教程中创建1G文件：

sudo fallocate -l 1G /swapfile

我们可以通过输入以下内容来验证其是否保留了正确的空间量：

ls -lh /swapfile
-rw-r--r-- 1 root root 1.0G Apr 25 11:14 /swapfile

第四步、启用Swap分区
我们需要将swap文件转换为swap分区。首先，我们需要锁定文件的权限，以便只有具有root权限的用户才能读取内容。

通过输入以下内容使该文件只能由root访问：

sudo chmod 600 /swapfile

输入以下命令验证权限更改：

ls -lh /swapfile
-rw------- 1 root root 1.0G Apr 25 11:14 /swapfile

如您所见，只有root用户启用了读写标志。

我们现在可以通过输入以下内容将文件标记为swap空间

sudo mkswap /swapfile
Setting up swapspace version 1, size = 1024 MiB (1073737728 bytes)
no label, UUID=6e965805-2ab9-450f-aed6-577e74089dbf

标记文件后，我们可以启用swap文件：

sudo swapon /swapfile

输入以下内容验证交换是否可用：

sudo swapon --show
NAME      TYPE  SIZE USED PRIO
/swapfile file 1024M   0B   -2

我们可以用free命令再次检查：

free -h
total        used        free      shared  buff/cache   available
Mem:           985M         84M        220M        680K        680M        722M
Swap:          1.0G          0B        1.0G

我们的swap已成功设置，我们的操作系统将在必要时使用它。

第五步、永久化swap文件
我们已启用当前会话中的swap文件。但是，如果我们重新启动的话，服务器将不会自动保留swap设置。我们可以通过将交换文件添加到我们的/etc/fstab来进行更改。

为了避免出现任何问题，先备份/etc/fstab文件：

sudo cp /etc/fstab /etc/fstab.bak

输入以下内容，将swap文件信息添加到/etc/fstab文件末尾：

echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab

接下来，我们将调整我们的swap空间。

第六步、调整您的Swap设置
您可以配置一些选项，这些选项会在处理swap时对系统的性能产生影响。

调整Swappiness参数
该swappiness参数主要配置系统将数据从RAM交换到交换空间的频率。该参数的值是介于0和100之间的百分比。

当值接近于零时，除非绝对必要，否则内核不会将数据交换到磁盘。请记住，与swap文件的交互是“费时的”，因为它们比与RAM的交互花费更长的时间，并且它们可能导致性能的显着降低。

当该值接近100时，其将尝试将更多数据放入交换中以努力保留更多的RAM空间。我们可以通过输入以下内容来查看当前的swappiness值：

cat /proc/sys/vm/swappiness
60

对于服务器本身来说，您可能希望这个数值更接近于0。我们可以使用sysctl命令将swappiness设置为不同的值。

例如，要将swappiness设置为10，我们可以输入：

sudo sysctl vm.swappiness=10
vm.swappiness = 10

我们可以通过在/etc/sysctl.conf文件中添加以下行来自动设置此值：

sudo nano /etc/sysctl.conf

在底部，您可以添加：

vm.swappiness=10

完成后保存并关闭文件。

调整缓存压力设置
您可能想要修改的另一个相关值是vfs_cache_pressure。这将关系到系统选择多少缓存inode和dentry信息。

您可以通过proc命令来查看当前值：

cat /proc/sys/vm/vfs_cache_pressure
100

我的设置系统会很快地从缓存中删除inode信息。我们可以通过输入以下内容将其设置为更保守的值（如50）更快就200：

sudo sysctl vm.vfs_cache_pressure=50
vm.vfs_cache_pressure = 50

同样，这仅适用于我们当前的会话。我们可以通过将其添加到配置文件来改变它，就像我们使用swappiness设置一样：

sudo nano /etc/sysctl.conf

在底部，添加指定新值的行：

vm.vfs_cache_pressure=50

完成后保存并关闭文件。

结论
本教程将为您提供一些额外的空间来避免内存不足的异常。swap空间可以避免一些常见问题。如果遇到内存不足错误，或者发现系统无法使用所需的应用程序，您的最佳解决方案是优化应用程序配置或升级服务器。

转自：https://cloud.tencent.com/developer/article/1165387修改了部分

转义字符含义，方便记忆

2019-08-08T09:17:00.000Z

\n是newline
\t是tabulator（也就是键盘上的tab）
\v是vertical tab
\b是backspace（也就是键盘上的退格键）
\r是return （也就是键盘上的回车，只不过键盘上写的是enter，意为进入）
\f是form feed（或feed）
\a是alarm

部分电信光猫查看超级管理员密码

2019-08-02T23:09:00.000Z

打开http://192.168.1.1/cgi-bin/baseinfoSet.cgi
部分可以，其实还是通过某个”网页”来查看用户信息
如图

使用下面python脚本进行解密：

list=[120,105,112,105,103,115,113,101,104,113,109,114,53,48,54,55,54,51,51,57]
result=[]
for i in list:
    if i > 57:
        i-=4
    result.append(chr(i))
print ''.join(result)

如果没有python环境
可以在线运行
http://www.pythontip.com/coding/run
list=替换成自己设备的加密密码即可。

部分来自：https://blog.51cto.com/jzking121/1750713

在Ubuntu17.04+中使用netplan配置ipv6隧道

2019-08-01T09:09:00.000Z

我们知道在Ubuntu17.04+中使用了netplan来代替/etc/network/interfaces
那么有两种方法
一：
卸载netplan重新使用interfaces
apt-get remove netplan
然后参照/etc/network/interfaces中注释的部分的来做，由于没有Ubuntu的机器，等有了再加

二：
以较出名的he-ipv6为例
1.创建 /etc/systemd/network/he-ipv6.network

[Match]

[Network]
Tunnel=he-ipv6

2.创建 /etc/systemd/network/he-ipv6-tunnel.netdev

[Match]                                                                                                                                                                                                            

[NetDev]                                                                                                                                                                                                           
Name=he-ipv6                                        
Kind=sit                                            

[Tunnel]
Independent=true                                            
Local=192.168.0.x #Private IP if behind NAT or Public IP without NAT                                   
Remote=184.105.250.46 #Tunnel broker's IPv4 address                         
TTL=255

3.配置 /etc/netplan/01-netcfg.yaml
nano /etc/netplan/01-netcfg.yaml
使用自己喜欢的编辑器，这里使用nano

# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
  version: 2
  renderer: networkd
  ethernets:
      he-ipv6:
          dhcp4: no
          dhcp6: no
          addresses: ['2001:470:xxx:xxx::2/64']
          gateway6: 2001:470:xxx:xxx::1
      enp0s3:
      ...

顺序会有所差别，不过一定要注意格式！
那个dhcp的可要可不要
4.重启网络
systemctl restart systemd-networkd && netplan apply

部分来自：https://askubuntu.com/questions/990195/ipv6-tunnel-in-ubuntu-17-10

typecho中如何使用emoji

2019-08-01T09:07:00.000Z

数据库使用utf8mb4或者使用sqlite数据库即可。
效果：😘😁😍🤣😂😊😉😎😜

如何查看typecho中页面的cid？

2019-08-01T09:05:00.000Z

如何查看typecho中页面的cid？
如果当你把页面的链接自定义了的话，那么打开页面，如图所示就是页面的cid了，文章也一样。

你好，世界！

2019-08-01T08:15:00.000Z

你好，世界！

Arkylin的小屋

主页标签栏留白修复:min-width 与溢出收缩的冲突

现象:主页标签太长,一串空白

定位:132px 来自基础规则的 min-width

修改:给 .is-pinned 加 min-width: 0

副作用:左右留白不对称

回滚与取舍

相关文件

构建与部署的增量双双失灵:9 张图片和 1915 个文件背后的三个坑

坑 1:那 9 张图片为什么永远处理不完

坑 2:deploy-oss 的跳过条件恒为假

坑 3:混淆器是非确定性的,这才是增量失效的真凶

验证:字节级稳定 + 增量生效

经验总结

Astro 构建再提速:把侧边栏从组件改成字符串生成器,13.4s → 6.9s

现状:侧边栏是最后的成本大头

方案选择:为什么不用 AstroContainer

实现:照抄模板,然后被两个坑教做人

验证:字节级 diff

结果

经验总结

静态站点文章加密实现详解:PBKDF2 + AES-256-GCM 全流程

整体架构

为什么不用 MD5 + AES-CBC

构建期加密:LockedContent.astro

浏览器端解密:Web Crypto API

接入文章页与防泄露处理

使用方式

安全性讨论:它到底能防什么

验证:构建产物检查

经验总结

Astro 构建提速 2.3 倍:从构建日志里揪出 Intl.DateTimeFormat 的隐形开销

起因:先量化”慢”

深挖:70ms 到底花在哪

为什么一页要 70ms:侧边栏比正文还重

修复:把 formatter 提升到模块级

结果

顺带验证:build.concurrency 没用

经验总结

测试Astro加密文章

全站滚动条改版:Butterfly 风格 5px 主题色细条

问题:滚动条要么没有,要么很丑

参考:Butterfly 主题的方案

实现

1. 颜色变量

2. 全局规则

3. 删掉局部覆盖

标签栏滚轮横滚

效果

相关文件

资源管理器引导线与缩进布局:对齐、等比网格与紧凑/宽松开关

问题清单

修复思路

1. 祖先层级线:一行画 N-1 条线

2. 等比网格:级别尺寸以引导线为准

3. 紧凑 / 宽松布局开关

验证

涉及文件

侧边栏云端文件树改造记录:中文目录、分类树与 SPA 导航

需求来源

最终结构

关键实现

1. 分类按配置显示

2. 点击目录:展开树 + SPA 打开页面

3. 层级引导线

4. 目录行高统一(踩坑)

遗留

相关文件

WordPress 迁移 Hugo 全记录:Plan、工具、代码与流程

背景与数据盘点

方案设计(关键决策)

工具

核心代码

1. SQL 解析器(兼容 mysqldump 转义)

2. HTML → Markdown + 图片归集

3. front matter 生成

流程(5 阶段)

踩过的坑

最终结果

数据文件

顺带验证:`build.concurrency` 没用