alvaro/normogen
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions
normogen/docs/implementation
History
goose fff1ed2e6d
Some checks failed
Lint and Build / format (pull_request) Successful in 1m44s
Details
Lint and Build / clippy (pull_request) Successful in 1m48s
Details
Lint and Build / build (pull_request) Successful in 6m40s
Details
Lint and Build / test (pull_request) Failing after 1s
Details
fix(backend): P2 config & Docker consistency 
Resolve the operational/config sprawl (#10-#14 from the review): the app read
NORMOGEN_*/MONGODB_* env vars but every env/compose file set SERVER_*/DATABASE_*,
the ports were all over the place (8080/8000/6500/6800), there were 5
inconsistent Dockerfiles (rust:1.82 vs rust:1.93, missing curl), and an 18 MB
binary was committed.

Env-var names — standardize on what the code reads:
* config/mod.rs: NORMOGEN_PORT default 8080 -> 6500 (avoid the over-common
  8000/8080).
* db/mod.rs: create_database() now reads MONGODB_DATABASE (was DATABASE_NAME).
* .env.example, defaults.env, docker-compose.yml, docker-compose.dev.yml,
  DEPLOYMENT_GUIDE.md, deployment/README.md, deploy-and-test-solaria.sh,
  deploy-local-build.sh: use NORMOGEN_HOST/NORMOGEN_PORT/MONGODB_URI/
  MONGODB_DATABASE/APP_ENVIRONMENT; drop the dead SERVER_*/DATABASE_URI/
  DATABASE_NAME names.

Ports — canonical container port 6500 everywhere:
* Both Dockerfiles EXPOSE 6500; prod compose maps 6500:6500, dev 6501:6500.
* Bulk-replaced the long tail of solaria:8000/localhost:8000/localhost:8080 in
  docs and test scripts -> 6500.

Dockerfiles — 2 canonical, rust:latest, curl + healthcheck:
* backend/Dockerfile (prod): rust:latest builder, debian runtime now installs
  curl (so the compose HEALTHCHECK actually works), EXPOSE 6500.
* backend/docker/Dockerfile.dev (dev): rust:latest both stages, EXPOSE 6500.
* Deleted 3 redundant Dockerfiles (Dockerfile.improved x2, docker/Dockerfile).
* Deleted the committed 18 MB binary backend/docker/normogen-backend.
* Deleted 2 stray fix-notes in backend/docker/.

Compose:
* docker-compose.yml: correct env names, 6500:6500, APP_ENVIRONMENT=production,
  JWT_SECRET/ENCRYPTION_KEY required via compose interpolation, dropped the
  obsolete top-level version: key.
* docker-compose.dev.yml: correct env names, 6501:6500, mongo:7 (was 6.0),
  added a working backend healthcheck.
* Deleted docker/docker-compose.improved.yml + backend/deploy-to-solaria-improved.sh
  (built around the now-deleted 'improved' Docker files).

Verified: cargo fmt --check clean, build + clippy --all-targets clean, 18 unit
tests pass; grep confirms no SERVER_*/DATABASE_* env names and no rust:1.x tags
remain outside docs/archive and docs/adr (historical).
2026-06-27 19:54:32 -03:00
..
FRONTEND_STATUS.md docs(ai): reorganize documentation and update product docs 2026-03-09 11:04:44 -03:00
MEDICATION_MANAGEMENT_IMPLEMENTATION_SUMMARY.md docs(ai): reorganize documentation and update product docs 2026-03-09 11:04:44 -03:00
MVP_PHASE_2.7_SUMMARY.md docs(ai): reorganize documentation and update product docs 2026-03-09 11:04:44 -03:00
PHASE-2-3-COMPLETION-REPORT.md docs(ai): reorganize documentation and update product docs 2026-03-09 11:04:44 -03:00
PHASE-2-4-COMPLETE.md docs(ai): reorganize documentation and update product docs 2026-03-09 11:04:44 -03:00
PHASE-2-5-COMPLETE.md docs(ai): reorganize documentation and update product docs 2026-03-09 11:04:44 -03:00
PHASE27_COMPLETION_REPORT.md docs(ai): reorganize documentation and update product docs 2026-03-09 11:04:44 -03:00
PHASE28_FINAL_STATUS.md fix(backend): P2 config & Docker consistency 2026-06-27 19:54:32 -03:00
PHASE_2.6_COMPLETION.md docs(ai): reorganize documentation and update product docs 2026-03-09 11:04:44 -03:00
README.md docs: reconcile documentation with reality (P3) 2026-06-27 16:02:16 -03:00

README.md

Implementation Documentation

Phase-by-phase implementation completion records. Each phase that's been built has a canonical completion note here; original plans and specs are in ../archive/.

By Phase

Phase 2.3 — JWT Authentication ✅

Phase 2.4 — User Management ✅

Phase 2.5 — Access Control ✅

Phase 2.6 — Security Hardening ✅

Phase 2.7 — Health Data Features ✅

Phase 2.8 — Drug Interactions ✅

Frontend 🚧

Implementation Progress

Phase Status
2.3 ✅ Implemented
2.4 ✅ Implemented
2.5 ✅ Implemented
2.6 ✅ Implemented
2.7 ✅ Implemented
2.8 ✅ Implemented (drug interactions)
P0/P1 Security + Tests ✅ Implemented
Frontend (Phase 3) 🚧 Early

Key Features Implemented

  • JWT authentication with token rotation + token_version invalidation
  • User management (profiles, settings, password change/recovery)
  • Permission-based access control + share management
  • Security hardening (audit logging, account lockout, session management)
  • Medication management (CRUD, dose logging, adherence)
  • Health statistics tracking + trends
  • Drug interaction checking (OpenFDA-based ingredient mapping)
  • Refresh-token persistence (hashed, revocable) + /refresh and /logout
  • Fail-fast production config + real client-IP audit logging

Last Updated: 2026-06-27