DOCUMENTATION

Build the project.
Know where to look.

Practical guides for getting a local site running and finding the useful clue when it does not.

Release-aware documentationThe interface and available automation evolve between releases. The download page always shows the exact version you receive.

01 · START

Install and first launch

  1. Download

    Choose a published build on the downloads page, then unpack the ZIP archive.

  2. Move

    Place ServerMaster.app in Applications so it has a stable home.

  3. Approve once

    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.

  4. Check dependencies

    Open Dependencies and review the tools needed by the server engine you plan to use.

Download from the source.

Use the official ServerMaster GitHub release. Checksums are provided with published archives where available.

02 · PROFILE

Save the way a project runs

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.

PROJECT FOLDER+ENGINE+PORT→SAVED PROFILE
  1. Create

    Open Profiles and add a profile. Depending on your release, start empty or choose a template.

  2. Point

    Select the folder containing your project. For a static site, that is usually the folder with index.html.

  3. Choose

    Select an engine suited to the project and pick a free local port such as 8080.

  4. Run

    Return to Control, start the profile, and open its local address.

03 · STATIC

Serve HTML, CSS, and JavaScript

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.

Done whenYour page opens at the local address shown by ServerMaster, and refreshing a nested route behaves as expected.

04 · PHP

Run a PHP project

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.

  • Set Root to the folder containing the public entry point.
  • Choose the PHP version used by this profile.
  • Use Apache when the project relies on its own .htaccess rules.
  • Start the profile and read the server log if PHP exits or returns an error.
Seeing PHP source in the browser?

The current engine is serving the file as text. Switch the profile to a PHP engine.

05 · CMS

Joomla, WordPress, Drupal, and more

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.

Joomla & WordPress

Use a PHP profile and create a database. Apache is a natural fit when the project uses .htaccess.

Drupal

Composer projects commonly expose the web subfolder. Point Root there.

Laravel & Symfony

Point Root to the public web directory and keep credentials in the project's environment configuration.

06 · DATABASE

Keep local data close

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.

Connection shapehost: 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

Use local HTTPS when the project needs it

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.

Keep it local.

Development certificates and servers are for local work. Review configuration before exposing any service to another network.

08 · PORTS

When a port is already busy

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

Follow the first useful clue

01

Read the profile log

Start with the first clear error, not the final exit code.

02

Check the port

Confirm the address is free and the expected process is listening.

03

Check dependencies

Make sure the selected engine and runtime exist.

04

Test the address

Use the available HTTP check, then compare its result with the server log.

10 · RELEASES

Versions and platform support

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.

  • macOS application downloads list the required macOS version and supported architecture.
  • The shared Swift CLI targets macOS and Linux, with glibc and musl builds planned.
  • The Windows interface will have its own release version and requirements.
  • Older published builds remain available for rollback.

Open the release catalog