OKAY. Some progress (and some setbacks :>)

So I’ve worked on the uploaded design, as well as the backend that was meant to write the file to the /tmp directory. The problem I needed to solve was to figure out a way to store the files on the backend that didn’t involve writing duplicates to the user’s disk.

This is a very difficult task, because I can’t get file paths from the input field in the frontend, only the filename and file content (and some other unrelated details).

Solution? Implement a different system that DOESN’T involve file uploads :D

If I just use the directory im in when the user runs the command to start the loopback GUI, I can define a “project scope” in a sense, where I only try to use images in that directory. This way, it’s up to the user to choose which folder they want to use as their project. :>

So now I need to refactor BOTH my design and backend to support this HA. Awesome