221afb599b
BIG MASSIVE REFACTOR OMG
...
Ripped out literally everything to simplify the backend as much as
possible.
Some of the code was so horrifically complicated it's insaneeee
2025-09-21 21:31:44 +01:00
f8619d3ef7
fix: stuff
2025-09-21 16:48:17 +01:00
3015d7bac2
fully working refresh tokens. No more expiring :)
2025-09-21 15:43:14 +01:00
a3345afbfa
AI: checking the actual expire
2025-09-21 14:51:02 +01:00
f078ac7d0b
AI: refactoring JWT tokens to jwt token manager
2025-09-21 14:42:06 +01:00
e28d9e5d16
using access token in header!
2025-09-15 21:50:15 +01:00
29c56bee1c
protecting backend images
2025-09-14 19:09:50 +01:00
0c595f76a3
disabling my mistakes
2025-09-14 18:03:52 +01:00
176d2b0bd4
reprocessing images now works
2025-09-14 18:02:40 +01:00
115d08a245
going back to how it was
2025-09-14 17:45:30 +01:00
b4b600bd7c
Revert "refactor: creating image process to handle processing of images"
...
This reverts commit 8b6b9453a8f86d705ec2319c51f429faf687cb52.
2025-09-14 17:44:33 +01:00
8b6b9453a8
refactor: creating image process to handle processing of images
...
Decoupling this from the DB, it's a good step.
Not yet perfect however.
2025-09-14 17:42:16 +01:00
2dd9f33303
feat: allowing users to delete images from lists
2025-08-30 21:38:01 +01:00
94ee8bdb7e
fix: cascade deleting of image properties
2025-08-30 21:03:15 +01:00
00359e2e8d
feat: handling image delete
2025-08-30 20:34:57 +01:00
95330c163b
fix: only firing update status when image is not 'not-started'
2025-08-30 20:32:05 +01:00
84a0996be9
feat: checking users limits when AI scans their images
2025-08-30 20:32:05 +01:00
f7c9c97f0a
fix: allowing images without lists to survive
2025-08-30 10:49:28 +01:00
76924a0332
chore: using requesty policy instead of direct models
2025-08-30 10:46:37 +01:00
d97593d487
feat: adding limits
2025-08-30 10:45:53 +01:00
de96f12b55
chore: removing comment
2025-08-30 10:10:46 +01:00
70161da3ed
opencode: delete method for stacks
2025-08-25 15:30:34 +01:00
3a182fc49b
working notifications across backend and frontend
2025-08-25 15:22:24 +01:00
ec7bd469f9
sending notifications about new stacks
2025-08-25 15:13:29 +01:00
61d2b81e8c
better handling of empty lists
2025-08-25 14:31:11 +01:00
fe0968716d
am i finished?
2025-08-25 14:23:57 +01:00
769f3981cd
feat: adding integration tests
2025-08-25 13:42:30 +01:00
a78f766122
more refactoring into seperate handlers
2025-08-25 13:16:40 +01:00
10cea769bf
creating stacks using a user request
2025-08-20 21:38:55 +01:00
f5e65524aa
improving by extracting common userID method
2025-08-19 21:51:08 +01:00
390a216260
implementing get list items
2025-08-19 21:44:11 +01:00
3e57d10360
a good start
2025-08-19 21:27:37 +01:00
28a4b37dde
feat: showing the lists which an image is a part of
2025-07-29 15:54:51 +01:00
4de4431390
feat: getting list that an image belongs in
2025-07-29 15:48:41 +01:00
13170a33e8
fix: adding wait group so we can concurrently call these
2025-07-29 15:40:18 +01:00
5024933852
feat: making the description markdown
2025-07-29 15:40:11 +01:00
a0bf27dd16
Haystack V2: Removing entities completely
2025-07-29 14:52:33 +01:00
3d05ff708e
feat: giving agent enough information to add to list instead of creating one
2025-07-29 12:14:45 +01:00
ee109f05a0
feat: showing table on frontend for pages
2025-07-29 12:01:35 +01:00
f4d8c9f083
feat: getting schema information from images
2025-07-29 11:44:08 +01:00
a1af3feb1d
chore: removing deadcode
2025-07-29 11:37:53 +01:00
8597584cf0
feat: initial draft of generating a schema from one image
...
fix: error formatting
2025-07-29 11:37:23 +01:00
88d033314e
feat: initial attempt to create a schema
2025-07-29 09:47:59 +01:00
9cae780431
fix: column generation
2025-07-29 09:47:47 +01:00
0058cdce40
feat: showing description on image page in frontend
2025-07-24 14:23:20 +01:00
37f966e508
feat: finishing description agent infrastructure on backend
2025-07-24 14:12:41 +01:00
59bf884f5d
refactor: changing notes to be a simple image description
...
Notes would generate too often and not be very useful. This is much
better.
2025-07-24 13:59:24 +01:00
e19e6562bb
feat: getting new lists onto the frontend
2025-07-22 19:49:36 +01:00
a283bc1bcd
feat: new AI generated lists
...
I think this could be how we generate other lists
Problems:
- Knowing it's a location is good because you can do nice stuff on the
frontend.
- Same for contacts & events.
So a good alternative, is to still use this type, but perhaps change the
database such that all lists live within the new tables (lists,
image_lists). But have special tags.
This would also make it easier on the AI I think.
2025-07-22 19:40:56 +01:00
1b816e512a
fix: using tagged switch
2025-07-22 18:52:26 +01:00
