[shohag121]

White Label bandwidth and disk for each customer (flywp/flywp-internal-tasks#91, #92). Contract v0.6.0.

What changes

• Traffic of each site. The agent reads the proxy's second log, ~/.fly/nginx/vhost/flywp-traffic.log ($server_name $bytes_sent), from a saved offset. Each sample gets traffic: [{host, bytes}].
  • The first read starts at the end of the file: old traffic is not counted.
  • The offset is saved before the sample is buffered. A sample that is dropped is not counted again.
  • The file opens with O_NOFOLLOW and must be a regular file. The agent cuts the open file once it read it and it is larger than 64 MiB.
  • A new file (another inode, or other first bytes: Linux can reuse the inode of a deleted file), or a file smaller than the offset, starts again from 0.
• Own files of each site. sites[].files_bytes is the site's app folder only, from the same disk walk. The disk_bytes figure does not change.
• Old FlyWP versions ignore the new fields. A new FlyWP reads them as optional.

Tested

• make check: lint 0 issues, all tests pass, on macOS and on Linux (Go 1.27.2). golangci-lint goes to v2.15.0: v2.13.2 cannot read the export data of Go 1.27.2. New tests in internal/metrics/traffic_test.go.
• On a real server (19 Oct): the FlyWP app wrote the proxy files, and the proxy wrote the log lines in the format this reader expects. The reader itself is covered by the unit tests only.

Release

• Release as v0.3.0. The FlyWP app sets up the traffic log only on servers whose agent is v0.3.0 or newer (WHITE_LABEL_TRAFFIC_AGENT_VERSION). For another version number, set that env on FlyWP.
• Agents update themselves 24 hours after the signature. Until then, bandwidth shows "not measured" on the customer pages.

🤖 Generated with Claude Code

[nabil1440]

CI fixes

• Lint (f959d1a): setup-go now installs Go 1.27.2, and golangci-lint v2.13.2 cannot read its export data (typecheck of the standard library fails). Bumped to v2.15.0.
• Traffic reader (ae4516d): TestTrafficReadsANewOrCutFileFromTheStart failed on Linux, which can give a new file the inode of one just deleted. The reader then went on from the old offset in the middle of a line, and a line cut there can name another site (shop.example.com → example.com).
  • traffic.json now also keeps a SHA-256 of the file's first bytes (up to 256, not past the offset). If the hash no longer matches, the reader starts from 0.
  • New test TestTrafficKnowsANewFileWithTheSameInode rewrites the file in place (same inode on every OS). It fails without the fix.
  • A negative offset in a corrupt traffic.json also reads from 0.

make check passes on macOS and on Linux (Go 1.27.2).