Replying to @⁨jello@programming.dev⁩

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.

📂 Web File Browser. Contribute to gtsteffaniak/filebrowser development by creating an account on GitHub.GitHubfilebrowser/frontend/public/config.generated.yaml at main · gtsteffaniak/filebrowser📂 Web File Browser. Contribute to gtsteffaniak/filebrowser development by creating an account on GitHub.

Replying to @⁨irmadlad@lemmy.world⁩

Henrique DiasUpdate On File Browser - Henrique DiasLast year, I wrote a bit on maintaining open source projects. At the time, I was struggling with one of my most (unexpectedly) successful side projects, File Browser. Today, I want to give an update on it, since I never wrote again about it. I’m hoping that this post helps explaining the current status of the project.

Replying to @⁨irmadlad@lemmy.world⁩

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?

Replying to @⁨irmadlad@lemmy.world⁩

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

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

Henrique DiasGoodbye File Browser, for Real This Time - Henrique DiasYesterday, I published the last planned release of File Browser. It includes a few security fixes and a notice about the wind-down of the project. Alongside it, I announced that this was the last planned release and updated the repository so that it’s ready to be archived on September 1st. For many people this came as a surprise. For those who’ve been following the project from close by, probably not. Either way, I wanted to write a bit about the decision and how we got to this point.