File Browser
File Browser: a first setup, important settings, verification, and recovery considerations.
Working directory: ~/homelab/apps/tools. Follow the common setup workflow first. This is a setup note based on the linked documentation, not a copy of my live configuration or a runtime verification of this full stack.
Start here
Use one utility at a time. File Browser is a useful first example because it makes the boundary of a mounted directory visible. Follow the project's container instructions, and create a new folder containing only disposable text files. Do not mount the host root, backups, or secret directories.
Settings and data
Persist the application's database and settings according to the selected image's documented paths. Mount the test folder as the file root. Complete administrator setup through the private access path and set limited permissions for a second test user. Other tools such as speed testing or container-log viewers need separate permissions and data plans.
Check it
Upload, rename, download, and delete a test file using the limited account. Confirm it cannot reach a folder outside its allowed scope. Restart and verify settings remain. Keep a separate copy of the sample while learning deletion behavior.
When something fails
Permission denied should lead to checking the mounted directory and container UID/GID, not chmod 777. A browser file manager turns its writable mount into a remote editing surface. Keep the mount narrow and back up configuration plus any real files independently.