Access

1. The sections, and who can see them

Each section has its own permission, so a team member can be given one without the others.

The split is deliberate: a developer can be given SFTP access without being able to read the database password, and someone can be allowed to see credentials without being able to change them.

2. Application URL

The addresses the application answers on:

Scheme is selectable — http:// or https://. Frontend and backend URLs matter for split applications (a React frontend calling a separate API): they are what the application is configured to call itself, so getting them wrong produces a site that loads but cannot talk to its own API.

3. Master User Details

The application's primary SSH and SFTP account — username, password, and the host and port to connect to.

This is the account that owns the application's files. Use it for deployment and administration; create separate users below for anyone who only needs to upload.

4. Additional SSH / SFTP users

Extra accounts scoped to this application.

Add New User takes:

• Username — Enter Username, validated
• Password — Enter Password

Edit changes an existing user; Delete User removes one, with confirmation. Both report progress (Creating User…, Deleting User…) and failures rather than going quiet.

Why use these rather than sharing the master account: each person gets their own credentials, so revoking one does not disturb anyone else, and file changes are attributable. Sharing the master password means rotating it for everybody whenever one person leaves.

5. SSH keys and the terminal

Keys authorised for this application's users, added two ways:

Generate Key — the panel creates a keypair. You give it a Key name (Enter Key name (e.g. my-ssh-key)), and it generates and installs it.

Add Public Key — Paste Your Public Key Here for a key you already have. This is the better option when you have one: your private key never reaches the panel.

Validation is explicit — Please enter a key name first, Please enter your public key, Please fix the key name errors — so a malformed key is caught before it is installed rather than after it fails to work.

Launch SSH Terminal opens a shell in the browser, scoped to this application. Failed to start SSH session generally means the server is unreachable rather than that credentials are wrong.

6. Database Credentials

The panel of most daily use.

What it shows

Edit changes the credentials, behind Access_Database_Credentials_Edit.

Application credentials are not available means none are bound yet — see changing the database below.

No database password available to copy means the record exists but the password was not stored, which happens with databases attached outside the panel.

Launching a database manager

Launch Database Manager opens a web client, installed on demand:

The panel installs it the first time (Loading phpMyAdmin…, Failed to check/install phpPgAdmin) and opens it in a new tab. MongoDB has no web client here.

Changing which database the application uses

Three options:

• Choose Existing Database — pick one already on the server. It lists what is there, with Search databases by name or username… and Refresh databases. No databases found on this server or No databases match your search when there is nothing to pick.
• Add New Database — create one and bind it in a single step.
• Change Database — repoint the application at a different database.

Confirm & Link commits the change.

7. Database Import

Upload a dump straight into the application's database.

Accepted: .zip or .gz. The form refuses anything else — Please choose a .zip or .gz dump file first — and shows No file selected until you pick one.

Import runs it, showing Importing… while it works.

An import replaces data. Take a backup from the application's Backup section first — that path takes a safety copy automatically, this one is a direct import.

8. Folder Permissions

Set filesystem permissions on the application's directories.

Mode — e.g. 755 or 775. Confirmed with Permissions updated successfully; failures report Failed to update permissions.

Sensible values:

Avoid 777. It is the reflexive fix for a permissions problem and it makes every file world-writable, which on a web-facing server means anything that achieves file access can rewrite your application. If 775 does not work, the owner or group is wrong — fix that instead.

9. Sensible practice

• One SFTP user per person. Revoking access then means deleting one account.
• Upload keys rather than generating where you already have one.
• Copy the connection URI rather than assembling it by hand — it carries the right host, port and database.
• Back up before importing or relinking. Both replace what the application reads.
• Do not reach for 777.
• Use the database manager for inspection, not bulk changes. For a large import use the Import section; for a large export use Backup.

10. Common problems