FS is an abstraction, a common interface for file systems.
It allows me to provide access to an archive (zip, tar) or database or
network (S3, HTTP ...) backed file system.
Thus exporting FS as a FUSE filesystem allows all those FS implementations
to be accessed as a real file system,
eliminatin
I can see a use - exporting an embedded FS (read only) from a binary,
especially for testing stuff.
On Thursday, 29 June 2023 at 08:00:18 UTC+1 Roland Müller wrote:
> Hello,
> I am struggling to understand the purpose of extension.
> FS is an interface to access file systems from go code. Is yo
Hello,
I am struggling to understand the purpose of extension.
FS is an interface to access file systems from go code. Is your new
extension acting as a handler and allows to expose any Go FS to be mounted
and acessed at operating system level?
https://en.m.wikipedia.org/wiki/Filesystem_in_Userspa
Hi,
Does anyone know an existing solution for exporting an fs.FS as a FUSE
filesystem?
As fs.FS is standard now, this would open several new possibilities,
as a lot of interesting fs.FS implementations exist (zip, tar, DB,
embedded, union ),
and this one little glue code could export them a
