The lack of a persistent filesystem is brought up as a drawback of the Jamstack
and it is a clear hurdle for people to conceptually overcome.
I think Redwood would benefit from helping people overcome this issue by suggesting or integrating a solution. While people can write coupled code specific to one of the storage platforms (e.g. Filestack, AWS S3) this requires quite a bit of boilerplate, requires people to think of this solution to non-persistence themselves and lacks the standardised and cleaner code of an integrated solution. Further, it makes them hard to swap and use different providers - e.g. if I want to use S3 in production but a local folder in development.
Rails offer Activestorage and there could be potential for a similar offering in Redwood.
A nodejs package that could potentially be used is flydrive:
While it doesn’t offer the image specific APIs Cloudinary, Filestack - the code for these services tends to be less generic and so potentially would be less of a candidate for a more abstracted solution. The use case I am thinking more of is storing custom log files, non-media file uploads, etc.
Any ideas on whether this is a good idea or not / whether it fits with Redwood’s value proposition?