Joomla & WordPress
Use a PHP profile and create a database. Apache is a natural fit when the project uses .htaccess.
DOCUMENTATION
Practical guides for getting a local site running and finding the useful clue when it does not.
01 · START
Choose a published build on the downloads page, then unpack the ZIP archive.
Place ServerMaster.app in Applications so it has a stable home.
The current build is unsigned. Try to open it, then use System Settings → Privacy & Security → Open Anyway. Follow the exact instructions in its release notes.
Open Dependencies and review the tools needed by the server engine you plan to use.
Use the official ServerMaster GitHub release. Checksums are provided with published archives where available.
02 · PROFILE
A profile connects a project folder to an engine, a port, and its runtime settings. That turns a launch recipe into something you can reuse.
Open Profiles and add a profile. Depending on your release, start empty or choose a template.
Select the folder containing your project. For a static site, that is usually the folder with index.html.
Select an engine suited to the project and pick a free local port such as 8080.
Return to Control, start the profile, and open its local address.
03 · STATIC
Point a profile at the folder that contains index.html. A Node http-server, Python HTTP server, or Nginx profile can serve static files. If a single-page app owns its routes, enable the SPA fallback where the selected engine supports it.
04 · PHP
Choose a PHP-capable engine. The PHP built-in server is useful for a simple project; Nginx or Apache with PHP-FPM provides a configuration closer to a full web stack.
.htaccess rules.The current engine is serving the file as text. Switch the profile to a PHP engine.
05 · CMS
Most CMS projects follow the same shape: project files, a PHP server profile, and a database. Templates can fill sensible defaults; availability and assisted downloads depend on the release.
Use a PHP profile and create a database. Apache is a natural fit when the project uses .htaccess.
Composer projects commonly expose the web subfolder. Point Root there.
Point Root to the public web directory and keep credentials in the project's environment configuration.
06 · DATABASE
Start ServerMaster's managed database, create a database and user, then enter those connection details in your application or installer. Use the exact host and port shown in the app.
host: 127.0.0.1
port: [shown in ServerMaster]
database: [your database]
user: [your user]Database backups are useful only when the managed database is running and included in the selected snapshot workflow.
07 · HTTPS
HTTPS support depends on the engine. Generate a self-signed certificate for quick testing, or use mkcert for a certificate your local browser can trust after its local authority is installed.
Development certificates and servers are for local work. Review configuration before exposing any service to another network.
08 · PORTS
Open Ports to see which local process owns the address you want. Stop a process only when you recognize it, or choose another port in the profile. Ports below 1024 can require macOS authorization.
09 · TROUBLESHOOT
Start with the first clear error, not the final exit code.
Confirm the address is free and the expected process is listening.
Make sure the selected engine and runtime exist.
Use the available HTTP check, then compare its result with the server log.
10 · RELEASES
ServerMaster is developed as one repository with platform-specific deliverables. Published source states are identified by Git tags; compiled archives remain attached to GitHub Releases.
11 · BUILD LABELS
The application version, such as 2.1.0, identifies the ServerMaster release. Its separate build label describes the machine and tools used to compile that particular binary.
arm.m27.3b.x27.3b1.uni| Part | Meaning |
|---|---|
arm | Compiled on an Apple Silicon Mac. This describes the build machine. |
m27.3b | The build machine runs a macOS 27.3 beta. m identifies macOS and the trailing b marks the beta channel. A stable system uses m27.3. |
x27.3b1 | Xcode 27.3 beta 1. x identifies Xcode; b1 identifies its beta iteration. A stable Xcode uses x27.3. |
uni | A Universal Mac binary with both arm64 and x86_64 architectures, for Apple Silicon and Intel. |
A build-host version does not set the oldest supported macOS. Check the minimum macOS and architecture shown for the actual download. This example explains the label format; it does not announce an available download.
Starting with macOS 2.1.0, each release includes its build environment and test-machine information in the GitHub Release notes. For example:
Built on: Mac17,3; macOS 26C5035r; Xcode 27C5020n. Target: Universal. Tested on the build machine.
The model identifier names the build machine; the macOS and Xcode codes identify the exact system and toolchain builds. Testing on the build machine does not imply testing on every supported Mac.
arm.27.0.b6.uni| Part | Meaning |
|---|---|
arm | Compiled on an Apple Silicon Mac; this describes the build machine. |
27.0 | The macOS version on the build machine. This older format does not record the macOS beta channel. |
b6 | Xcode beta 6. It does not mean macOS beta 6; the exact Xcode version is not encoded in this older format. |
uni | Universal output for Apple Silicon and Intel. Other legacy targets include arm for Apple Silicon only and int for Intel only. |
Legacy identifies the older naming format, not the support status of the application. Published releases keep their original labels. The current format separates the macOS and Xcode versions and their beta channels explicitly.