A grounded operations room for an independent community platform, with subtle discussion networks and infrastructure dashboards.

Independent community infrastructure

Good Phorum

GP stands for Good Phorum. The P in Phorum stands for Perl. A general-purpose, Perl-native forum platform for communities that need durable discussion, explicit governance, serious moderation, and infrastructure that can be operated for years.

Perl
application runtime
BSD-3
licensed foundation
Perl
native by design
PostgreSQL authoritative Mojolicious SSR Minion workers PostgreSQL FTS Redis optional
Platform

Built for communities that outlive trends.

Good Phorum treats a forum as civic software: conversations, policy, moderation, search, events, and operations are all first-class parts of the system.

Durable discussion

Spaces, categories, threads, posts, revisions, archival, and search are modeled as long-lived community assets.

Operational moderation

Reports, scoped staff authority, reversible actions, audit logs, and policy versioning keep governance visible.

Independent stack

Modern Perl, Mojolicious, DBIx::Class, PostgreSQL full-text search, Minion, and a Redis-optional coordination model.

Architecture

A modular monolith with distributed instincts.

The design favors explicit boundaries, stateless app nodes, event tables, asynchronous projections, observable workers, and cache layers that can be rebuilt.

Edge Nginx or HAProxy
Application Mojolicious nodes
Domain Identity, discussion, moderation, authorization
Persistence PostgreSQL, event log, audit log
Derived systems Minion, PostgreSQL FTS, local caches, realtime
Governance

The rules are part of the product.

Good Phorum does not bury moderation inside ad hoc admin screens. Policy, trust, role scope, auditability, appeals, content lifecycle, and privacy rights are documented as architecture.

01

Deny by default

Authorization evaluates actor, action, target, scope, resource state, and user state.

02

Events tell the truth

Durable domain events drive projections, notifications, replay, and audit investigation.

03

Privacy is operational

Retention, deletion, export, consent, search visibility, and breach readiness are explicit.

Roadmap

A running forum, with room to grow.

The forum HTTP MVP is running. What remains is the hardening that turns a working system into one you can trust with a community.

  1. Shipped Identity

    Registration, login, server-side sessions, revocation, CSRF, and password and email lifecycle tokens.

  2. Shipped Core forum

    Categories, threads, replies, revisions, keyset pagination, search, and safe server-rendered composition.

  3. Shipped Moderation

    Scoped roles, reports, reversible actions, suspensions, and audit review for staff.

  4. Next Private beta

    Mail delivery, staging drills, database-backed failure tests, and load tests on representative hardware.

Open source, BSD-3-Clause

Read the code. Run the gates.

Clone the repository, install dependencies with Carton, and run make check: syntax, tests, Perl::Critic, perltidy, and the architecture contract.

View on GitHub