File manager
Browse, edit, upload and download a website's files in the browser, unpack and create archives, and change permissions, all as the site's own Linux user.
The file manager works inside a website's home folder, /var/www/<site name>. Every request runs on the server as the website's own Linux user, so it can reach that site's files and nothing else, and new files belong to the site.
Open it from Data & Files > File Manager and pick a website, or from the Files tab of a website.
What you can do
| Action | How |
|---|---|
| Browse | Click folders, or use the path at the top to go back up. Up to 2,000 entries are listed per folder. |
| Edit a text file | Click the file. The editor opens text files up to 10 MB; binary files can be downloaded but not edited. |
| Create | New file or New folder. |
| Upload | Upload files from your computer. A file with the same name asks before it is replaced. |
| Download | The download button on a file's row. |
| Rename, delete | The buttons on each row. |
| Extract | The extract button on a .zip, .tar.gz, .tgz or .tar file. |
| Compress | Select files and folders, then click Compress to make a .zip file. |
| Permissions | The permissions button on each row. |
Paths always stay inside the website's folder. Symbolic links are listed but never followed.
Large files
Small files go straight through the panel. Larger ones travel in pieces, so their size is not limited by a single request:
- Uploads go up in pieces of up to 8 MB. The panel keeps them until the whole file is in, checks its SHA-256, and the server's agent then fetches the file over its signed connection and saves it in the site as the site's user. The panel's own limit is set with
VAULTPANEL_FILE_UPLOAD_MAX_MB(default 2048 MB); no agent takes more than 10 GB. - Downloads of large files work the other way: the agent reads the file as the site's user and sends it to the panel, which checks it against the agent's SHA-256 before you download it. The limit is
VAULTPANEL_FILE_DOWNLOAD_MAX_MB(default 2048 MB), and copies are removed an hour after they are ready.
Saving a file from the editor is limited to 1 MB.
Extract archives
Click the extract button on an archive and choose:
| Field | Notes |
|---|---|
| Extract into folder | A path inside the site. A folder that does not exist yet is created; leave it empty for the home folder. |
| Replace files that already exist | Off by default: files that already exist in the folder are kept as they are. |
The archive is unpacked on the server as the website's user. It is unpacked only when its content fits in the free disk space (and 20 GB by default). The agent installs unzip, zip and tar when they are missing.
Compress files
Select up to 200 files and folders in one folder, then compress them. Give the archive a name ending in .zip.
Permissions
The permissions dialog shows who may read, write and run (or open, for folders) the file or folder, as a grid and as a number:
- Folders are usually
755. - Files are usually
644; scripts that run,755.
For a folder, Also change everything inside sets the folder permissions on every folder inside it and separate permissions on every file. Permissions are three digits from 0 to 7; special bits (setuid, setgid, sticky) are not available.
Permissions to use it
| Permission | Allows |
|---|---|
files.read | Browsing, opening and downloading files. |
files.write | Creating, editing, uploading, renaming, deleting, extracting, compressing and changing permissions. |
Hosting customers reach only their own websites' files. See Users and roles.
Related
- Git deploy: deploy a site from a repository instead of uploading its files.
- Backups: back up a website's files before large changes.
NGINX rules and .htaccess
Add custom NGINX directives to a website's server block, or turn on .htaccess files so Apache serves the site behind NGINX for rewrites and protection.
Git deploy
Deploy static and PHP websites from a Git repository into release folders, with builds, environment variables, instant rollbacks and signed push-to-deploy webhooks.