Framework
walkor/webman avatar
walkor/webman

webman: a Chinese landing page, a container that ships nothing, and three releases in one afternoon

Probably the fastest PHP web framework in the world.

2,701 stars251 forksPHPMIT

At a glance

What is it?
A PHP framework built on workerman, with start.php at the root and Windows-specific startup files beside it. The README is a Chinese link page with no install command and no code, the Dockerfile copies no application and installs no dependencies, and three patch tags shipped on a single afternoon in February 2026.
Who is it for?
webman is worth evaluating if you already know workerman, because the repository gives you the runtime entry point, a compose file and a Windows path, and nothing else. Decide on that basis.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 23 days ago.
What is it written in?
Mainly PHP, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • walkor/webman2,701 ★ · +10
Star history
Repository2026-10-042026-11-15
walkor/webman2.7k2.7k

10 Stars in the last 42 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The README is a Chinese landing page that links out six times

The front page of the repository is written in Chinese and is styled as an HTML block rather than prose. It opens with an `h1` reading webman and one sentence describing the project as an ultra-high-performance PHP framework developed on the basis of workerman.

Everything after that is a list of seven links under a heading meaning Learn. Each label is bilingual, Chinese then English, and every target leaves the repository:

code
主页 / Home page          https://www.workerman.net/webman
文档 / Document           https://webman.workerman.net
安装 / Install            https://www.workerman.net/doc/webman/install.html
问答 / Questions          https://www.workerman.net/questions
市场 / Apps               https://www.workerman.net/apps
赞助 / Sponsors           https://www.workerman.net/sponsor
致谢 / Thanks             https://www.workerman.net/doc/webman/thanks.html

The only body text in the file is the license sentence, which says in English that the webman is open-sourced software licensed under the MIT. There is no install command, no configuration sample, no code example and no feature description anywhere in it.

The metadata Homepage field points somewhere different again, at `https://webman.workerman.net/`, while the Home page link in the README goes to `https://www.workerman.net/webman`. Two addresses for one project, neither of them this repository.

Two floated columns of the README are sponsorship blocks

After the link list the page splits into two floated side-by-side blocks, and neither of them is about the framework.

The first is headed 赞助商, Sponsors, and splits further into 特别赞助, a special sponsor, and 铂金赞助, platinum sponsors. Three commercial domains are linked, and every one of them carries a source parameter in its query string: `https://www.crmeb.com/?form=workerman`, `https://www.fadetask.com/?from=workerman`, and `https://www.yilianyun.net/?from=workerman`.

The second block is headed 请作者喝咖啡, asking the reader to buy the author a coffee, and contains a bolded sentence saying that if webman has been helpful to you, donations are welcome.

Each sponsor anchor in the file is empty, holding a link and nothing else, which means the sponsor marks are images whose sources are not carried in the text. So a reader arriving at this page sees two columns of marks and a request for money before reaching the one sentence of real content, the license line at the bottom. That is a reasonable thing for a project page to be, and it does mean the repository's front page is not a place to look for how the software works.

The repository gives you an entry point and an external documentation URL

What the tree does contain is the shape of a runtime installation. Fourteen top-level entries are listed, and among them are `start.php`, which is the script the container runs, a `composer.json`, and directories named `app/`, `config/`, `public/`, `runtime/` and `support/`. Two of the entries exist purely for one platform: `windows.bat` and `windows.php`.

What is not there is any instruction for getting from that tree to a running process. The Install link resolves to `https://www.workerman.net/doc/webman/install.html`, a documentation page on the workerman domain, and the Document link resolves to `https://webman.workerman.net`. Neither is in this repository.

That split has a practical effect. The parts a reader needs in order to reproduce a working setup, the PHP version, the required extensions, the composer step, and what `start.php` expects to find around it, all live off-site. The repository supplies the files but not the procedure, and there is no second file in the tree that fills the gap. `CHANGELOG.md`, `CONTRIBUTING.md` and a test directory are also absent from the listing, along with any CI configuration directory.

The container copies no application and installs no dependencies

The Dockerfile is short and stops before it does anything with the project:

dockerfile
FROM php:8.3.22-cli-alpine

RUN mv "$PHP_INI_DIR/php.ini-production" "$PHP_INI_DIR/php.ini"

The rest installs two extensions, enables opcache and pcntl, then ends with `RUN mkdir -p /app` and `WORKDIR /app`. There is no `COPY` of any project file, no `composer install`, and no `CMD` or `ENTRYPOINT`. The image contains a PHP runtime and an empty working directory.

The compose file supplies both gaps from the host side:

yaml
services:
  webman:
    build: .
    container_name: docker-webman
    restart: unless-stopped
    volumes:
      - "./:/app"
    ports:
      - "8787:8787"
    command: ["php", "start.php", "start" ]

The bind mount puts the working tree where the image's empty `/app` was, and the command is the only start instruction in either file. The dependencies declared in `composer.json` are never fetched by anything here, so they have to be installed on the host before the tree is mounted, or added as a build step. Running the image on its own, without the mount and without a command, starts nothing.

The apk cache cleanup is joined onto the previous command

One line in the Dockerfile does not do what its shape suggests. The tail of the extension setup reads:

dockerfile
RUN docker-php-ext-enable opcache pcntl
RUN docker-php-source delete \
    rm -rf /var/cache/apk/*

The backslash continues the line, so these are not two commands. They are one command, `docker-php-source delete`, with `rm -rf /var/cache/apk/*` arriving as its arguments rather than being handed to a shell. No separate cleanup runs, and the paths meant for the cache removal are passed to the source-delete step instead.

Two other choices in the same file are worth naming. The apk repository is rewritten from `dl-cdn.alpinelinux.org` to `mirrors.aliyun.com`, which fixes the image to a mirror region for anyone building outside it. And the extension install puts its parallel flag in the middle of the argument list, `docker-php-ext-install pdo pdo_mysql -j$(nproc) pcntl`, so `pdo` and `pdo_mysql` are built in parallel and `pcntl` follows.

The base image is pinned to an exact patch, `php:8.3.22-cli-alpine`, and the production ini is moved rather than copied, so the php.ini-production template is gone from the image once that layer is built.

Windows has two dedicated files and the port is workerman's default

Most PHP process managers assume POSIX signals. This repository carries two files whose only job is the other platform: `windows.bat` and `windows.php`, sitting at the root next to `start.php`. Which one is the normal path and which is the fallback is not stated anywhere in the tree, so anyone deploying on Windows has to determine that from the scripts themselves.

The container publishes `8787:8787`, which is workerman's default HTTP port rather than a port this project chose, and the start command passes a third argument, `start`, to the entry script:

code
php start.php start

So `start.php` takes a mode as its first argument, and `start` selects one. The compose file defines no `environment` block, no health check and no dependency, and it is a single service with no database and no reverse proxy alongside it. It also still carries the `version: "3"` key at the top, which current Compose releases report as obsolete, so the file announces a schema version that the tool no longer needs.

Nothing in either file records which PHP extensions webman requires. The image installs pdo, pdo_mysql and pcntl, which is a reasonable guess at the needs of a database-backed framework, but the confirmation lives on the external install page rather than in the repository.

Three patch tags on one afternoon, then seven weeks without a release

The three most recent releases are all dated 2026-02-24: v2.2.1 at 06:58 UTC, v2.2.2 at 12:20 UTC, and v2.2.3 at 13:31 UTC. Three patch-level tags inside roughly six and a half hours is a fast correction pattern, and it is worth noting because it is the opposite of the cadence the version numbers suggest. Whatever changed between those tags, it was adjusted three times in one working day.

The dates after that are quieter. The last push to the default branch `master` was 2026-04-15, about seven weeks after the newest tag, and as of 2026-10-04 the branch has seen no push for roughly five and a half months. The repository is not archived, and its license is MIT with a `LICENSE` file at the root matching the sentence on the front page.

Two gaps in the listing round out the picture. None of the fourteen top-level entries is a test directory, and none is a CI configuration directory. For a framework whose selling point is a process manager running a long-lived worker, that means the visible repository contains no way to confirm a change did not break a stream, and no record of how the three same-day patch tags were validated.

Editorial conclusion

webman is worth evaluating if you already know workerman, because the repository gives you the runtime entry point, a compose file and a Windows path, and nothing else. Decide on that basis. Fetch the install and documentation pages named in the README before writing any code, since the repository itself contains no command, no configuration sample and no example. If you adopt the container, expect to add a dependency install step and an application copy, because neither Dockerfile nor compose provides them. And check the branch dates against your own plans, since the newest release tag is v2.2.3 from 2026-02-24 and the last push to master was 2026-04-15.

Frequently asked questions

What is webman and what is it built on?

webman is a PHP framework built on workerman. The repository description calls it probably the fastest PHP web framework in the world, and the Chinese README describes it as an ultra-high-performance PHP framework developed on the basis of workerman.

How do I install webman?

The repository contains no install command. Its README links to the install page at https://www.workerman.net/doc/webman/install.html and the documentation at https://webman.workerman.net, both of which are outside this repository.

What license is webman released under?

MIT. The README states that the webman is open-sourced software licensed under the MIT, and a LICENSE file sits at the repository root.

How do I run webman with Docker?

The compose file builds the image, bind mounts the working tree into /app, publishes port 8787, and runs php start.php start. The Dockerfile itself copies no application files, installs no composer dependencies, and defines no CMD or ENTRYPOINT.

Does webman run on Windows?

The repository carries windows.bat and windows.php at its root alongside start.php, which are the Windows-specific startup files. The README does not state which one is the normal path or how the modes differ.

Official sources

  1. License: MIT
  2. Project website
  3. README
  4. Releases
  5. walkor/webman on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/walkor-webman.svg)](https://hysenlabs.com/projects/walkor-webman)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/walkor-webman.svg)](https://hysenlabs.com/projects/walkor-webman)

Was this useful?