Skip to content
ForgeVPS

Browse guides

Find your way around

Learn what ForgeVPS does, what each tab is for, and how the different parts of your workspace fit together.

Connect or install ForgeVPS

Choose hosted or self-hosted, connect your machine, and open your first workspace.

Use the Dashboard

Check the machine you are working on, understand its resource readings, and find your next step.

Browse and edit files

Find your project, edit and save code, search files, and understand the Workspace and Git controls.

Use the Terminal

Run commands on your machine, keep separate tasks in tabs, and return to sessions you left open.

Use the Servers tab

Add an app, choose development or production, and use the list and detail controls to keep it running.

Deploy from GitHub

Connect a repository, follow its build, and publish later changes by pushing to the selected branch.

Give your app a web address

Point a domain at your machine, choose the app it should open, and check that HTTPS is working.

Use the Databases tab

Create a PostgreSQL database, open tables, edit rows, run a query, and connect your application.

Import a Supabase database

Copy selected application schemas into a new local database, verify the result, and switch your app deliberately.

Back up and restore a database

Use the Backups dialog to save a recovery point, download a copy, and restore when you need to.

Work with an agent

Give your agent a reliable starting point without handing over credentials or changing your project's instructions.

Technical reference

Understand the panel, managed processes, workspace files, and the boundary between ForgeVPS and your applications.

Open app ↗
Browse documentation
Docs/Browse and edit files

Browse and edit files

Find your project, edit and save code, search files, and understand the Workspace and Git controls.

Hosted & self-hostedReviewed 2026-09-29Read as Markdown ↗
On this page

Understand the Files page

Files combines a file browser with a code editor. The folder tree helps you find files on the machine; opening a file creates an editor tab. The Workspace menu controls which folders you keep close at hand.

These are the actual files on your VPS. Saving an edit changes that file on the machine. The editor is not an extra copy of the project and does not automatically publish a GitHub deployment.

Find and open your project

  1. Select the correct machine and open Files.
  2. Expand folders in the tree until you reach your project. To keep the project handy, open Workspace → Add Folder to Workspace… and choose its folder.
  3. Open the project’s README or another text file. It appears in an editor tab.
  4. Open more files as needed and use the tabs to move between them.

Adding an existing folder to Workspace makes it easier to navigate; it does not upload, clone, or move that folder. Remove from Workspace removes the shortcut. Delete is a separate action that removes the actual file or folder.

Make and save an edit

  1. Click the file you want to change and edit its contents.
  2. Use Save, or press Ctrl+S on Windows/Linux or Cmd+S on macOS while in Files.
  3. Wait for the save to finish. If it reports an error, resolve that error before assuming the machine has the new contents.
  4. Check your application. A development server may reload automatically; a production app may need a build, restart, or deployment.

Saving is explicit. An unsaved change in an editor tab is not the same as a saved change on the machine. If you close a tab with unsaved work, read the confirmation so you do not discard it accidentally.

Create, upload, rename, and measure

Right-click an item in the file tree to see the actions that apply to it. Use New File…, New Folder…, Upload Files…, Rename…, or Delete as appropriate. Upload Files… transfers selected files from your computer into the chosen machine directory.

Choose Storage usage… on a file or folder to calculate how much disk space it uses. A folder measurement includes its hidden contents. Large folders can take time to scan; an error or unfinished reading is not a size of zero.

Opening a file is not the same as running it. Use Terminal for commands and Servers for a managed application.

Review changes with Git

  1. Choose Git in the Files sidebar to see source-control information for your project.
  2. Open a changed file or use Compare with Last Commit to inspect the difference.
  3. Stage the intended changes, enter a commit message, and commit when ready.
  4. Push when you want to send the commit to the configured remote repository.

Save, commit, and push are different steps. Save writes the file on the machine; commit records changes in Git; push sends commits to the remote. A hosted GitHub deployment is triggered by a push to its configured branch, not merely by saving a file.