You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The promise of using the unstorage layer with Nuxt/Content/Assets is to be able to plug in any of a variety of sources.
Proposal
Studying the makeSourceStorage() of src/runtime/assets/source.ts, it appears that the module currently supports either the fs or github unstorage driver or defaults to the memory driver. I propose that the Nuxt Content Assets module support custom unstorage drivers as well following along the same pattern as the Nuxt Content module.
The text was updated successfully, but these errors were encountered:
I just wrote a webdav driver for unstorage. My goal is for authors to be able to simply write content on their own desktop or online via NextCloud. This currently works with Nuxt Content module, although I needed to submit a PR for Nuxt Content to build with custom drivers (nuxt/content#2193).
I would be glad to help out . . I love the architecture of serving from plain directory of markdown (or MDC) and assets. The Content module really needs Content-Assets to be fully functional.
Background
The promise of using the unstorage layer with Nuxt/Content/Assets is to be able to plug in any of a variety of sources.
Proposal
Studying the
makeSourceStorage()
ofsrc/runtime/assets/source.ts
, it appears that the module currently supports either thefs
orgithub
unstorage driver or defaults to the memory driver. I propose that the Nuxt Content Assets module support custom unstorage drivers as well following along the same pattern as the Nuxt Content module.The text was updated successfully, but these errors were encountered: