0fcdd73a47
feat(sse): very rough events. Not used in the client yet
...
feat(sse): very rough events. Not used in the client yet
2025-04-13 14:27:59 +01:00
a86addc8b2
feat(jwt): adding access and refresh token generation
2025-04-10 15:35:35 +01:00
f72ee73020
feat(notes): saving the notes for any images for easy text searching
2025-04-01 20:45:43 +00:00
901f214f9d
feat(contacts): events can now have organizers
2025-03-31 18:40:36 +00:00
0c78d741f0
feat(schema): basic contact tables
2025-03-31 18:10:04 +00:00
59737ca9ac
feat(schema): removing coordinates and adding start times to events
...
.
2025-03-31 16:44:42 +00:00
a576355e7c
feat: creating events and attaching locations
2025-03-26 16:16:48 +00:00
6f938a34e3
feat(tool-calling) Big refactor on how tool calling is handled
...
these commits are too big
2025-03-22 20:46:26 +00:00
44d506bc69
wip(frontend): adding more information
2025-03-21 14:36:03 +00:00
2e1809aa27
refactor(text,tags,links): to foreign key to image instead of user_image
2025-03-18 17:48:38 +00:00
6fcb1e9f26
feat(tags): creating and getting user tags
2025-03-11 21:23:41 +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
c36fb1c0d6
feat: saving AI information to database
2025-02-24 21:00:05 +00:00
050126116c
refactor: moving all files to backend
2025-02-22 23:30:59 +00:00
