Self-hosted service
pH7Software/pH7-Social-Dating-CMS avatar
pH7Software/pH7-Social-Dating-CMS

pH7Builder ships 19.3.1 while its default branch is still 18.x

Self-hosted, open-source PHP 8.2+ software for building white-label dating sites, matchmaking communities, and social networks. Own your code, hosting, database, and member data.

1,076 stars617 forksPHPMIT

At a glance

What is it?
A self-hosted PHP dating and social network builder, MIT licensed, requiring PHP 8.2 and MySQL 8.0 with MariaDB explicitly unsupported. The Docker compose path is documented for evaluation only, its volumes are snapshotted and destroyed by one flag, and the default branch does not match the release line.
Who is it for?
pH7Builder fits an operator who wants a dating or community site on infrastructure they control, and the README is unusually candid about the conditions. Three things to settle before you commit.
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 1 day 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

  • pH7Software/pH7-Social-Dating-CMS1,076 ★ · +20
Star history
Repository2026-09-112026-11-15
pH7Software/pH7-Social-Dating-CMS1.1k1.1k

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

Editorial analysis

The default branch is 18.x and the newest release is 19.3.1

The first oddity worth noticing is administrative rather than technical. The repository's default branch is `18.x`, while the release feed shows 19.2.0 on 2026-09-12, 19.3.0 on 2026-09-22 and 19.3.1 the same afternoon, and the product was renamed from pH7CMS to pH7Builder along the way. That means a plain clone of the default branch is not the current release, so anyone who clones first and reads the README second is working from a line one major version behind. The production instructions compensate for it by being tag-specific: the download commands reference v19.3.1 by name, and the Composer command pins `ph7software/ph7builder:19.3.1`. The last push to the repository matches the newest release. Treat the branch name as legacy and install by tag.

MariaDB is explicitly out, which removes most cheap hosts

The requirement is MySQL 8.0 or newer with `utf8mb4` support, and the text is direct about the alternative: older MySQL releases and MariaDB are not verified or supported for this release. That single line decides where the software can run. A large share of inexpensive shared hosting ships MariaDB, so the practical consequence is that a cheap host is ruled out until you confirm its database engine. PHP has a similar floor at 8.2 or newer, with an explicit extension list including `curl`, `dom`, `exif`, `fileinfo`, GD with FreeType and WebP, `hash`, `iconv`, `json`, `mbstring`, `openssl`, `pdo_mysql`, `simplexml`, `xmlwriter`, `xml`, `zip` and `zlib`. On the web server side it is Apache with URL rewriting, or nginx with equivalent routing and protected path rules.

The installer refuses to import a schema until it has checked everything

What makes the requirements tractable is that the browser installer verifies rather than assumes. Before importing the schema it checks the runtime, the extensions, writable paths, the MySQL version and the database connection, and fails rather than proceeding on a broken prerequisite. The production path is to set the required writable directories, configure the web server, generate an installer access token from the deployed directory, and only then open `/_install/`. The token step matters: the installer is not reachable to anyone who can merely load the URL. Deployment is estimated at 20 to 30 minutes with a ready server, and the estimate explicitly excludes DNS, TLS certificate issuance and mail provider approval, which in practice is where a first deployment loses most of its afternoon.

SMTP credentials live in the environment, not in the database

The mail requirement is unusual enough to call out. You need a server sendmail transport, or SMTP credentials supplied through the server environment as `PH7_MAILER_DSN`, and the reason is stated: the application does not store SMTP credentials in its admin form. That is a deliberate security decision with an operational price. A hosting panel where the only way to configure the app is clicking around an admin UI cannot receive mail at all, because there is nowhere to put the DSN. It also means rotating mail credentials is a deployment action rather than a settings action, and a misconfigured DSN produces silent or bouncing mail rather than a visible form error. Registrations, password resets and notifications all route through that transport, so test it before you invite anyone.

The compose path snapshots your code into a volume and can delete it

The Docker route is documented for development and evaluation, and the text says so directly. Four commands start it:

console
git clone https://github.com/pH7Software/pH7-Social-Dating-CMS.git
cd pH7-Social-Dating-CMS
docker compose up --build -d
docker compose exec php php _install/create-install-token.php

The token script prints a one-time value you paste into the installer at http://localhost:8080, where the database host is `db` and the database, username and password are all `ph7builder` on port `3306`. Then comes the trap. The checkout is snapshotted into a Docker volume, and to test changed source you run `docker compose down -v` before starting again. That refreshes the snapshot but permanently deletes the local application and database volumes. A flag that removes your data as the documented way to iterate is a development convenience, and it is the reason the same section says this is not a production deployment.

Compose puts nginx in front of PHP-FPM and gates startup on MySQL

The compose file has three services with a deliberate asymmetry in how they wait. The `db` service is `mysql:8.4` with database, user and password all `ph7builder`, a root password, and a healthcheck running `mysqladmin ping` every five seconds with twenty retries and a thirty second start period. The `php` service builds from the local `Dockerfile`, waits for `db` to be healthy, sets `PH7_CANONICAL_HOST` to `localhost:8080`, and mounts the `ph7builder-app` volume read-write. The `web` service is `nginx:1.28-alpine` publishing `127.0.0.1:8080:80`, mounting the same app volume read-only plus its own config, and depending on `php` with `condition: service_started`. So a database health gate sits in front of PHP but not nginx, which is the right shape when the frontend is static and only the PHP worker needs the schema.

The image build fails on a missing extension rather than at runtime

The Dockerfile is built to fail early. It takes a PHP version argument defaulting to 8.2, uses a `composer:2` stage to lift the binary, then builds on `php:8.2-fpm-bookworm` with the development libraries needed for image handling. GD is configured explicitly with FreeType, JPEG and WebP. After `composer install` with `--prefer-dist`, two inline PHP checks run: the first loops over fourteen extensions and exits 1 with a message naming the missing one, and the second reads `gd_info()` and exits if FreeType Support or WebP Support is absent. Then permissions are normalised with `find` across directories and files, with the install directory and the several data, config, backup, cache, log and temp paths given write access explicitly. A container that builds is a container whose extensions were checked at build time.

The tree is organised by access boundary, not by type

The top-level layout is unusual and worth learning before you install anything. Directories beginning with an underscore mark the sensitive zones: `_install/` for the installer, `_protected/` for configuration and data, `_repository/` and `_tools/` for internals, `_tests/` for tests. Everything else is public-facing: `static/`, `templates/`, `data/`, `index.php`, plus `robots.txt` and `humans.txt`. Two entries have no business in a normal PHP repository and hint at the intended audience. `llms.txt` is a machine-readable summary for language models, and `WebsiteChecker.php` sits at the root as a standalone tool. Quality tooling is declared in files rather than assumed, with `phpcs.xml.dist`, `phpstan.neon.dist`, `phpunit.xml.dist` and `.php-cs-fixer.dist.php` all present at the root next to `composer.json` and `composer.lock`. Two related files sit beside them. `sample.htaccess` holds the rewrite rules to copy into your own configuration, and `.htaccess` is the version shipped inside the package. A `service-worker.js` at the root is what enables the PWA support, and that feature only works when the site is served over HTTPS, which is why HTTPS appears in the production requirements. The documentation set is a directory rather than a wiki, with `docs/` holding the quick start, the upgrade guide and the launch checklist that the README links to as things to read before accepting real users. The last instruction worth repeating is that features depend on which modules you enable and which external services you configure, so a feature list on a marketing page is not the same as a feature you have switched on.

Editorial conclusion

pH7Builder fits an operator who wants a dating or community site on infrastructure they control, and the README is unusually candid about the conditions. Three things to settle before you commit. The support floor is PHP 8.2 and MySQL 8.0, with MariaDB stated as neither verified nor supported, so check what your host actually runs. The mail configuration is environment-only through `PH7_MAILER_DSN`, because the admin form deliberately will not store SMTP credentials, which means a deployment that cannot set environment variables has no working mail. And the two install paths are not interchangeable: the compose file is labelled for development and evaluation, its volume snapshot is destroyed by `docker compose down -v`, and production is meant to run the verified release ZIP. Complete the launch checklist before accepting real users or payments, and pin a tag rather than tracking the default branch, which is 18.x while the newest release is 19.3.1.

Frequently asked questions

What is pH7Builder and what does it include?

It is self-hosted PHP software for building white-label dating sites, matchmaking communities and social networks, formerly called pH7CMS. It covers member profiles, search and matchmaking, messaging and chat, membership groups and paid plans, moderation queues and abuse reporting, multilingual routes and themes, and a REST API module, all built as a modular MVC application on the project's own pH7Framework and PH7Tpl engine.

What are the server requirements for pH7Builder?

PHP 8.2 or newer with a long list of required extensions including GD with FreeType and WebP, MySQL 8.0 or newer with utf8mb4, and either Apache with URL rewriting or nginx with equivalent routing. MariaDB and older MySQL releases are stated as not verified or supported. HTTPS is required for production and FFmpeg only when local video processing is enabled.

How do you install pH7Builder in production?

Download the ZIP attached to a tagged release, verify it with the accompanying `.sha256` file using `sha256sum -c`, unzip it, set the required writable paths, configure the web server, generate an installer access token from the deployed directory, then open `/_install/`. Composer 2 is only needed for a source checkout, since the release ZIP ships with locked production dependencies.

How do you configure email for pH7Builder?

Either use a server sendmail transport or supply SMTP credentials through the server environment as `PH7_MAILER_DSN`. The application deliberately does not store SMTP credentials in its admin form, so mail configuration has to happen at the deployment level rather than in settings.

Is the Docker setup for pH7Builder a production option?

The README states the compose path is for development and evaluation, not a production deployment. It also snapshots your checkout into a Docker volume, and the documented way to pick up changed source is `docker compose down -v`, which permanently deletes the local application and database volumes.

Does pH7Builder require a Powered by link?

No. The project states there is no required public Powered by link under the MIT license, and that the only obligation is keeping the license notice with copies or substantial portions of the software.

Official sources

  1. License: MIT
  2. pH7Software/pH7-Social-Dating-CMS on GitHub
  3. Project website
  4. README
  5. Releases
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/ph7software-ph7-social-dating-cms.svg)](https://hysenlabs.com/projects/ph7software-ph7-social-dating-cms)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/ph7software-ph7-social-dating-cms.svg)](https://hysenlabs.com/projects/ph7software-ph7-social-dating-cms)

Was this useful?