Buy

Terminal

Free & Premium

The Terminal page manages what makes up your shell on the Mac: shell aliases, the prompt, SSH keys, SSH host shortcuts and known hosts. You keep all of it in one place, and every new terminal window uses it without you editing dotfiles by hand. At the top of the page sits the WebDonkey CLI card for the wd command line.

What you do here

  • Check whether your terminal finds the wd command and jump to the command reference: CLI (wd)
  • Create shortcuts such as gs for git status -sb, switch them on and off, or take them over from your shell: Shell aliases
  • Build your command line from parts, with a live preview: Prompt
  • Generate key pairs, copy the public key, delete old keys: SSH keys
  • Create server shortcuts for ssh myserver and put your key on the server: SSH hosts
  • Remove stale server fingerprints after a server move: Known hosts

Page layout

The page has two tabs:

Tab Content
Shell & SSH from top to bottom the cards WebDonkey CLI, Shell aliases, SSH keys, SSH hosts and Known hosts. Known hosts is folded, the number in brackets counts its entries. A click on the heading unfolds it.
Prompt the designer for your command line with In use, My prompts, Templates and the Preview

WebDonkey remembers which tab was open for the current session. ⌘K finds both tabs directly, for example with the search word "prompt".

If an action on the Shell & SSH tab fails, the message appears as a red-framed line above the cards. A click on it dismisses it.

What happens in the background

WebDonkey never writes into the lines you wrote yourself. It generates its own files and pulls them in through clearly marked blocks:

  • Aliases and prompt live as files in ~/Library/Application Support/WebDonkey/config/ (aliases.sh and prompt.sh). A marked block in ~/.zshrc loads them, and in ~/.bashrc if you have that file. If ~/.zshrc is missing, WebDonkey creates it.
  • The SSH host shortcuts live in ~/.ssh/config.d/webdonkey. A marked Include block at the very top of ~/.ssh/config pulls them in. The rest of your ~/.ssh/config stays as it is.
  • WebDonkey generates SSH keys with ssh-keygen, straight into ~/.ssh.

Changes take effect in new terminal windows at once. In a window that is already open, reload with source ~/.zshrc or exec zsh. If you remove WebDonkey with wd uninstall, it takes the marked blocks out again.

The right versions in your shell

The setting Tools in the terminal (Settings › Sites & services) puts small forwarders for php, composer, node, npm, npx, mysql, mysqldump, psql, pg_dump, redis-cli and more tools on your PATH. They point to the versions WebDonkey manages and resolve per folder: inside the folder of a site with its own PHP version, php is exactly that version, otherwise the active one. wd reaches your PATH the same way.

PHP in the terminal uses the same php.ini as the web server, so php bin/console cache:clear gets the same memory_limit as your web requests. Composer runs without a memory limit. If you set PHPRC or PHP_INI_SCAN_DIR yourself, WebDonkey leaves them alone. More under Sites & services.

Free and Premium

Everything on this page is free. The one limit: on the Free plan you keep 3 own prompts. The eight templates in the Prompt tab do not count.

Shell aliases Free

An alias is a shortcut for a longer command: you type gs, the shell runs git status -sb. With Shell aliases you keep these shortcuts in a list instead of your .zshrc. WebDonkey writes them into a file of its own that your shell loads at startup.

Where to find it

Sidebar Tools › Terminal, tab Shell & SSH, card Shell aliases.

How to do it

  1. Click New alias.
  2. Enter the shortcut under Name, for example gs.
  3. Enter the command under Command, for example git status -sb.
  4. Click Save or press Enter in the Command field. The alias appears in the list.
  5. If the Load in shell checkbox at the top right is still off, switch it on. Only then does your shell load the aliases.
  6. Open a new terminal window and type gs.

Take an alias over from your shell

Below the list sits Detected in your shell with the number of matches. These are aliases your shell already knows, plugin packs such as oh-my-zsh included, that WebDonkey does not manage yet.

  1. Click Detected in your shell to unfold the list.
  2. Click Import in the alias's row.

The alias appears in your list (sorted by name) and is switched on. The original in your dotfiles stays untouched. WebDonkey's block goes to the end of your .zshrc when you switch it on, so for the same name the managed alias usually wins.

Edit, switch off, delete

  • Checkbox in front of the row: puts the alias into the generated file or leaves it out, without deleting it. A switched-off alias is struck through.
  • Pencil: opens Edit alias with name and command.
  • Bin: asks Delete alias? and removes it from the generated file after Delete.

Fields and options

Element Meaning
Load in shell on: a marked block in ~/.zshrc (and in ~/.bashrc, if present) loads the alias file. off: the block is removed, your aliases stay saved but have no effect. A yellow note reminds you.
Name the shortcut. Letters, digits and the characters _, -, . and : are allowed, 64 characters at most.
Command the command the shortcut stands for. It must not be empty.

While the list is empty, it suggests the classics gs, gl and ll.

What happens in the background

  • WebDonkey stores the aliases in its own database and rewrites the file ~/Library/Application Support/WebDonkey/config/aliases.sh on every change. It holds only the aliases that are switched on. Lines you edit in that file by hand are overwritten.
  • Load in shell appends a block between # >>> WebDonkey aliases >>> and # <<< WebDonkey aliases <<< to the end of ~/.zshrc that loads the file. If ~/.zshrc is missing, WebDonkey creates it. ~/.bashrc only gets the block if the file already exists. Switching Load in shell off takes exactly this block out again.
  • For Detected in your shell, WebDonkey asks an interactive shell for its aliases. That is why the page takes a moment to load.

Troubleshooting

What you see Why What you do
The alias does nothing in an open terminal The shell read its startup file before the change Run source ~/.zshrc or open a new window
Yellow note that the aliases are not active Load in shell is off Switch the checkbox on
Message invalid alias name The name contains spaces or other characters Use only letters, digits, _, -, . and :
The alias does something else than expected A line after the WebDonkey block in your .zshrc defines the same name again Remove the duplicate alias from your .zshrc

See also

Prompt Free & Premium

The prompt is the text to the left of your cursor in the terminal, such as folder, Git branch and a ❯. In the Prompt tab you assemble it from parts, without writing escape codes, and see the result right away in the Preview. WebDonkey turns it into shell code for zsh and bash.

Where to find it

Sidebar Tools › Terminal, tab Prompt. ⌘K with the search word "prompt" takes you straight there.

How to do it

Use a template

  1. Pick a design under Templates. Every card shows a small preview.
  2. Click Use. The message Prompt switched. confirms it, the card shows In use.
  3. Open a new terminal window. In a window that is already open, run exec zsh.

There are eight templates: Frame, Minimal, Arrow, Brackets, Status line, Rounded, Classic and Timestamp.

Build your own prompt

  1. Click New under My prompts, or Adapt on a template. The editor New prompt opens on the right.
  2. Enter a Name, for example "My prompt".
  3. Add parts with Add part. Every line of the prompt has its own picker.
  4. Click a part in the line to change it. Its settings appear below.
  5. Click Save and use. The prompt sits under My prompts and is active.

Save only stores the prompt without switching to it.

Fields and options

The parts

Part Shows Setting
Text fixed text, up to 40 characters Text, plus Characters with frame and arrow characters such as ╔═, ┌─ or ❯
Folder the current folder Display: Full path (~/Sites/shop), Last two folders (Sites/shop) or Folder name only (shop)
User your user name
Computer the name of the Mac
Time the time when the prompt is shown Hours and minutes (14:05) or With seconds (14:05:09)
Date the date 30-09-2026, 30.09.2026 or 2026-09-30
Git branch the branch, only inside a Git repository Template ({branch} = branch name), such as ({branch}). {branch} must appear exactly once, other braces are not allowed.
Result whether the last command worked Symbol on success, Symbol on error, Display: Symbol only or Symbol and exit code
$ or # the input character: # when you work as root, otherwise the shell's usual character (% in zsh, $ in bash)

For every part

  • Colour: one of the 256 terminal colours or Terminal default. For Result you pick Colour on success and Colour on error separately.
  • Bold: sets the part in bold.
  • Space after: adds a space after the part.
  • Move left, Move right: moves the part within the line.
  • Remove part: deletes the part.

Lines and preview

  • Add line adds another line, Remove line deletes it. A prompt has 1 to 4 lines with 1 to 12 parts each.
  • The Preview shows the prompt as in the terminal. Last command failed and In a git repository show how it looks in those cases.
  • Shell code shows the file your .zshrc and .bashrc load. WebDonkey rewrites it on every change.

My prompts and In use

  • Every card under My prompts has Use, Edit (pencil), Duplicate and Delete.
  • In use at the top names the active design or Your own prompt from ~/.zshrc.
  • Use my own switches WebDonkey's design off, your own prompt from .zshrc applies again.
  • If you delete the active prompt (Delete prompt?), your own prompt comes back as well.

What happens in the background

  • The active design becomes the file ~/Library/Application Support/WebDonkey/config/prompt.sh. A marked block at the end of ~/.zshrc loads it (and at the end of ~/.bashrc, if that file exists). Because it sits at the end, it wins over a PROMPT=… further up in the same file.
  • Use my own removes this block again. WebDonkey never touches your own lines in .zshrc.
  • Text from your design lands safely in the shell code: characters such as $, backticks or % stay literal and are never run.

Free and Premium

The eight templates are free for everyone and do not count. On the Free plan you keep 3 own prompts, a counter next to New shows where you stand. At the limit, New, Adapt and Duplicate are locked. Premium has no limit.

After a switch from Premium to Free all your prompts are kept. Those above the limit are locked: you can rename and delete them, but not use or change them until Premium is active again.

Troubleshooting

What you see Why What you do
Yellow note that Powerlevel10k, Starship, Oh My Posh, Spaceship or Pure builds its own prompt These tools set the prompt anew on every command and win over WebDonkey Remove or comment out the entry in your .zshrc, then exec zsh
The new prompt does not appear The terminal window was already open Run exec zsh or open a new window
Message that the git template needs {branch} {branch} is missing or the template has other braces Change the template to exactly one {branch} without other braces
Message that a text part must not be empty A Text part has no content Enter text or remove the part

See also

SSH keys Free

An SSH key is a key pair: the private half stays on your Mac, the public half goes onto the server, into GitHub or into your hosting panel. After that you log in without a password. SSH keys shows the key pairs in ~/.ssh, generates new ones and copies the public half.

Where to find it

Sidebar Tools › Terminal, tab Shell & SSH, card SSH keys.

How to do it

Generate a key

  1. Click New key.
  2. Enter a File name. The default is id_ed25519.
  3. Choose the Type: ed25519 (short and modern, right for almost every server) or RSA 4096 (for older servers that do not know ed25519).
  4. Under Comment, enter what tells you later which key this is, commonly you@machine.
  5. Set a Passphrase (optional) if you want one. Empty means no passphrase. WebDonkey does not store it.
  6. Click Save. While the key is generated, the button reads Generating….

Hand out the public key

  1. Click Copy public key in the key's row. The button briefly shows Copied.
  2. Paste the text where the server expects it: into ~/.ssh/authorized_keys on the server, into GitHub's SSH settings or into your hosting panel.

For your own servers there is a quicker way: create an SSH host with this key, and WebDonkey offers Add key.

Delete a key

  1. Click the bin in the row.
  2. The question Delete SSH key? names the key. Confirm with Delete.

This deletes both halves of the pair from ~/.ssh. Servers that only trust this key become unreachable. This cannot be undone.

Fields and options

Column or field Meaning
Name the file name in ~/.ssh
Type badge for example ed25519 or rsa
public key only the private file of this key is missing. You can hand it out but not log in with it.
Fingerprint the short form of the key as ssh-keygen -l shows it. If it is missing, the comment appears instead.
File name letters, digits, _, - and ., 64 characters at most, not starting with a dot
Type ed25519 or RSA 4096
Comment free text at the end of the public key
Passphrase (optional) protects the private file. ssh asks for it when you use the key.

If ~/.ssh is empty, the card says No SSH keys found in ~/.ssh.

What happens in the background

  • The list shows every .pub file in ~/.ssh and checks whether the private file sits next to it.
  • New key runs ssh-keygen and creates ~/.ssh/<file name> and ~/.ssh/<file name>.pub. If the folder ~/.ssh is missing, WebDonkey creates it with mode 700.
  • If a file with that name already exists, WebDonkey stops instead of overwriting it.

Troubleshooting

What you see Why What you do
a key with this name already exists ~/.ssh already holds a file with this name Choose another File name
invalid key name The name contains spaces, / or starts with a dot Use only letters, digits, _, - and .
A key is missing from the list It has no .pub file Recreate the public file with ssh-keygen -y -f ~/.ssh/<name> > ~/.ssh/<name>.pub

See also

SSH hosts Free

With SSH hosts you create shortcuts for your servers. After that, ssh webserver-prod is enough instead of ssh -p 2222 -i ~/.ssh/id_ed25519 deploy@203.0.113.10. Everything built on the SSH configuration uses the shortcut too: scp, rsync, git and the remote features of many editors.

Where to find it

Sidebar Tools › Terminal, tab Shell & SSH, card SSH hosts.

How to do it

  1. Click New host.
  2. Fill in the fields (see below). Alias and Hostname / IP are required.
  3. Click Save. The host appears as ssh <alias> in the list, next to it user, address, port (if not 22) and key.
  4. Right after that, WebDonkey checks the key login. The result shows above the list.
  5. Open a new terminal window and type ssh <alias>.

Put the key on the server

If the server does not know your public key yet but offers a password login, the dialog The server does not know this key yet opens:

  1. If the server is not in ~/.ssh/known_hosts yet, the dialog shows the fingerprint of its host key. Compare it with the one your hoster gives you and tick The fingerprint matches, trust this server.
  2. Enter the user's password once under Password of ….
  3. Click Add key.

WebDonkey adds the public key to ~/.ssh/authorized_keys on the server, like ssh-copy-id, and checks the login again. Then the line above the list says Done: the key login works. The password is not saved. Under Rather in the terminal? This does the same: you find the matching command to copy.

Edit and delete

  • Pencil: opens Edit host. If you change address, user, port or key, WebDonkey checks the login again.
  • Bin: asks Delete host shortcut? and removes the host after Delete. After that, ssh <alias> stops working.

Fields and options

Field Meaning Default
Alias the shortcut you type, for example webserver-prod empty, required
Hostname / IP the server's address, for example example.com empty, required
User (optional) the login, for example deploy. Empty: ssh uses your Mac user name. empty
Port the server's SSH port 22
SSH key (optional) one of your SSH keys with a private file. ssh default leaves the choice to ssh. ssh default

Result of the key check

Message Meaning
Key works: "ssh …" logs in without a password. all set, the message disappears after a few seconds
No key set for "…": ssh will ask for the password on every login. you chose ssh default, WebDonkey does not check then
The host is saved, but the key login could not be checked: … the reason follows, for example an unreachable server. The host stays saved.

What happens in the background

  • WebDonkey writes all hosts into the file ~/.ssh/config.d/webdonkey (mode 600) and rewrites it on every change. Lines you edit in it by hand are overwritten.
  • At the very top of ~/.ssh/config sits a marked block (# >>> WebDonkey ssh config >>>) with an Include line for this file. It has to be at the top, otherwise ssh would read it only inside another Host section. The rest of your ~/.ssh/config stays byte for byte.
  • When you delete the last host, WebDonkey removes file and block again.
  • For Add key, WebDonkey logs in once with the password and adds to ~/.ssh/authorized_keys on the server.

Troubleshooting

What you see Why What you do
The key path contains a line break or a quotation mark. Pick the key file again. Such a path could write a line of its own into the SSH configuration, WebDonkey refuses it Pick the key from the list again
ssh <alias> does not know the host The terminal read the configuration before you saved, or your own Host section with the same name is in the way Connect again. Remove duplicate entries from ~/.ssh/config.
ssh warns about a changed identity The server was set up anew Remove the old entry under Known hosts
ssh asks for the password despite the key The public key is not on the server Edit the host and save, then Add key in the dialog

See also

Known hosts Free

On first contact with a server, ssh remembers its fingerprint in ~/.ssh/known_hosts. If it changes later, ssh refuses the connection because it cannot rule out an attack. Known hosts shows this file in readable form and removes single entries, without you hunting for lines by hand.

Where to find it

Sidebar Tools › Terminal, tab Shell & SSH, the card Known hosts at the bottom. It is folded, the number in brackets counts the entries. A click on the heading unfolds it.

How to do it

The usual case: a server was set up anew or moved, and ssh reports REMOTE HOST IDENTIFICATION HAS CHANGED.

  1. Unfold Known hosts.
  2. Find the server's entry. Every row shows the address (or hashed entry) and the type of the host key.
  3. Click the bin in the row.
  4. Confirm Remove entry? with Delete.
  5. Connect again. ssh asks for the server's fingerprint once more.

Check the new fingerprint before you accept it, especially if you did not set the server up anew yourself. A changed identity can also mean that someone sits in between.

Fields and options

Element Meaning
Address the host as written in the file, for example example.com,203.0.113.10 or [example.com]:2222
hashed entry ssh stored the address unreadably (option HashKnownHosts). ssh-keygen -F <address> in the terminal tells you which server it is.
Type badge the type of the host key, for example ssh-ed25519

If the file is empty, the card says ~/.ssh/known_hosts is empty.

What happens in the background

  • Before removing, WebDonkey backs up the whole file as ~/.ssh/known_hosts.old, the way ssh-keygen -R does. Every removal writes this backup anew.
  • Before deleting, WebDonkey checks that the line still holds the same host. If the file changed in the meantime, it stops instead of deleting the wrong line.
  • The connections on the Remote pages keep their server fingerprints separately. This list only affects the ssh in your terminal.

Troubleshooting

What you see Why What you do
Message that known_hosts changed (known_hosts changed on disk) The file was changed after the page read it Reopen the page and remove the entry again
ssh still reports a changed identity after removing The server has several entries, for example for name and IP Remove the server's other entries too

See also

Cookie preferences

This website uses cookies to ensure the best experience possible. Your choice applies to webdonkey.io and the shop at shop.webdonkey.io. More information...

Technically required

Cookies required for this website to function:

Always on
WebDonkey
WebDonkey
Provider: BuI Hinsche GmbH, Neumarkt 7, 06712 Zeitz, Germany
Purpose: Your consent, colour scheme and language for website and shop, price switches; with wd_debug in the address, the measurement events in the developer console for troubleshooting
Cookies and storage: Cookie wd_consent on .webdonkey.io, shared with shop.webdonkey.io (12 months); cookies wd_theme and wd_lang on .webdonkey.io, shared with shop.webdonkey.io, only when you switch colour scheme or language yourself (365 days); localStorage wd:consent, wd:theme, wd:lang; sessionStorage wd:acc, wd:term, wd:debug (only with wd_debug in the address; until the tab closes)

Statistics

Shows us which pages and products people look at on webdonkey.io and in the shop, where visitors come from and how they get to a purchase (with order number, amount and products, without name or email address). Provider: Google. Transfer to the USA possible (EU-US Data Privacy Framework). Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Google Analytics 4
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Google Analytics 4
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Usage statistics: page views, clicks, scroll depth, sources, devices, load times; in the shop also basket, checkout, purchases, registration and sign-in
Cookies and storage: _ga, _ga_<ID> (2 years)
Privacy policy

Marketing

Measures whether our ads on Facebook, Instagram and TikTok lead to visits and downloads on webdonkey.io and to registrations and purchases in the shop, and builds audiences for ads. Providers: Meta and TikTok, with whom we are jointly responsible for this. With this consent Google may also set advertising cookies (_gcl_…). Transfer to the USA and other countries outside the EU possible. Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Meta Pixel (Facebook, Instagram), TikTok Pixel
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Meta Pixel (Facebook, Instagram)
Provider: Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland
Purpose: Ad measurement and target groups on Facebook and Instagram, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _fbp (3 months), _fbc (3 months, only if you arrive through an ad), fr on facebook.com (3 months)
Privacy policy
TikTok Pixel
Provider: TikTok Technology Limited, 10 Earlsfort Terrace, Dublin, D02 T380, Ireland
Purpose: Ad measurement and target groups on TikTok, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _ttp, _tt_enable_cookie (13 months)
Privacy policy