Buy

Services

Free & Premium

The Services page is where you manage everything that powers your local development setup: databases, web servers, PHP in several versions, cache, search, queue, storage and mail, plus runtimes such as Node.js, command line tools, apps and AI CLIs. Every service runs in exactly the version you chose, with its own configuration, data and log. Nothing updates or switches by itself.

What you do here

Page layout

  • Header: title and description. On Free, the right side shows how many services run, such as "4/6 services running".
  • Views: Installed, Updates and Discover, each with its count. WebDonkey remembers the view you picked until you quit the app.
  • Search field "Search services and tools…": filters the view shown by name. The counts on all three views follow the search, so you also see hits in the other views.

Default ports

Service Port
MySQL 3306
MariaDB 3307
PostgreSQL 5432
MongoDB 27017
Redis 6379
Memcached 11211
Meilisearch 7700
OpenSearch 9200
RabbitMQ 5672, web interface 15672
MinIO 19000, console 19001
Mailpit SMTP 10025, web interface 18025
Ollama 11434
Adminer 8085
nginx 8080 and 8443
Caddy 8081 and 8444
Apache 8082 and 8445
Front proxy 80 and 443

The web servers listen on their own ports, and the front proxy forwards the domains from 80 and 443 to them. PHP runs as PHP-FPM over a socket, without a port.

Free and Premium

On Free, up to six services run at the same time. Every running PHP version counts on its own. Not counted are the front proxy, the processes of sites with a serve command, and Adminer, which the Databases page starts by itself for its DB browser. Apps, tools and AI CLIs do not count either, they do not run as services. Once the limit is reached, Start is locked for further services and the counter carries the Premium badge.

When a Mac with more running services moves from Premium to Free, WebDonkey asks with Choose your services which six should run. The rest stay stopped. Premium lifts the limit. Prices: webdonkey.io/pricing.

Installed and Discover Free

The Installed view shows everything on this Mac: the services that run or are off, what else is running, and the runtimes, tools, apps and AI CLIs. Discover lists what you can still add. Both views share the search field at the top right.

Where to find it

Sidebar Local › Services, view Installed or Discover. Manage services in the Active services menu leads straight to Installed. In the terminal, wd services, wd start, wd stop and wd restart control the same services, see Core commands.

Installed

From top to bottom:

  1. Numbers: Running, Installed, off and Runtimes, tools and apps.
  2. Running: the running services. A crashed service shows up here too, marked red.
  3. WebDonkey: WebDonkey, the WebDonkey Editor and WebDonkey Pages, as far as installed, see The WebDonkey apps.
  4. Installed, off: services that are installed but stopped.
  5. Also running: what else runs, the front proxy and the processes of sites with a serve command, each with Restart and Stop.
  6. Runtimes, Tools, Apps and AI CLIs: one group per kind, with a Check again button for the update check. See Apps and tools.
  7. System check: checks every running service, see System check.

Within Running and Installed, off, your favourites come first, then everything else by name. While nothing is installed at all, it says "Nothing installed yet." with the Discover button.

A service's row

Every service row has the same slots, so versions, ports and buttons line up:

Slot Content
Name Logo, name and a star. The star makes the service a favourite, it then sits at the top of its group. Below, the state: how long it has been running, crashed, starting… or off, and the kind, such as Database or Web server.
Versions Every installed version side by side. The chosen one carries active, a running one a green dot, and each one a dot for its version status. Clicking another version makes it the active one after a confirmation, see Install and choose versions. If the chosen version is no longer installed, it appears dashed with missing.
Port The main port, with further ports below. For PHP it says Socket.
Actions Start or Stop, Versions, Restart, Logs, Configuration, Open web interface and Remove.

The actions in detail:

  • Start starts the active version, Stop stops what runs. Start is locked while no version is chosen ("Choose which installed version to start first") or when Free's limit of six services is reached.
  • Versions opens the service's versions. When Homebrew has a newer build of an installed version, the button says Update, and its tooltip names old and new.
  • Restart stops and starts the service. For PHP the button is locked, there every version has a button of its own.
  • Logs opens the Logs page with this service's log, Configuration opens the Configuration page with its configuration file.
  • Open web interface (port …) opens the interface in the browser, for Mailpit, RabbitMQ or MinIO for example. Without an interface, or while the service is off, the button is greyed out.
  • Remove uninstalls the service with every version, see Uninstall a service.

PHP in several versions

PHP versions run side by side so every site gets its own. That is why each PHP version in the row has its own start and stop button. Start starts the active version, Stop stops every running one. WebDonkey also manages Node.js, Composer and Hugo in versions but does not start them as services. They are listed under Runtimes and Tools.

Problems in the row

When a start fails, the reason appears right in the row, with the step that fixes it:

  • Chosen version missing: "… is not installed (any more)." WebDonkey does not start another version in its place. If there is a newer version of the same line, the row offers Switch old → new, next to Versions.
  • Library replaced: if Homebrew renewed a library a version was built against, that version no longer starts. Repair fetches the matching build from Homebrew and starts the service again. Your data stays.
  • PostgreSQL data does not fit: another major version cannot open the data folder. The row names the version needed and offers Set old data aside, see Autostart and lifecycle.

If another program holds a service's port, a banner appears at the top of the window, such as "MySQL cannot start", naming the program that holds the port. Free port … stops that program and then starts the service again. If a system process holds the port, WebDonkey cannot free it.

Discover

Discover lists what is not on this Mac yet. The chips choose the kind, each with its count: All, WebDonkey, Services, Runtimes, Tools, Apps and AI CLIs.

  • WebDonkey: a missing app of the family, at the very top under All, see The WebDonkey apps.
  • Services: one tile per service with kind, port and description. Choose version… opens the versions, where you install the one you want. Afterwards the tile shows Installed and Show under Installed.
  • Runtimes, Tools, Apps and AI CLIs: the same cards as under Installed, with Install as the main button. See Apps and tools and AI CLIs.

What you install here stays in its place until you leave the view, with its progress and its result. Only then does it move to Installed.

If Homebrew is missing, the top says "Homebrew is missing. WebDonkey installs it for you …" with Install Homebrew. If Node.js is missing, a note offers Install Node.js.

Searching

The search field "Search services and tools…" filters the view shown by name. Without a hit it says "No match for "…"." If another view or chip has hits, a button leads there, such as Search under "Discover" (3) or Search all kinds (5).

Free and Premium

On Free, up to six services run at the same time, see Services. Once the limit is reached, Start is locked and its tooltip says "Free service limit reached". Installing, Discover and every other button are part of Free.

Troubleshooting

What you see Why What to do
A banner with Free port … Another program holds the service's port. Click Free port … or quit the other program yourself.
"Port … is held by a system process" A macOS process holds the port, WebDonkey does not stop it. The message names it in brackets when it is known. Turn off the system service that uses the port in System Settings and start the service again.
Start is locked No version is chosen, or Free's limit is reached. Click a version and confirm, or stop another service.
An install fails The card explains the cause, such as no network, a full disk or missing Command Line Tools. Follow the cause. Details shows what the installer reported.
Homebrew may not write to its folder The folder belongs to another user account. Repair permissions. macOS asks for an administrator's password.

See also

Updates Free

The Updates view gathers everything on this Mac that has a newer version and that WebDonkey can update itself: runtimes, tools, apps and AI CLIs, npm and the WebDonkey apps. You see in one place what is due instead of checking every group on its own.

Where to find it

Sidebar Local › Services, view Updates between Installed and Discover. The number on the tab says how many updates are open.

How to do it

  1. Open Services and switch to Updates.
  2. Wait a moment until the check is through. Meanwhile it says "Checking for updates…".
  3. Click Update on an entry. The card shows the progress and then the new state with up to date.
  4. Check again at the top looks again at any time.

With nothing open, it says "Everything is up to date."

What the view shows

From top to bottom:

  • WebDonkey: WebDonkey, the WebDonkey Editor and WebDonkey Pages, when their update channel offers a newer version. They always come first, see The WebDonkey apps.
  • npm: "npm … is installed; … is available." with Update npm, when there is a newer release.
  • Runtimes, Tools, Apps and AI CLIs: one group per kind with every entry that has a newer version. The card shows old → new and the Update button.

What you update here stays until you leave the view and shows up to date. The counts only name what is still open. The search field filters this view too.

What is not listed here

  • Services such as MySQL, PHP or Redis have no update check in this view. Their newer builds show up on the button in the service's row, which then says Update instead of Versions, see Install and choose versions. That way every version stays exactly the one you chose.
  • Tools and apps installed elsewhere, with the vendor's installer for example, are recognised by WebDonkey but not updated. That happens where they came from.

What happens in the background

  • On every visit to the Services page, WebDonkey checks once every installed entry that came through Homebrew or npm, one request per kind. That is why the tab shows a count even before you open the view.
  • The check asks Homebrew and npm for the newest version. For the WebDonkey apps, WebDonkey asks their update channel, at most every ten minutes.
  • Without internet, the check waits and runs as soon as the Mac is back online.
  • Some apps such as Visual Studio Code or Google Chrome update themselves. Their card then says updates itself. You can still update them here.

Free and Premium

The view is entirely part of Free.

Troubleshooting

What you see Why What to do
The count stays 0 although you expect an update The check ran before the update was published. Click Check again.
Homebrew would upgrade something else too The update needs newer versions of formulae that are already installed. Nothing has changed yet. Check the list and click Upgrade and install, or cancel.
Updating fails The card explains the cause, Details shows the installer's message. Follow the cause, then click Update again.
"npm update failed: …" npm could not update itself. Read the message, often write permissions in npm's global folder are missing.

See also

Install and choose versions Free

Every service and runtime can be on your Mac in several versions. In the versions dialog you install new versions, update a release line, remove old ones and decide which version is active. The active version is used for the next start and in the terminal. Sites can keep their own PHP and Node version independently of it.

Where to find it

  • In a service's row: Versions (or Update when an update is waiting).
  • For runtimes such as Node.js: Manage versions, or Install while no version is installed.
  • For a service under Discover: Choose version….
  • In the terminal: wd services install <name>@<version> installs, wd services use <name>@<version> sets the active version.

How to do it

Install a version

  1. Open the versions dialog.
  2. Find the version under Installable here and click Install.
  3. A progress display shows the phases: Downloading, Extracting, Configuring, Compiling, Installing. You can close the dialog, the install keeps running.
  4. The version appears at the top under On this Mac.

A new version never becomes active by itself. To use it, make it active.

Switch the active version

  1. Click the version you want in the service's row, or Make active in the dialog.
  2. The confirmation "Switch the version of …?" names old and new and what happens, such as "The next start of MySQL uses 8.4.3."
  3. Click Switch.

If the service is running, WebDonkey stops the old version and starts the service on the new one. For PHP and the runtimes, the new version becomes the one for the terminal and new starts, versions that run keep running, and sites keep their own version. Nothing is downloaded or installed, and you can switch back at any time.

Update a release line

When Homebrew has a newer build of an installed line, the button in the service's row says Update. In the dialog, the line says "8.4.3 installed" with the button Update to 8.4.5. If Homebrew moves to another release line in the process, with MySQL for example, WebDonkey asks first. The new line then starts with an empty data folder of its own, and the databases of the old line stay on your Mac.

Remove a version

  1. Click Remove on the version in the dialog.
  2. Confirm "Remove this?". If the version came from Homebrew, WebDonkey also asks "Remove Homebrew installation?", because brew uninstall affects everything that uses that installation. Confirm with Remove anyway.

If it was the active version, the dialog then says which one is active now. Sites that used the removed PHP version are moved to another one, and the dialog says how many. If the Homebrew formula stays installed, the dialog offers Remove the formula too.

The versions dialog

  • On this Mac: the installed versions as tiles. Each shows its state (running, off or crashed), active on the chosen one, its version status and Recommended on the version you should rather install. Plus Make active and Remove, and Repair for a broken version.
  • Installable here: everything that really installs on this Mac, by source:
    • via Homebrew: ready builds for this Mac, installed in seconds. One row per release line with the newest build Homebrew knows.
    • prebuilt binary: vendor downloads outside Homebrew. WebDonkey makes them available in the terminal itself.
    • from source: collapsed. WebDonkey downloads the source and compiles it, which takes from a few minutes to a good half hour depending on the service. Missing tools such as a compiler or pkg-config are installed first.
  • Reload fetches the current list and asks Homebrew for its current state. Nothing installed changes.

Every row names the exact version. newest is only a hint for choosing. Versions without a ready package for your Mac, formulae Homebrew has disabled and downloads without a published checksum are not offered. Unmaintained lines carry unmaintained when the version status has nothing more precise.

Sites with their own version

A site with PHP 8.3 always uses 8.3, whichever version is active globally. That way old and new projects run side by side. If a site's version is no longer installed, the dialog warns "… site(s) use a PHP version that is no longer installed" and lists the sites with the configured and the actual version.

What happens in the background

  • WebDonkey stores the active version as an exact version number. It only changes when you change it.
  • WebDonkey never runs brew update or brew upgrade by itself. If Homebrew would have to upgrade something already installed for an install, WebDonkey stops and asks "Homebrew would upgrade something else too" with the list old → new. It only goes on after Upgrade and install.
  • If a version was changed outside WebDonkey, with brew upgrade in the terminal for example, WebDonkey keeps starting your chosen version as long as it is there. The dialog reports "…: version changed outside WebDonkey" and offers Adopt ….
  • Databases keep a data folder per version series.

Troubleshooting

What you see Why What to do
missing on the active version The chosen version is no longer installed, often after brew upgrade. WebDonkey does not start another one in its place. Switch old → new in the row, or make another version active. For PHP, your php.ini of that version moves along.
A version does not start and Repair appears Homebrew replaced a library the version was built against. Repair fetches the matching build. Data and settings stay.
The vendor publishes no SHA-256 checksum WebDonkey does not install anything unchecked. Take another version or the Homebrew variant.
GitHub's limit of 60 requests per hour is reached Prebuilt binaries often come from GitHub, which limits anonymous requests. The message says when it works again.
Apple's Command Line Tools are missing A build from source needs the compiler. Finish the installer macOS opens and click Install again.

See also

Version status Free

The version status tells you at every version whether it still gets updates: supported, security fixes only, close to the end, without any support (EOL), or with a known vulnerability. That way you spot an old PHP or an unsupported database before you build a site on it. The marks are hints only, every version stays selectable and installable.

Where to find it

The marks appear by themselves wherever versions are shown:

  • Services: as a coloured dot on every installed version in a service's row and for the runtimes.
  • Versions dialog: as a mark with a word on every version, plus Recommended, see Install and choose versions.
  • Sites: as a dot in the Runtime column, see The WebDonkey tab.
  • A site's form: below the PHP version and Node version fields, the mark of the chosen version, and in the lists the additions EOL or Recommended. With the Shopware 6 package also at the Shopware version field.
  • DDEV: in a project's Configuration form at the PHP, database and Node.js version, and in the lists when creating a project, see Manage a DDEV project.

Hover a mark or a dot and the tooltip shows the full reasoning.

The marks

Mark Colour Meaning
Supported green The release line gets full updates.
Update available grey There is a newer release of the same line.
Security fixes only grey The line only gets security fixes, no more bug fixes.
Support ends soon yellow Support for the line ends within 90 days.
Vulnerable red A newer release of this line fixes a known vulnerability.
EOL red The line gets no more updates, not even security fixes.
Recommended accent colour Rather install this version: newest line with full support, with long-term support the newest LTS line.

When several reasons apply, the mark shows the weightiest. The tooltip names them all, such as "Release line 8.1", "No updates since …, not even security fixes.", "Known vulnerability, fixed in …", "Long-term support (LTS).", "Recommended: line 8.4." and finally "As of … (endoflife.date, vendors)".

Without data there is no mark, for example offline the first time, or for a product the version status does not know.

Which products

PHP, Node.js, nginx, Apache, Caddy, MySQL, MariaDB, PostgreSQL, MongoDB, Redis, Valkey, Memcached, RabbitMQ, OpenSearch, Meilisearch, Composer, Shopware, WordPress and Magento.

Settings

The Fetch version status switch under Settings › General is on by default, on Free and on Premium. Turned off, WebDonkey asks nobody any more and every mark disappears at once. The WebDonkey Editor takes this switch as its default. See General.

What happens in the background

  • WebDonkey asks endoflife.date, php.net, nodejs.org and nginx.org directly from your Mac for end-of-support dates and known vulnerabilities.
  • Only product names go out, for PHP also the major version of the release list. Your installed versions, sites or servers never leave the Mac.
  • WebDonkey only asks once a mark is needed. It stores the answers under ~/Library/Application Support/WebDonkey/cache/versionsstatus/. A copy younger than 24 hours is used as it is. An older one is shown right away and renewed in the background.
  • If a request fails, the old copy stays and the source rests for an hour.

Free and Premium

The version status is the same on Free and Premium.

Troubleshooting

What you see Why What to do
No mark anywhere Fetch version status is off, or the Mac was offline on the first request. Turn the switch on under Settings › General, or look again later.
A version has no mark The product or the line is not known to the sources. Nothing. The version works all the same.
A version is EOL but you need it Old projects often need old versions. Keep using it. The mark only advises, it locks nothing.

See also

Apps and tools Free

Besides services, the Services page installs developer tools that do not run as a service: runtimes and languages such as Go, Rust or Python, command line tools such as Git, GitHub CLI, jq or DDEV, and desktop apps such as Visual Studio Code, TablePlus, Postman or Docker Desktop. You do not start or stop them, you install, open, update and remove them.

Where to find it

  • What is on this Mac: Services page, view Installed, groups Runtimes, Tools, Apps and AI CLIs.
  • What you can add: view Discover, chips Runtimes, Tools or Apps.
  • What has an update: view Updates, see Updates.

How to do it

  1. Open Services › Discover and choose the Apps chip.
  2. Find the app, with the search field for example.
  3. Click Install. The card shows a progress bar and the latest line of output. Cancel stops the install.
  4. Once it is done, the app is listed under Installed in the Apps group. For command line tools the card confirms "Ready: … works in a new terminal window."

A tool's card

Part Content
Name Logo, name and the tool's own pricing model: Open Source, Free, Freemium or Paid. That says nothing about WebDonkey, only about the tool.
State Not installed, Installed, after the update check the version with up to date or old → new. Without an installable package it says "No package" with a pointer to the official site.
Description What the tool is for.
What it provides Chips such as Terminal commands: …, macOS app or Web UI on port …, after the install the source: via Homebrew, via npm, downloaded or installed elsewhere.
Main button Install, or Update when the update check has found a newer version.
Open starts an installed app, for command line tools it opens their website. Before the install it is greyed out. For tools without a package it says Open download page.
Manage versions only for languages with several versions side by side, such as Python or Ruby, see Install and choose versions.
Remove uninstalls the tool after the confirmation "Remove this?".

For apps that update themselves, such as Visual Studio Code or Google Chrome, the card says updates itself as soon as an update is due.

Runtimes with versions

WebDonkey manages Node.js, Composer and Hugo in versions. Their card shows the installed versions side by side, the active one with active, each with its version status. Clicking another version makes it, after a confirmation, the version for the terminal and new starts. Without an installed version the card shows Install, which leads to the versions, or System: … when there is a version outside WebDonkey. Manage versions opens the versions dialog, Remove uninstalls the runtime with every version.

Where a tool comes from

WebDonkey picks the right way per tool: apps through Homebrew Cask, command line tools through Homebrew formulae, some apps as the vendor's download. If Homebrew is missing, WebDonkey installs it itself. Under Discover, a note then offers Install Homebrew.

A tool you installed another way, with the vendor's installer, by drag and drop or with another package manager, is recognised by WebDonkey and shown as installed elsewhere. You can use it, but it is updated and removed where it came from. Remove is locked then.

What happens in the background

  • Installs keep running in the background, even when you leave the page.
  • If Homebrew would have to upgrade something already installed for an install, WebDonkey asks first, "Homebrew would upgrade something else too", and lists old → new. It only goes on after Upgrade and install.
  • After the install, WebDonkey checks whether a new terminal finds the command, and tells you.
  • WebDonkey fetches the logos from the vendor and keeps them locally.

Free and Premium

Apps and tools are entirely part of Free. They do not count towards Free's six services and are not part of the system check.

Troubleshooting

What you see Why What to do
"Installed, but … could not be found for the terminal." The terminal does not know the new command yet. Open a new terminal window. If it is still missing, run the rescan under Settings.
The install fails The card names the cause, such as no network, a full disk, an older macOS or missing Command Line Tools. Follow the cause and click Install again. Details shows the installer's message.
"… is already on this Mac in another version, installed without Homebrew." WebDonkey does not overwrite the app. Update the app through its own updater, or move it to the Trash and install it here.
"nvm is a shell function and has to be loaded when the shell starts" Some tools such as nvm are not a command but a shell function. Turn on Tools in the terminal in Settings, or add the lines from brew info nvm to your ~/.zshrc.
Homebrew is busy with another installation Homebrew handles one install at a time. Wait until it is finished, then click Install again.

See also

AI CLIs Free

AI CLIs lists coding assistants for the terminal: Claude Code, Gemini CLI, OpenAI Codex CLI, GitHub Copilot CLI, OpenCode, Qwen Code, Aider, Crush, Goose, llm and Cursor CLI. WebDonkey installs them like other tools, checks for updates and removes them again. You sign in with their provider inside the CLI itself.

Where to find it

  • Installed AI CLIs: Services page, view Installed, group AI CLIs.
  • More AI CLIs: view Discover, chip AI CLIs.

How to do it

  1. Open Services and switch to Discover.
  2. Choose the AI CLIs chip.
  3. Click Install on the CLI you want. The card shows the progress, Cancel stops it.
  4. Once it is done, the card confirms "Ready: claude works in a new terminal window."
  5. Open a new terminal and start the CLI with its command, such as claude, gemini, codex or aider.

Managing

An AI CLI's card has the same parts as every tool card:

  • Update appears when the update check has found a newer version. Check again above the group checks once more.
  • Open opens the CLI's website once it is installed.
  • Remove uninstalls the CLI after a confirmation.
  • The chips show the command (Terminal commands: …) and the source, such as via Homebrew.

What happens in the background

  • WebDonkey installs the AI CLIs through Homebrew, as a cask or as a formula. If Homebrew is missing, WebDonkey sets it up first.
  • If you installed a CLI through npm earlier, Claude Code or Gemini CLI for example, WebDonkey recognises that copy and can update and remove it.

Free and Premium

AI CLIs are entirely part of Free and do not count towards Free's six services. Whether the CLI itself costs money is shown by the chip on its card, such as Paid or Open Source.

Troubleshooting

What you see Why What to do
npm may not write to its global folder An earlier npm copy lives in a folder that belongs to root or another account. Give the folder named in Details to your user account, or remove the old copy there and install it here again.
"Installed, but … could not be found for the terminal." The terminal does not know the command yet. Open a new terminal window, otherwise run the rescan under Settings.
The CLI says you are not signed in The sign-in with the provider is missing. Start the CLI in the terminal and follow its sign-in.

See also

The WebDonkey apps Free

On the Services page, WebDonkey, the WebDonkey Editor and WebDonkey Pages have a group of their own called WebDonkey. You see which version is installed and whether the app is running, update it with one click and download an app that is missing. That way you keep all three up to date in one place.

Where to find it

Sidebar Local › Services:

  • Installed: the WebDonkey group right below Running, with every installed app.
  • Updates: the apps with a newer version, always at the very top.
  • Discover: an app that is missing on this Mac, at the very top under All and behind the WebDonkey chip.

An app's row

Part Content
Name Logo and name. WebDonkey itself carries This app.
State running · … or installed · … with the version, old → new when an update is waiting, otherwise Not installed.
Description What the app does.
Main button Update when a newer version is offered, Download when the app is missing.
Open starts the app. For WebDonkey itself the button is greyed out.

How to do it

Update the WebDonkey Editor or WebDonkey Pages

  1. Open Services › Updates or Installed.
  2. Click Update on the app.
  3. If the update channel announces a change to the terms, the terms question comes first (see below).
  4. If the app is running, WebDonkey asks "Update …?": for the update the app is quit and then opened again. Confirm with Update.
  5. The row shows the progress and then "Updated to …".

If the running app does not quit within a minute, because it asks something first for example, the update is still installed. The new version then starts the next time you open the app, and the row says so.

Update WebDonkey itself

Click Update in WebDonkey's row. WebDonkey's update dialog opens with the release notes, see Updates. If there is nothing new, the row says "WebDonkey is up to date."

Get a missing app

Click Download on the app under Discover. The browser opens the download page in the WebDonkey shop.

The terms question before an update

If the update channel of the Editor or Pages announces a change to the terms, WebDonkey asks before the update, just like the apps themselves do:

  • The dialog Our terms change on … says what changes and links Read the new terms.
  • Below it you see when your subscription ends if you do not agree, and "Until then the current version applies. You get the update either way."
  • Agree and update sends your consent and updates.
  • Only update updates without agreeing.
  • Cancel closes the dialog without updating.

For a company account it only says "Your company agrees to the new terms in the customer account." with Open customer account and Continue updating. If the consent does not reach the shop, the row says "Consent not transmitted, you can agree in your customer account." The update runs in any case.

What happens in the background

  • WebDonkey reads on the Mac which apps are installed and running.
  • WebDonkey asks the update channel of the Editor and Pages when you open the page, and after that at most every ten minutes. Without internet, the request waits.
  • WebDonkey downloads the Editor's and Pages' update from the shop, verifies it with that app's update key and replaces the program.

Free and Premium

The group is entirely part of Free.

Troubleshooting

What you see Why What to do
"Update failed: …" Downloading or verifying the update failed. Check the internet connection and click Update again.
No app shows an update although a new version is out The update channel was already asked within the last ten minutes. Click Check again under Updates.
The app is missing from the group It is not installed. Click Download under Discover.

See also

Uninstall a service Free

When you no longer need a service or a runtime, you remove it with every version in one step. WebDonkey first stops whatever of it is running, takes every installed version off the Mac, Homebrew's included, and names the data folders. It only deletes the data when you explicitly tick that.

Where to find it

Services page, view Installed:

  • for a service such as MySQL or Redis: Remove (trash icon) on the far right of its row,
  • for a runtime such as Node.js or Composer: Remove on its card under Runtimes or Tools.

To remove a single version instead, use the versions dialog, see Install and choose versions.

How to do it

  1. Click Remove in the service's row.
  2. The Uninstall …? dialog names every version that will be removed, such as "MySQL is removed from this Mac with all its versions: 9.1.0, 8.4.3. Whatever of it is running is stopped first."
  3. Leave Also delete the data of … unticked if you want to keep the data. The data folders are listed below it with their full path.
  4. Click Uninstall. The button shows Removing… until everything is gone.

Afterwards the service disappears from Installed and is listed under Discover again. The bell reports whether everything worked.

Fields and options

Option Meaning
Also delete the data of … Off (default): the data is kept and a new installation finds it again. On: the folders listed are deleted for good and cannot be restored. The checkbox only appears when there are data folders.

Data folders are the service's folder under ~/Library/Application Support/WebDonkey/data/ and what was set aside there, such as PostgreSQL data that was set aside.

What happens in the background

  • First WebDonkey stops every running version of the service. That way a database never loses files while it writes.
  • Then it removes one installed version after the other. It removes versions from Homebrew with brew uninstall, even if programs outside WebDonkey use them.
  • Sites that need the service only run again after a new installation.
  • Only with the checkbox ticked does it then delete the data folders.

Free and Premium

Uninstalling is part of Free.

Troubleshooting

What you see Why What to do
"Nothing of … was installed through WebDonkey that could be removed here." The service comes from another source, the system for example. Uninstall is locked. Remove it where it came from.
An error message in the dialog A version or a folder could not be removed. Whatever was removed before is gone. Read the message and open the dialog again, it names what is left.

See also

System check Free

The System check tests every running service at protocol level, not just whether its process exists. A service can run as a process and still not answer. That is exactly what the check reveals, together with each service's response time.

Where to find it

Services page, view Installed, the System check box at the very bottom ("Protocol checks for the running services (apps & CLIs aren’t checked)").

How to do it

  1. Open Services and scroll to the end of the Installed view.
  2. Click Run check. The button shows Checking….
  3. Each line then shows the service with a green check or a red cross, a detail such as "HTTP 200" or "TCP 127.0.0.1:5672 ok", and the response time in milliseconds.
  4. The summary at the top says either that all active services are healthy or how many are failing, such as "1 of 5 active services failing".

The list always includes the front proxy and every service WebDonkey knows. Stopped and uninstalled services are listed neutrally as stopped and are not checked. Adminer only appears while it runs.

What is checked

Service Check
MySQL, MariaDB, PostgreSQL a real SELECT 1 query
Redis PING, expecting PONG
Memcached version, expecting VERSION
Meilisearch, MinIO, OpenSearch, Mailpit, Ollama, Adminer an HTTP request to their endpoint, such as /health for Meilisearch
PHP-FPM whether a PHP-FPM socket is present
nginx, Caddy, Apache, MongoDB, RabbitMQ, front proxy whether their port accepts connections

Each check waits three seconds at most. The system check does not test apps, tools or AI CLIs.

Free and Premium

The system check is part of Free.

Troubleshooting

What you see Why What to do
A red cross with "timeout" The service does not answer within three seconds. Restart it in its row and run the check again.
A red cross with an error message The service runs but refuses the connection, after a bad configuration for example. Look at what it reports with Logs in its row.
A service is stopped It is not running or not installed. Start it in its row, or install it under Discover.

See also

Active services Free & Premium

On the right of the top bar, WebDonkey shows on every page how many services are running. Clicking it opens the Active services menu with everything that runs right now: the services, the processes of sites and the front proxy. From there you restart or stop something without leaving the page.

Where to find it

  • Top bar, on the right: the status with a dot, such as "3/7 services running". When nothing runs it says "All services stopped", when a service has crashed "A service has crashed". While something runs and nothing has crashed, the dot glows.
  • Services page, view Installed: the same processes, without the services, are listed under Also running.

How to do it

  1. Click the status in the top bar.
  2. The Active services menu opens below it.
  3. Click Restart or Stop in a row.
  4. Manage services at the bottom opens the Services page in the Installed view.

A click next to the menu or the Esc key closes it. When nothing runs, it says "Nothing is running right now."

What the menu shows

Every row names the entry, its kind and how long it has been running. The order:

  1. Front proxy ("Routes every site"), while it runs.
  2. Crashed services, so you see them right away.
  3. The running services, by name and version.
  4. The processes of sites with a serve command ("Site process").

If you stop the front proxy, no site is reachable until it runs again. The tooltip of Stop says so in its row.

Start all, Stop all, Restart

On the left of the top bar, three buttons act on all services at once:

  • Start all brings back the services you used last, together with the front proxy. If PHP is among them, it also starts the PHP versions your sites need. It does not start everything that is installed.
  • Stop all stops every service and the front proxy. WebDonkey still remembers what you used last for the next start.
  • Restart stops everything and starts it again.

More under Autostart and lifecycle.

Free and Premium

On Free, up to six services run at the same time. The Services page shows how many there are right now, such as "4/6 services running". The front proxy, site processes and Adminer do not count. Once the limit is reached, further starts are locked. If Start all would bring back more than six services, WebDonkey asks with Choose your services which ones should run. See Services.

Troubleshooting

What you see Why What to do
"A service has crashed" A service ended unexpectedly. It is at the top of the menu. Restart in its row. If that does not help, open its Logs on the Services page.
No site is reachable The front proxy is stopped. Click Start all, or open a site with Open in browser.

See also

Autostart and lifecycle Free

WebDonkey manages the whole lifecycle of your services: on start it brings back what you used last, on quit it stops everything cleanly, and after a crash it cleans up leftover processes. You do not need to set anything up for this.

Where to find it

The lifecycle runs by itself. What is running right now is shown in the Active services menu and on the Services page.

When the app starts

  1. If there is no site yet, WebDonkey starts nothing.
  2. Otherwise it starts the front proxy and syncs the sites' name resolution.
  3. Then it brings back the services that ran last time: every service you started and have not stopped individually since. If PHP is among them, it also starts the PHP versions your sites need.
  4. Finally it starts the processes of all enabled sites with a serve command, one after another.

On the very first start nothing has been remembered yet, so nothing starts. Whatever you start then, WebDonkey remembers for next time. Stop all does not count as stopping individually, so the services come back on the next start. If you stop a service in its row, it stays off on the next start.

On Free, WebDonkey starts nothing when the app starts if what it remembered would be more than six services. If you then click Start all, it asks with Choose your services which ones should run.

When the app quits

  • WebDonkey stops every service and the front proxy. Nothing of WebDonkey keeps running in the background.
  • Open terminals inside containers are closed, running downloads of the SFTP file manager are stopped.
  • If an operation is still running on a server, such as a restore, a sync or a backup, WebDonkey asks "Quit WebDonkey?" and names the number of operations. Quit quits anyway, Cancel keeps the app open.

This applies to ⌘Q, Quit from the Dock and closing the window.

After a crash

After a crash or a force quit, WebDonkey finds its own leftover processes on the next start and stops them deliberately. It never touches foreign installations, such as your own Docker or Homebrew services outside WebDonkey. Every service runs in a process group of its own, so its child processes are stopped along with it, the Erlang VM of RabbitMQ for example.

Data folders and versions

  • The services' data lives under ~/Library/Application Support/WebDonkey/data/.
  • Databases keep a data folder per version series. When you switch versions, both series keep their data.
  • PostgreSQL has a data cluster that another major version cannot open. The service's row then names the version needed. Your databases stay unchanged. To keep them, install the old version again, back up the databases as a dump and load them into the new one.
  • Set old data aside moves the data/postgres folder to data/postgres-pg<version>-<date>. Nothing is deleted and other services are not affected. PostgreSQL then starts with a new, empty cluster.

Troubleshooting

What you see Why What to do
Nothing runs after the start There is no site, or you stopped the services individually last time. Start the services under Services, and they come back on the next start.
On Free nothing starts when the app starts What was remembered would be more than six services. Click Start all and choose the six.
PostgreSQL does not start after a version switch The new major version cannot open the old cluster. See above: install the old version again or set the cluster aside.

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