Skip to main content
Open Files on a running instance to browse files, edit text and download data from the dashboard.

​
Choose a root

The selector determines which directory you can browse:
  • VM home: the host user’s home directory, normally /root.
  • An app volume: a named Docker volume belonging to the selected install. An app can have several volumes; choose the one containing the data you need.
Paths in the browser are relative to the selected root. A container’s internal path depends on its image and Compose configuration, so it may differ from the path shown in Files. The app volume list is loaded from running installs. This is a scoped file browser, not the whole host filesystem. Use the host terminal for paths outside these roots, including separately mounted block-storage volumes. The .ssh directory is excluded from file-browser access; manage SSH keys through the dashboard’s SSH key controls.

​
Available actions

  • Navigate directories using the tree and breadcrumbs.
  • Open and edit text files with syntax highlighting, find and undo. Use Save, Cmd-S or Ctrl-S to write changes.
  • Format JSON or YAML. Review the result before saving; YAML formatting can remove comments.
  • Download a file, or select entries and download a ZIP archive.
  • Rename or delete files and folders. Deletion is permanent, so keep a copy of data you need.
The current limits are 1 MiB for reading or editing a text file, 50 MiB for a single-file download, and 10 GiB of source data for an archive. A selected archive accepts up to 100 paths. Large transfers can also fail because of connection or request timeouts; use an appropriate file-transfer tool for larger exports.

​
Edit an app configuration file

  1. Check the app’s guide for the correct file and volume.
  2. Download a copy or create an appropriate backup before editing.
  3. Open the file, make the change and save it.
  4. Restart the app if its documentation requires it, then check its logs and behavior.
Use the app’s Variables or configuration controls for settings managed by Suji. Hand-editing generated configuration files can be overwritten by a later deployment or configuration update. Automatic reload behavior depends on the app.

​
Path restrictions

File operations validate the selected root and reject paths that escape it, including symlinks pointing outside it. A path accessible from the root terminal can therefore be unavailable in Files. These restrictions do not remove the authority of someone with root access to the VM.

​
Next

Terminal

Work with host paths or app-specific command-line tools.

Snapshots and backups

Protect data before changing it.