Skip to content

Develop - #72

Merged
jhosepmyr merged 11 commits into
mainfrom
develop
Jul 10, 2026
Merged

Develop#72
jhosepmyr merged 11 commits into
mainfrom
develop

Conversation

@jhosepmyr

Copy link
Copy Markdown
Contributor

Description of Change

Section modified:

Motivation:


Type of Change

  • New section or subsection
  • Update to existing content
  • New diagram or image
  • Typo or writing correction
  • Incorrect data or information fix
  • Structure reorganization (no content change)
  • Asset change (image replacement)

Checklist Before Requesting Review

  • The PR targets develop (not main)
  • The branch name follows the convention feature/* or bugfix/*
  • Commits follow the Conventional Commits convention (feat:, fix:, docs:, etc.)
  • CHANGELOG.md has been updated with the change made
  • New images are placed in the correct assets/ subfolder
  • Image links in the README render correctly
  • Spelling of added or modified content has been reviewed
  • No generated files are included (.pdf, .docx, .html)

Screenshots or Evidence (optional)


Suggested Reviewers

salimramirez and others added 11 commits July 9, 2026 23:13
feat: update video section with link to About The Team and add conclu…
README.md relies heavily on inline HTML (tables, images, line breaks) that
pandoc's Markdown reader drops or mangles when writing to docx. Rendering
full HTML first with the same engine used for the PDF, then converting
that HTML to docx, preserves tables and images that were previously lost.
The diagram described an architecture that was never built (AWS API
Gateway, a Grafana Alloy sidecar, a dedicated EC2 running Prometheus/
Loki/Tempo/Grafana). Replaced with what actually exists in
reqsai-infra: Route 53 (tamci.app), ACM certificates, a CloudFront
distribution with two origins (S3 for the SPA, the ALB for /api/* and
/ws/*) plus a CloudFront Function blocking the default *.cloudfront.net
domain, a VPC with public/private/database subnets, an ALB restricted
to CloudFront's IP range only, ECS Fargate (1 vCPU/2GB, no sidecar),
RDS Postgres+pgvector, and the supporting managed services (ECR,
Secrets Manager, CloudWatch Logs). Also corrects the mobile app's
traffic path: it now goes through CloudFront too, since the ALB's
security group no longer accepts direct traffic from anywhere else.
Sections 4.3.4 (C4 deployment diagram narrative) and 7.1.4 (deployment
configuration) described an architecture that was never built: AWS
API Gateway, a Grafana Alloy sidecar, and a dedicated EC2 instance
running Prometheus/Loki/Tempo/Grafana. Rewrites both to describe what
actually exists: Route 53 + ACM for the custom domain, CloudFront
fronting both the SPA (S3 origin) and the backend (/api/*, /ws/* on
the ALB origin) under one origin with no CORS needed, a CloudFront
Function blocking the default *.cloudfront.net domain, the ALB's
security group restricted to CloudFront's IP range only, a single
Fargate container (no sidecar) reading secrets from Secrets Manager,
and CloudWatch Logs instead of a self-hosted observability stack.

Left the Landing Page references and the historical sprint evidence
sections untouched — those are either a different product or a
record of what actually happened at the time, not something to
retroactively rewrite.
Defines branded heading styles (Title/H1-H4), a header, and a footer with
page numbering (Página X de Y), matching the PDF's A4 layout and margins.
Used as pandoc's --reference-doc when generating the Word document.
Wires the branded reference-doc into the pandoc conversion, generates a
native Word table of contents (--toc), and post-processes the docx to set
updateFields so Word refreshes the TOC and populates it automatically
when the file is opened, since pandoc does not set this by default.
…ram-aws-infra

Feature/update deployment diagram aws infra
@jhosepmyr
jhosepmyr merged commit 88db2b1 into main Jul 10, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants