Closed fbl773 closed 3 months ago
We can probably fix this as part of #23 and #3 . The issue is that we are accessing the image URI directly from the frontend, no API req is being made. To fix this I propose we keep much of the backend storage of photos as is, but handle their retrival via blobs. This way the request can still be made to the machine running behind the reverse proxy, who can send it as a blob. Even the object specs don't need to change this way. They will still have a image_path
field of sorts, it just won't be a URI, it will be a path to the photo on the machine that is hosting the API.
This ended up being an issue with our NGINX config, it has been handled.
~issue - Image access impossible on WAN
Description
We cannot access images as we are running the app now because they are stored in a folder on the machine hosting the API, because we are coordinating the network via NGINX on a different machine and the software is looking for images on the machine it is contacting (that is, the NGINX machine), it is unable to find images.
Image upload works fine, but images cannot be fetched.
See:
12