Uploaded menu items are saved to the filesystem which means spinning up a new server to horizontally scale the service results in the fresh service not having access to the menu images stored in /assets/media/uploads. Is this intentional? I know how I would solve this my own way, but is there a native way the community has gotten around this?
Uploaded menu items are saved to the filesystem
A CDN would be the obvious solution, but to be honest I haven’t found any reason to scale horizontally - restaurant delivery is hyper localized and the bandwidth doesn’t come close to the limits on even the smallest of instances. Based on my experience, I’d highly doubt that there’s a native way to solve the problem, just because I don’t think it’s a problem that a lot of shop owners have - love to be surprised by the community on this one though!
Thanks for your well-thought out response. I agree with your points. My main concern is the lack of persistence. This set up essentially mimics the volatile storage nature of RAM. If the instances goes down, so do all the uploaded images.
Oh, that’s actually an issue that I have had before, and I’ve definitely written up a a few bash scripts that download the assets folder and dump the db as a backup. Unfortunately I have nothing to point to as they tend to be quick one-offs.
The issue that I’ve encountered is the the upgrade process can be quite fickle, especially if you’ve got a lot of extensions to get through, and I end up bricking an instance more frequently than I’d care to admit. I don’t know of a native solution to this but I’d love to see an extension or something that downloads and restores the entire filesystem easily, since yes, you can absolutely lose a bunch of data on accident.