Getting into your app: console, files and database

Managed hosting usually means you can use the application and nothing else. That is not the case here.

Console

The Console tab opens a shell inside your app's container. Run commands, read logs, inspect configuration — whatever the application's own documentation tells you to do.

For an app with several containers, the console opens on the application itself by default. You can choose another service if you need to.

The app has to be running for the console to open.

Files (SFTP)

The Files tab issues SFTP credentials for your app's data. Connect with any SFTP client — FileZilla, Cyberduck, WinSCP, sftp on the command line.

The account reaches your app's data and nothing else. It cannot be used for a shell or for tunnelling.

Database

If your app has a database, the Database tab shows its credentials and offers a one-click export. The export is a normal dump file you can restore anywhere.

You can also import a dump to replace the database contents — useful when migrating an existing installation in.

Your database is not reachable from the internet. Only the application's own public port is exposed; the database sits on a private network shared with just that app.

Environment variables

The Environment tab shows the variables the app runs with and lets you change them. Saving recreates the container so the new values take effect.

One limitation worth knowing: variables cannot be edited on an app that runs several containers, such as anything with its own database. Rewriting a value on a running multi-container app risks leaving the pieces holding credentials that no longer match each other. If you need a change on one of those, open a ticket.