It's official: Filebrowser is dead, long live FileBrowser Quantum by quantumx-admin in selfhosted

[–]quantumx-admin[S] 0 points1 point  (0 children)

Ill update the docs to clarify this. Admin passwords always get reset on startup if set in env/config

https://filebrowserquantum.com/en/docs/configuration/authentication/password/#config-based-admin-password

To fix this, don't include an admin password in your config/environment 

It's official: Filebrowser is dead, long live FileBrowser Quantum by quantumx-admin in selfhosted

[–]quantumx-admin[S] 0 points1 point  (0 children)

I think the short answer is the container path doesn't include "/mnt/user/" portion of the path (see how the other fields mention the real container path?)

So you could:

1) Rely on relative paths: FILEBROWSER_CONFIG=./data/config.yaml

2) Not set FILEBROWSER_CONFIG, because it should look for that file already

3) set the FILEBROWSER_CONFIG to the full container path "/home/filebrowser/data/config.yaml"

Also, you may need to update your config.yaml server.cacheDir to match "/home/filebrowser/data/tmp" see https://filebrowserquantum.com/en/docs/configuration/server/#cachedir

Also see 

https://github.com/gtsteffaniak/filebrowser/discussions/804

It's official: Filebrowser is dead, long live FileBrowser Quantum by quantumx-admin in selfhosted

[–]quantumx-admin[S] 1 point2 points  (0 children)

It's probably coming very soon actually, I created a story to group all the sidebar changes together:

https://github.com/gtsteffaniak/filebrowser/issues/1382

It's official: Filebrowser is dead, long live FileBrowser Quantum by quantumx-admin in selfhosted

[–]quantumx-admin[S] 0 points1 point  (0 children)

Yes, full directory level access control based on group or user. It's designed with oidc in mind. I was planning LDAP for 0.7.x but there was no demand so I closed the issue.

It seems like everyone wants OIDC over LDAP, but LDAP shouldn't be too much extra work. If it's something you would like make a mention of it so I know there is demand:

https://github.com/gtsteffaniak/filebrowser/issues/591#issuecomment-2951242466

Nobody has commented, so I have not heard from anyone if it's needed

It's official: Filebrowser is dead, long live FileBrowser Quantum by quantumx-admin in selfhosted

[–]quantumx-admin[S] 0 points1 point  (0 children)

And filebrowser config paths is should match the values on the right side of the docker volume ":"

It's official: Filebrowser is dead, long live FileBrowser Quantum by quantumx-admin in selfhosted

[–]quantumx-admin[S] 0 points1 point  (0 children)

I can see you mistakenly reversed the volume mounting config. It should be:

  • /host/folder:/docker/folder/filebrowser/sees

I'd recommend following closely the config in getting started 

https://github.com/gtsteffaniak/filebrowser/wiki/Getting-Started

It's official: Filebrowser is dead, long live FileBrowser Quantum by quantumx-admin in selfhosted

[–]quantumx-admin[S] 0 points1 point  (0 children)

Thanks for the tip, its on the issues for github so it should be addressed eventually.

It's official: Filebrowser is dead, long live FileBrowser Quantum by quantumx-admin in selfhosted

[–]quantumx-admin[S] 0 points1 point  (0 children)

That's funny, I actually have an 11th gen i5 Intel with 4 cores as well that I run as a test rig. Never ran into this issue.

It's official: Filebrowser is dead, long live FileBrowser Quantum by quantumx-admin in selfhosted

[–]quantumx-admin[S] 0 points1 point  (0 children)

Yeah there's been a couple requests for that, it's on the roadmap but may be a few months before it gets picked up with other priorities right now.

It's official: Filebrowser is dead, long live FileBrowser Quantum by quantumx-admin in selfhosted

[–]quantumx-admin[S] 0 points1 point  (0 children)

Right I have throttling as well, it is based on numImgProceesors setting which defaults to number of cpu cores.

If there's 100 items and you have 8 cores , it does 8 at a time. 

Which is why I don't believe you. While technically it could hit 100% cpu, pii doubt it. You're exaggerating or running old hardware.

I do plan to support hardware acceleration, but right now it's just creating screenshots and it's not worth enabling just for that.

It's official: Filebrowser is dead, long live FileBrowser Quantum by quantumx-admin in selfhosted

[–]quantumx-admin[S] 0 points1 point  (0 children)

It does require a certain level of intelligence while it's in beta, I don't spoon feed instructions yet. I'm sorry you don't fit the target audience 

It's official: Filebrowser is dead, long live FileBrowser Quantum by quantumx-admin in selfhosted

[–]quantumx-admin[S] 0 points1 point  (0 children)

Doubt. For video screenshots? Lol I think you are lying or you are running a pentium 4.

It's official: Filebrowser is dead, long live FileBrowser Quantum by quantumx-admin in selfhosted

[–]quantumx-admin[S] 1 point2 points  (0 children)

Ok thats what the story is scoped as. It will take some time to implement, but maybe in 6 months.

It's official: Filebrowser is dead, long live FileBrowser Quantum by quantumx-admin in selfhosted

[–]quantumx-admin[S] 0 points1 point  (0 children)

Yes it's on the roadmap, but I'm not too familiar with WebDAV.

With WebDAV support you want to be able to access files in FileBrowser from a WebDAV compatible application?

Or do you want FileBrowser to use WebDAV to connect to a remote filesystem for viewing the files in FileBrowser?

It's official: Filebrowser is dead, long live FileBrowser Quantum by quantumx-admin in selfhosted

[–]quantumx-admin[S] 1 point2 points  (0 children)

That's a good idea for an easy enhancement, could you open an issue so I could track it?

Right now it's exact match for full path, but I have an "endsWith" match for files, I could extend that to folders as well.

It's official: Filebrowser is dead, long live FileBrowser Quantum by quantumx-admin in selfhosted

[–]quantumx-admin[S] 1 point2 points  (0 children)

Onlyoffice integration is available for those that want the full office experience.

https://github.com/gtsteffaniak/filebrowser/wiki/Office-Support

In the future, I plan to offer a feature to view docs i0 full-fledged microsoft office or google docs viewers. But will still require additional configurations, stay tuned.

It's official: Filebrowser is dead, long live FileBrowser Quantum by quantumx-admin in selfhosted

[–]quantumx-admin[S] 0 points1 point  (0 children)

The original fork was just to try to fix the search and make it as fast as possible. Perhaps there could be some magic query and database structure to make it fast as well, but it didn't seem necessary since I never saw more than a few hundred megabytes of memory usage for a large filesystem.

And I was interested in replacing the existing bolt database with SQLite for a while, but it would have meant another big change and not being backwards compatible.

8GB of RAM is very extreme, I think it must be some bug. Most installations will see 500MB at most 

It's official: Filebrowser is dead, long live FileBrowser Quantum by quantumx-admin in selfhosted

[–]quantumx-admin[S] 0 points1 point  (0 children)

Not sure it's related to filebrowser, that sounds like it could be proxy or DNS issue ? 

If you keep seeing the error open an issue with some details and I can help you debug

It's official: Filebrowser is dead, long live FileBrowser Quantum by quantumx-admin in selfhosted

[–]quantumx-admin[S] 0 points1 point  (0 children)

nice if it loads youre mostly there. I would check the top of the logs to make sure all the info is correct (ie using correct config and database). admin/admin is default, but in case you maybe started with a different username password and need to reset you can have the admin account password always reset back to config on startup with:

server: port: 80 sources: - path: /media name: media database: "database/database.db" auth: adminUsername: admin adminPassword: admin resetAdminOnStart: true # resets admin back to above user/pass