Use the Databases tab

What appears in Databases?

Databases shows PostgreSQL databases on the selected machine. Open one to see its tables and data. A database created through ForgeVPS has managed connection details and the editing and backup controls described below.

You may also see an existing database labeled Browse only. You can inspect it, but ForgeVPS does not have managed credentials for its editing and management actions. This label does not make PostgreSQL itself read-only. The self-hosted panel’s internal database is kept out of this list.

Create a database for an application

1. Open Databases on the machine that will host the database.
2. Choose New database and enter a name, such as my_app.
3. Create it and wait for the new entry to appear in the list.
4. Use Connect on that database to obtain its connection details, then add them to your application’s database configuration.

Creating a database gives your application a place to store data. It does not create the application’s tables for you. If your project uses migrations or an initial schema, run its setup instructions after configuring the connection.

Open a table and find a row

1. Click the database to open its browser.
2. Use Search tables… to find a table, then open it.
3. Read the column headings and use the table’s filter and sorting controls to narrow the data.
4. Move through result pages when there are more rows than fit on one page. You can open other tables in tabs without losing your place in the current one.

The table view is a page of results, not necessarily every row in the database. A filter can hide rows without deleting them. Clear the filter and refresh before deciding that data is missing.

Edit data in a managed database

Use the table editor’s row controls to add, edit, or delete records. Confirm the table and row before saving a change; these controls work with the real database used by your application.

Editing and deleting individual rows requires a primary key, which gives each row a reliable identity. If the table has no primary key, the interface cannot safely identify one row to change. A missing edit control can therefore be about the table structure rather than an account problem.

After a change, refresh or run a small query to confirm the result. If your application still shows old data, check its own caching and confirm it uses this database.

Use the SQL editor

1. Within a managed database, switch to SQL editor.
2. Enter the query you want to run against this database. Start with a read query if you are exploring.
3. Run it and read the results or error shown below the editor.
4. Return to Table editor when you want to browse visually.

The SQL editor executes the SQL you enter. A DELETE, UPDATE, or schema change is not a preview. For a large change, first check which rows it will affect and take a backup if you need a recovery point.

Connect the app to the right database

Connection details belong in the application’s environment or configuration. In Servers, open the app’s Env tab to edit its environment. Follow the project’s variable names rather than assuming every app uses the same name.

After changing environment values, restart a local production/development server or redeploy a GitHub server as directed by its Env tab. A process that was already running may still have its old values.

• Back up and restore data
• Bring a database from Supabase

Rename or delete a database

The rename control changes the actual PostgreSQL database name. Stop applications using it before renaming, then update their connection strings and start them again. It is not just a label change.

Deleting a database removes its data. If you only want an application to stop using it, change or stop the application instead. Take and download a backup before deletion if you will need that data later.