10 Commits

Author SHA1 Message Date
79ee5e23ca fix: getting user images 2025-02-26 20:09:19 +00:00
1f16cfb30b 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
2a37e37c4b refactor: using chi router + bug fixes 2025-02-26 18:04:30 +00:00
b29f5b1bb5 fix: actually saving to the correct db table 2025-02-26 15:54:27 +00:00
111c6ac74f fix: actually returning all the user images
fix
2025-02-24 21:19:59 +00:00
c36fb1c0d6 feat: saving AI information to database 2025-02-24 21:00:05 +00:00
e26835861d feat: method for getting images 2025-02-24 20:05:56 +00:00
e69d7b5c08 feat: methods to get image 2025-02-24 20:02:58 +00:00
c9cd0df9ca feat: working docker image and compose file 2025-02-24 19:44:19 +00:00
050126116c refactor: moving all files to backend 2025-02-22 23:30:59 +00:00