include memory logger

[anna-follestad-4ss]

What changed

Adds a memory logger for development purposes. The tool is controlled by a single variable in the .env file, "LOG_MEMORY". When set to true, the logger prints the used memory to terminal every time the user navigates to a new page.

Why

Included as a development tool, as we know that the 4insight implementation of python dashboards will have limited memory.

Definition of done

CI covers the first two. The rest are yours — tick them because you did them,
not because they were already ticked. See CONTRIBUTING.md for why each is here.

• pytest passes
• black is clean
• memory logger acts as decribed
• memory logger behaviour is logical and useful.

Anything the reviewer should look at closely

Check if you think the logging interval make sense. I tried to do a "timed" version, i.e. log memory usage every 30 sec, but I figured at navigation is more useful.

[Copilot]

Pull request overview

Adds an opt-in development memory logger (controlled by LOG_MEMORY) so developers can observe the app process’ RSS usage during navigation, helping validate memory headroom for constrained deployments.

Changes:

• Introduces src/memory_log.py to print RSS memory usage on demand.
• Adds LOG_MEMORY wiring in src/app.py to log once on URL/pathname changes.
• Documents the feature in README.md / .env.example and adds psutil to requirements-dev.txt.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/memory_log.py	New utility for printing current process RSS memory usage.
src/app.py	Adds LOG_MEMORY env toggle and calls the logger on navigation.
requirements-dev.txt	Adds psutil as a dev dependency.
README.md	Documents how to enable memory logging via .env.
.env.example	Adds LOG_MEMORY configuration and usage notes.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.