What is inside Server by Zaweba: components and licences
Help, Components and licences in Server by Zaweba lists every bundled part with its version and licence, each download checked against its SHA-256.
Bundled software comes with licences and version numbers, and Server by Zaweba keeps both in one window. Help, Components and licences lists every component the app ships with: Apache, mod_fcgid, MariaDB, the four PHP versions, Adminer and Mailpit, each with its version and its licence. Every one of those downloads was checked against its published SHA-256 before it was included.
What each component does
Apache 2.4 is the web server. It answers requests for your sites and runs as a console program with a configuration the app generates and tests before using. mod_fcgid is the Apache module that hands PHP requests to PHP. Each PHP version has its own pool of php-cgi processes, which is how different sites run different PHP versions at the same time.
MariaDB 11.8 is the database server, compatible with the MySQL style of database most PHP software expects. PHP comes in four versions, 5.6, 7.4, 8.2 and 8.3, each with its own php.ini. The first two are end of life and are included for older projects you need to keep running locally.
Adminer is a database manager in a single file, opened already logged in from the Databases page, a site's Database button or Tools, Adminer. Mailpit is the mail catcher: every php.ini points PHP's mail settings at it, so mail sent by your sites lands on a local web page instead of reaching anyone.
Why the versions matter
When a project's documentation says it needs a particular PHP or database version, this window is the quickest way to check what you have. It also helps when you report a problem to a framework or plugin author, who will usually ask which versions you were running. The control panel shows the components' versions too, but the Components window puts them all in one list with their licences.
Why the licences are listed
Every part of the bundle is open source software made by other projects, each under its own licence. Listing them gives those projects their due. It also tells you exactly what you are running, which matters if you work somewhere that asks staff to check the software on their machines.
The SHA-256 checks
A SHA-256 checksum is a fingerprint of a file. Projects publish the checksum alongside their downloads so anyone can confirm that the file they received is the one the project released, unchanged. Each component in Server by Zaweba was checked against its project's published checksum. It is a basic step, but it guards against a damaged or tampered download ending up in the app.
Where the components live
The components sit in their own folder beside the program, separate from your data and your sites. That separation is part of what makes the app portable: the configuration paths are re-applied on every start, so the folder can be moved, and nothing is installed in Windows except what you allow. Settings lists the folders if you want to look inside.
phpMyAdmin is not among the components. Adminer covers the same everyday jobs of browsing tables, running queries and editing rows, in a single file.
On Mac and Linux
The separate macOS and Linux build has a different set of parts, so its list differs: Caddy with PHP-FPM instead of Apache, PHP 8.2 and 8.3, MariaDB or MySQL 8.4 depending on the system, plus Mailpit and Adminer. Those are downloaded on first use and checked by SHA-256 in the same way.
