docs: fix drift in Local Setup - #300
Draft
jack-arturo wants to merge 1 commit into
Draft
Conversation
Verified against verygoodplugins/automem@8ff266e and verygoodplugins/mcp-automem@2816beb. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DGd3AJwGfwXzgH1ip6Jrut
Deploying automem-website with
|
| Latest commit: |
bb4204a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://8b3894fe.automem-website.pages.dev |
| Branch Preview URL: | https://docs-audit-development-local-16v0.automem-website.pages.dev |
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.
Automated docs-accuracy audit of
development/local-setup. This page was 61 days since its last review (the longest gap on the docs site), and the drift is concentrated in fabricated env vars and stale build scripts.FLASK_ENV(defaultproduction, "developmentenables debug") andLOG_LEVEL(defaultINFO) are documented config vars, with a "Enable development mode for verbose logging and auto-reload" snippet claimingFLASK_ENV=developmentgives stack-trace error pages and auto-reloadFLASK_ENV,FLASK_DEBUG, andLOG_LEVELacross.py/.yml/.toml/.sh/Makefilereturns nothing.app.run()hardcodesdebug=False, so there is no debug mode and no auto-reload to enable.debug=Falseis hardcodedprebuildisnode scripts/sync-template-versions.mjs;postbuildisnode scripts/build-openclaw-plugin-package.mjs && chmod +x dist/index.jsprebuildnow also regenerates the shared memory policy first (tsx scripts/sync-memory-policy.ts && …);postbuildhas nochmodstepscripts.prebuild/scripts.postbuildengines.nodeis^20.19.0 || ^22.13.0 || >=24— 20.0.0–20.18.x, 21.x, and 23.x all fail the checkengines86400(1d),604800(7d),2592000(30d), and0— forgetting is disabled by default, not dailymemory-servicedocker-compose.ymldefinesfalkordb,qdrant, andflask-api— there is nomemory-serviceserviceflask-apiVerified against: verygoodplugins/automem@8ff266e
Verified against: verygoodplugins/mcp-automem@2816beb
Questions
None — every fix above is a direct source contradiction.
Unverified
scripts/bootstrap_dev.shtip is pinned toed36b98e, an old SHA. I checkedgit log ed36b98e..HEAD -- scripts/bootstrap_dev.shand the file has not changed since, so the permalink still resolves to identical content. Left as-is rather than churning the link..python-version(3.12.13), the pinned dev-tool versions (pytest==8.3.4,black==24.8.0,isort==5.13.2,flake8==7.1.1,pre-commit==4.0.1),make dev→docker compose up --build,make fmt→ black + isort, theunitpytest marker, the remaining config-table defaults, and every other npm script row.Follow-ups
nltkandrichas installed via-r requirements.txt, but both live inrequirements-dev.txtonly (nltk==3.9.1,rich>=13.0.0).requests,python-dotenv, and spaCy in that same sentence are correct.0.0.0.0:8001", butapp.run(host="::", …)binds the IPv6 any-address (dual-stack) rather than0.0.0.0. Cosmetically minor, but the literal string is wrong.Both were beyond the 5-fix cap.
Generated by Claude Code