Repository navigation
chore: drop dead config and correct the docs - #33
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Category
Docs, mostly (plus some dead code out)
Overview
A few places said more than the app does.
AIUSAGE_SCAN_INTERVALwas in.env.examplebut nothing ever read it, since the interval lives in settings. The README promised a calendar of every day (it stops at a year), every session (it's the most recent 60), daily totals by project (only tool or model) and Node 22.12, when the engines field wants 22.17. And the footer said nothing is sent anywhere, while the plan windows check is on by default - it now says "Only the plan windows check leaves it." when that's on.The compose file also published 8080 on every interface, which the README warns against a few lines further down, so it's bound to localhost now.
The rest is unused bits: three config values, a Gemini CLI tool entry with no source behind it, a
daysfield nothing reads, andlstatOf, which was callingstat.Issue Number
n/a
Additional Info
Anyone who reaches the compose setup from another machine will need the old port mapping back. Checked the footer both ways in a build, and
check, tests andformat:checkpass.