bzf/archivefs

Mount your archives and browse them as regular files

archivefs's Issues

Watch for new files in directory

Handle directories in archives

Handle non-RAR archives

Make it work without the -s flag

Having it being written in Rust, we should be able to use it without the single thread option.

Add proper logging with levels

Add man pages

Keep the directory structure of the archives

Right now it shows all found archives at the top level of the mounted directory rather than keeping the directory hierarchy for them.

Build new versions on every commit

CircleCI maybe?

Handle zip archives

Browse non-archives as regular files

Only replace archives with a folder and browse other files as regular files.

Before:

$ tree mounted/
mounted
├── files.rar
└── foo.txt

0 directories, 2 files

After:

$ tree mounted/
mounted
├── files
│   └── debian-9.0.0-amd64-netinst.iso
└── foo.txt

1 directory, 3 files

Could this program run in a Docker container?

It seems like a cool idea to have the full fuse and libarchive dependencies inside a Docker container which could be downloaded an manage the streaming part (and maybe it will be easier to have Docker as a dependency than install Fuse?).

• Can you mount a fuse filesystem on a mounted directory through Docker?
• Will it be fast enough?

I'm imagining running a command simliar to

$ docker run --rm -v /where/my/archives/live:/archives -v ./mountpoint:/mountpoint archivefs

which, on start, would scan for archives in /archives and mount the filesystem in /mountpoint.

All filenames and directory names are downcased

Fix permission handling

Can we port this to Rust?

Handle mounting multiple archives

Memory leak when reading from archived files

When running the app as a way of exposing files as a Samba share in Proxmox, it seems to leak memory while reading from archived data. I'm not sure if it does that for regular files as well.

I just recently moved my Samba shares to run in a Proxmox container, so it hasn't been live for that long, but the graph shows a telling story never the less.

How to test for memory leaks

Could we run valgrind in a Github Action and read some files from an archive and see if something got leaked?

Add test for verifying that the package works on Debian