Meeting 12.04.24

[Exand0]

TODO

you need to have a clear idea of buy vs build for at least one component

• Recipe Images
• Graphendb? (Neo4j)
• DB Service vs own container with db (probably redundant question)
• The app functionality is already done
• Validate sent photos to be images of actual food (would require image recognition)
• Instead of frontend in container -> azure web apps or something similar

discarded a few approaches that didn't work at all (write down why)

• not happened yet

have made at least one decision codified in a lightweight ADR - TODO write as ADRs

• Recipe images in Bucket (user submitted images) ✔️
• Own recipe images in a different tier storage (to be decided) ✔️
• Comic/Design/Ui - static images - will stay in image ✔️

edited your Value Proposition and made it more concise - TODO

• it is already concise
• change status to active
• add team members

---

In general:

you should be building /producing something, like a container image as an artifact (while you can have many images, one is required)

• Basic Pipeline + Frontend container image are done -> need to be integrated together TODO

---

• Simple artifact versioning in the pipeline (every change on main produces artifact that can be traced back to commit) https://stackoverflow.com/questions/69343233/github-action-increment-version-on-push-to-main/69404167#69404167 TODO

• Frontend - Configuration TODO

  • Only requires backend-url (simple solution would be enough)
  • (env vars?) - difficult
  • must work during runtime
  • mounting different json config?
  • custom startup script

• Backend/DBs images TODO

• Backend - Config-Map

• Allow uploading images of new recipes? (Would be new feature with new Endpoint...)

• Our own recipe images are not backed in into the image (see ADRs)

• App design images (resources?) will stay in the image (see ADRs)