psychedelicious a1773197e9 feat(nodes): remove image_origin from most places ... - remove `image_origin` from most places where we interact with images - consolidate image file storage into a single `images/` dir Images have an `image_origin` attribute but it is not actually used when retrieving images, nor will it ever be. It is still used when creating images and helps to differentiate between internally generated images and uploads. It was included in eg API routes and image service methods as a holdover from the previous app implementation where images were not managed in a database. Now that we have images in a db, we can do away with this and simplify basically everything that touches images. The one potentially controversial change is to no longer separate internal and external images on disk. If we retain this separation, we have to keep `image_origin` around in a number of spots and it getting image paths on disk painful. So, I am have gotten rid of this organisation. Images are now all stored in `images`, regardless of their origin. As we improve the image management features, this change will hopefully become transparent.		2023-06-14 23:08:27 +10:00
..
images.py	feat(nodes): remove image_origin from most places	2023-06-14 23:08:27 +10:00
models.py	logger is a interchangeable service	2023-04-29 10:48:50 -04:00
sessions.py	fix(nodes): address feedback	2023-04-26 06:29:30 +10:00