Files
Last updated
/jabali-panel/files. AntD-native. The earlier filebrowser daemon was decommissioned 2026-04-19.
What you can do
- Browse: navigate inside your own home directory (
/home/<you>). Symlinks resolved, no escaping above your root. - Upload: drag-and-drop multiple files; chunked uploads with a cancel button and a live speed readout. Direct upload works even over a bare IP (no domain configured yet).
- Download: single file or selected files (zipped server-side).
- Create / rename / delete: files and directories.
- Edit text files in-browser (CodeMirror editor; syntax highlighting for common languages).
- View images, archives (list contents), PDFs.
- Set permissions: octal (
755,644, etc.) or per-bit checkboxes. - Compress / extract: tar.gz, zip, 7z — with live progress for extract, copy, and move.
- Copy / move (Paste): runs async with a real byte-progress bar on large trees instead of blocking the request.
What you can’t do
- Browse outside your home directory.
- Set ownership (
chown, handled by the agent for app installs; you can’t change UIDs). - Run arbitrary shell commands from the file manager (use SSH / SFTP for that).
- Execute uploaded scripts directly (they execute only when served by nginx → PHP-FPM; the file manager doesn’t shell out).
Admin File Manager
Admins get the same File Manager UI (layout, functions, design) as tenants, but scoped to the whole filesystem rather than one home tree. It is:
- Opt-in and deny-listed — sensitive paths are blocked, and the write allow-list is enforced on the API, not just in the UI.
- Gated behind step-up (recent-auth / MFA) re-authentication before it opens, so a stolen session alone can’t reach the whole filesystem.
Implementation note
Filesystem ops run through the agent over Unix socket. The panel-api translates UI requests into agent calls; the agent enforces “this UID can only touch its own home” for tenants (and the deny-list + write allow-list for the admin manager). No bind-mounts, no chroot helpers, no separate file-browser process.
Why the rewrite
The original filebrowser was a separate Go daemon with its own auth, session, and storage assumptions. Inside Jabali this meant:
- Two auth stacks to keep in sync.
- A second listening port (or socket) to lock down.
- Its own JSON config to diff vs. panel state.
- UI mismatch (its UI is Vue, Jabali is AntD).
The in-panel file manager eliminates all four; everything is one panel-api call away.