Suggestion: Use Caddy built-in file browser as an alternative

[maple3142]

Currently, caddy's builtin file browser can be enabled by changing Caddyfile to:

@protected path / /index.html /js/* /files/*

basicauth @protected {
        ...
}

# omitted...

route /files/* {
    uri strip_prefix /files
    file_server {
        root /data
        browse
    }
}

and to get Content-Type works correct (so that images and videos can be viewed or played in browser), mime database required by go needs to be avaiable (e.g. mounting /usr/share/mime/globs2)

Of course this is missing some feature that the current file browser supports (e.g. sharing), but it is good for people who want direct HTTP based file access.

The UI looks like this

[wahyd4]

Cool, it sounds good, then we can make filebrowser optional.
Would your like to make a PR for this?

[maple3142]

Of course

I am wondering should this be in a different path than /files (maybe /fs) that it can coexist with existing file browser, and both filebrowser and caddy file_server can be enabled/disabled separately? I am not sure how to handle this with current multiple Caddyfile setup.

[wahyd4]

Yeah, I think we can use /fs for the Caddy file server one.
Regarding the multi Caddyfile setup, most of them are the same, the only difference is SecureCaddyFile will be used when user turns on authentication by enabling ENABLE_AUTH.
So most likely you can put the same contents into the 2 files.