14 Commits

Author SHA1 Message Date
d8095b0c67 refactor: tables for image and processing_image
This allows a single table to be used to process images, meaning if
anything happens to the system we can always return to polling the
database and process these images individually.

Because of this we also want an `image` table to contain the actual
binary data for the image, so we aren't selecting and writing it each
time, as it is potentially a bottleneck.
2025-02-26 20:01:56 +00:00
410270e217 refactor: using chi router + bug fixes 2025-02-26 18:04:30 +00:00
5bec6c9590 fix: actually saving to the correct db table 2025-02-26 15:54:27 +00:00
971f705288 fix: actually returning all the user images
fix
2025-02-24 21:19:59 +00:00
13ebd80ce9 chore: documentation 2025-02-24 21:04:25 +00:00
b99432c202 feat: saving AI information to database 2025-02-24 21:00:05 +00:00
ee0587a16b feat: method for getting images 2025-02-24 20:05:56 +00:00
64f6bde6a9 feat: methods to get image 2025-02-24 20:02:58 +00:00
f49589907a feat: instructions for docker compose 2025-02-24 20:02:54 +00:00
2115da85b5 feat: working docker image and compose file 2025-02-24 19:44:19 +00:00
43092fa4f5 feat: using parsing on response 2025-02-24 19:05:11 +00:00
46e4043994 chore: updating gitignore
fix
2025-02-24 19:01:18 +00:00
24ef31e00f feat: parsing response from open ai
bruh
2025-02-24 19:01:18 +00:00
97b1619b01 refactor: moving all files to backend 2025-02-22 23:30:59 +00:00