Skip to content

File Manager

Browse, upload, edit, and organize site files from the browser.

Who can use this page? Site access — read/write/manage as granted. Site owners have full access on their sites.

Open

Sidebar → File Manager, or Site Actions → Open in File Manager.

Upload an application

  1. Open the site's … → Open in File Manager so you start in the correct document root, normally /var/www/example.com/public.
  2. Choose Upload for files or an archive, or Upload Folder for a directory. The current folder determines the upload destination.
  3. For an archive, wait for the upload to finish, right-click it, and choose Extract here. ZIP, TAR, TAR.GZ, and TGZ archives are supported.
  4. Check the extracted structure. An archive may add a directory such as my-app/; move its contents if the app is supposed to run directly from the document root.
  5. Confirm the entry files are in the expected place: index.html for a static site, or package.json and your source files for an uploaded Node app.
  6. For Node apps, continue with Start or Build & Restart. Uploading does not automatically start the app.

Let the server install Node dependencies; do not transfer your computer's node_modules. Configure secrets through Environment Variables.

For a Git-connected app, deploy from the repository. Files uploaded manually do not replace its active Git release.

Capabilities

ActionNotes
BrowseNavigate the site tree
UploadDrag & drop; large uploads supported (limits from panel settings)
DownloadSingle files
EditSyntax-aware for PHP, JS, CSS, JSON, YAML, shell
Rename / moveWithin permitted paths
chmodPermissions
Create folderUse Folder in the toolbar
Zip / unzipArchive helpers
Lock / unlockImmutable bit (chattr +i) on sensitive files

Lock / unlock

Right-click → lock sets the immutable bit (e.g. on wp-config.php). If locking is unavailable or fails, contact NitHost support.

UI unlocks are temporary: a sweeper re-locks files after a TTL so a forgotten unlock does not leave configs writable forever.

Good practices

  • Edit one file at a time; keep a backup before bulk changes
  • Do not chmod 777 — use the minimum write access the app needs
  • Prefer Git deployments for application code
  • After code edits, purge cache if applicable

Customer documentation · Nusite IT Consulting Limited