File Manager

The Files tab browses the filesystem of the app's running container. It is meant for inspecting and small fixes, not for moving data in and out.

What it is

Every operation runs a command inside the running container (ls, head, tee, touch, mkdir -p, rm -rf), as the container's user. You see the container exactly as the app sees it, mounts included.

Using the Files tab

• Open the app and go to the Files tab. The tree starts at /; Refresh re-reads the current directory. Each entry shows its size, date and Permissions (read-only).
• Click a file to display it. Binary content is not displayed.
• Edit, then Save, rewrites the file with the text of the editor.
• New File creates an empty file and New Folder a directory, in the current directory.
• Delete removes a file, or a directory with everything it contains, after a confirmation.
• For an app with several services, a selector chooses the container; the default is the main container.

API

The same operations through the API (actual responses):

$ curl -s -H "Authorization: Bearer $SH0_TOKEN" "https://panel.example.com/api/v1/apps/<app-id>/browse?path=/app"
{"data":{"entries":[{"file_type":"file","modified":"1970-01-01 00:00:00","name":"server.js","permissions":"-rw-r--r--","size":"182"}],"path":"/app"}}

$ curl -s -X PUT -H "Authorization: Bearer $SH0_TOKEN" -H "Content-Type: application/json" \
    -d '{"path":"/app/notes/todo.txt","content":"hello from sh0\n"}' \
    https://panel.example.com/api/v1/apps/<app-id>/file
{"data":{"path":"/app/notes/todo.txt","written":true}}

$ curl -s -H "Authorization: Bearer $SH0_TOKEN" "https://panel.example.com/api/v1/apps/<app-id>/file?path=/app/notes/todo.txt"
{"data":{"content":"hello from sh0\n","path":"/app/notes/todo.txt"}}

• GET /api/v1/apps/<id>/browse?path=… -- list a directory.
• GET /api/v1/apps/<id>/file?path=… reads a file; PUT on the same route, with path and content, writes it.
• POST /api/v1/apps/<id>/files/mkdir and POST …/files/new, with path -- create a directory or an empty file.
• DELETE /api/v1/apps/<id>/files?path=… -- delete. /, /bin, /etc, /usr, /lib, /lib64, /sbin, /proc, /sys, /dev and /boot themselves are refused (“Cannot delete protected system directory”).
• Paths must be absolute and must not contain ... Reading needs the viewer role on the app's project; writing, creating and deleting need the developer role.

What is not there

• No upload. There is no route to send a file from your computer; POST …/files/upload answers 404.
• No download and no archive. You cannot download a file or a directory as an archive; GET …/files/download answers 404.
• No change of permissions or owner. Permissions are displayed, not editable.

For those operations, use the server: docker cp between the host and the container, or work directly in the volume directory on the host (see Volumes and Mounts). On the server itself, sh0 ssh <app> opens a shell in the container (see Terminal Access).

Limits and cautions

• 1 MB read limit. Reading returns at most the first 1,048,576 bytes of a file, without saying it was cut. Do not edit and save a larger file from the Files tab: the saved file would keep only that first megabyte.
• The image needs the tools. Images without a shell toolbox (distroless, scratch) lack ls or tee, and the file manager cannot work in them.
• Deletion is recursive and final. There is no recycle bin.
• The container must be running. A stopped app has no container to browse.