Browse, edit, transfer, archive, and protect files.
The file manager provides controlled access to an application's release and persistent files without requiring a separate FTP service. Operations run as the application's owner and verify that paths stay inside the permitted root.
Browse directories and symlinks with size, permissions, and modification metadata. Large directories are paginated and sortable. Search by filename or file content when you know only part of a path or value.
Text files open in a syntax-aware editor. Saves include a modification precondition, so ServerChirp reports a conflict instead of overwriting a newer version written by another operator or process.
Authorized users can:
.zip or .tar.gz archives.Symlink and owner checks prevent a path from escaping the application's release or approved persistent mounts.
Bulk bytes do not travel over agent commands. The browser uploads through expiring presigned multipart requests to private object storage, and the agent receives only a transfer ID and scoped capability.
This keeps large uploads resumable and prevents the command broker from becoming a file-transfer queue.
Release-based deployments create new directories. Files that must survive a deployment belong in configured persistent paths, which are linked into each release. Editing a non-persistent file inside the current release can be lost at the next deployment.
Use the file manager for investigation and small operational changes. Keep application source changes in Git so the next release is reproducible.