54
File Browser is being archived on 2026-09-01 (github.com)
submitted 3 months ago by to c/selfhosted@lemmy.world
23 comments fedilink hide all child comments

all 23 comments

sorted by: hot top controversial new old
[–] [S] 24 points 3 months ago (9 children)

There is a fork though: File Browser Quantum https://filebrowserquantum.com/

  • permalink
  • fedilink
  • source
  • hideshow 9 child comments
    •
  • [–] 8 points 3 months ago (5 children)

    I've tried to use quantum and it lost the "just works" factor that OG filebrowser has. Not sure what I'll do now

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 6 points 3 months ago (4 children)

    Really? I never tried the original but didn’t have much problems setting up quantum. I had to modify my caddy file somewhat to suite my needs, but just works now.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 3 months ago (3 children)

    Did you make any modifications for large file uploads? My main problem was that big files (As in 5GB) would fail.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 3 points 3 months ago (2 children)

    No changes to the container image, but I had to fiddle with the config file. There is an option (tokenExpirationHours) to set for how long a token is valid, default is 2 hours. I can only find this in the commented example config, setting it to sometime really high like 50 let my friend upload his audiobooks without problems.

    Create a config file and place it somewhere the container can access it. Then add the environment variable FILEBROWSER_CONFIG=/some/path/to/your/config.yaml.

    Here is a snippet from my config:

    server:
  # ...
auth:
  tokenExpirationHours: 50
  # ...
userDefaults:
  fileLoading:
    maxConcurrentUpload: 100 # The inferface only shows up to 10 so I don't know if setting this value higher does anything
    uploadChunkSizeMb: 10

    tokenExpirationHours is the key to set.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 6 points 3 months ago

    I wonder how viable it would be to do the opposite of quantum. If we remove every at risk feature and strip it down to the basics: no scripts, no multi-user, no public sharing etc...

    Project could be pretty easy to maintain indefinitely?

  • permalink
  • fedilink
  • source
  • parent
  • [–] 4 points 3 months ago

    Thanks for that. I grinned at the pitch; 'It’s a no-compromise solution that’s a a quantum leap forward. Looking at the rest of the page, it does seem to have some bases covered with features. So, naturally, I'm going to have to check it out. Bookmarked.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 8 points 3 months ago (11 children)

    I couldn't find any reason they're winding down. I wonder why? Was this planned? Battlefield Fatigue? I've used it before, had no real complaints. It fit the use case at the time.

  • permalink
  • fedilink
  • source
  • hideshow 11 child comments
    •
  • [–] 11 points 3 months ago (1 child)

    It's there on the readme: https://hacdias.com/2026/07/28/filebrowser/

    The project needs a rewrite from scratch, but the author had enough.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 8 points 3 months ago

    File Browser would need to be rewritten from the ground up, with security and a good API in mind, neither of which was on my mind when I was 15.

    Ok, fair enough. I hope someone rewrites it, though.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 7 points 3 months ago

    I remember reading earlier this year that the project was essentially "complete" and would only get security updates.

    But like he says: "people keep making PRs for new features. Features that I do really think would benefit the project."

    I really struggle with folks' sense of gratitude sometimes. Like there's so many people making cool things for us... for free... When they could be doing the same work for money.

    But yeah, sucks nobody could really keep the project up and secure. I'm not looking for a fork that will add anything to the project.

    I'll read some of the bug tickets to see what the current state is like. Figured this thing could just work indefinitely without much maintenance... its so simple?

  • permalink
  • fedilink
  • source
  • parent
  • [–] 5 points 3 months ago (5 children)

    This is 100% off topic but I just realised username is ”I R mad lad” and not ”Irma Dlad”.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 2 points 3 months ago (3 children)

    I read "I R Madlad" in the style of "I R Baboon".

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 3 points 3 months ago (2 children)

    Actually, you have discovered my origin story.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 3 months ago (1 child)

    You'll have to take my word for it, but I am pantslessly dancing in victory.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 3 months ago

    I'll....take your word for it. I'm good. For some reason, in my head, flashed a Blazing Saddles quote:

    Okay, Jim, since you are my guest and I am your host, what are your pleasures? What do you like to do?

    Oh, I don't know. Play chess...screw.

    Well let's play chess.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 1 point 3 months ago

    If you're looking for a new way to manage your long term storage now that File Browser is being archived, you might want to look at huskhoard. It is an open source data tiering archive that uses fanotify to monitor your filesystem and keep your catalog in sync without heavy manual scans. I started contributing recently and I use it for my lto archive.

  • permalink
  • fedilink
  • source
    •