Two levels of access
The right user, the right directory.
Open the terminal where you work — on the whole server or inside a single site. Common commands are collected in a menu, and every command you run stays in the task log.
Terminal to a serverThe whole server — as the user you need
Full server access for administration: services, packages, diagnostics. As the chosen server user.
- By default — the deploykin user with sudo rights
- Pick another server user from the list next to the prompt
- Script mode: several lines of bash in one run
- Interactive programs like vim and top need regular SSH — the server menu has a link for it
$ whoami
deploykin
$ sudo whoami
root
$ systemctl --failed --no-pager
0 loaded units listed.
Terminal to a siteStraight in the site's directory, as its user
Commands run in the site's directory and as its system user — artisan, composer, wp-cli with no risk to neighboring sites.
- The cd into the site's directory is added for you; with zero-downtime deploys — into the current release
- The cd switch in the terminal header turns the automatic cd off
- Neighboring sites are off limits: each has its own system user
$ whoami
shop
$ pwd
/home/shop/shop.example.com
$ php artisan migrate --force
INFO Nothing to migrate.
Quick commandsCommon commands — from a menu
Server diagnostics, artisan and wp-cli are collected in the Quick commands menu. A command is inserted into the prompt, so you can edit it before running.
- Server: uptime, df -h, free -h, failed services, Nginx and syslog logs
- Laravel: optimize:clear, migrate, queue:restart, schedule:run, laravel.log
- WordPress: core version, plugins and themes, cache flush, file permissions
Laravel
shop@prod-01:$ php artisan queue:restart
INFO Broadcasting queue restart signal.
shop $
▶ Run
LogEvery command stays in the tasks
A terminal run is a regular server task: it keeps the command itself, its output, the start time and the duration. A failed command is kept too — with the error text.
- A link to the task — under the output of every command
- The ↑ and ↓ arrows recall previous commands
- Up to 10 minutes for a single command to run
- The log is kept for 90 days
Convenient and secure
Console access — by role, with no keys handed out.
The panel runs the command over its own SSH connection: keys and passwords never reach the browser and are never handed out to members. Who may run commands is decided by the team role.
- Owner, admin and developer run commands, a viewer does not
- Strict mode: before a command — a confirmation with a security key or password, and one covers 30 minutes
- Remove a member from the team and their terminal access is gone — no server keys to rotate
- All you need is a browser: you can handle an incident even from your phone
Strict mode
In the panel 203.0.113.21 Connect done in 4 min 52 s
The console is always at hand.
Open the terminal straight from the panel — to a server or a site, in one click.
- 7 days free
- No card required
- Human support