Weave Code
Framework Laravel Package
flarum/framework
Flarum is a free, open-source forum platform built on a Laravel-style PHP backend with a modern JavaScript frontend. Its fast, extensible architecture offers a clean REST API and a rich extension system, making it easy to launch and customize a beautiful community forum.
Simple forum software for building great communities.
Frequently asked questions about Framework
- Can I install flarum/framework with Composer inside an existing Laravel application?
- No. flarum/framework is the core runtime that Flarum's own extensions build against, not a Laravel package you can require into an existing app. Flarum is a standalone, opinionated forum application deployed on its own host, typically via composer create-project flarum/flarum. Treat it as an adjacent deployable joined by SSO, JSON:API, and links rather than an embedded dependency.
- Is flarum/framework a Laravel package, and which Laravel versions does it support?
- It is not a Laravel package and does not declare Laravel version compatibility. It consumes selected Illuminate and Symfony components internally, so many idioms will feel familiar, but it ships its own bootstrap, CLI, service-provider and extender model, and JSON:API layer. Plan upgrades around Flarum's own release cycle and extension APIs, not Laravel's release cadence.
- How do I integrate Flarum SSO with Laravel Passport or Socialite?
- Use Flarum's OAuth2/OIDC or SAML extensions and make Laravel the identity provider of record through Passport or Socialite-backed authentication. Flarum must never own credentials. Avoid sharing Laravel's session cookie directly because session handling, CSRF, and cookie configuration diverge, and Laravel session changes can silently log out the forum.
- Can I embed Flarum's forum UI inside a Laravel Blade view?
- No, there is no supported path to render a Flarum forum panel inside a Blade view. Flarum is a Mithril.js single-page application that assumes it owns the page. Integrate by link-out, subdomain, or reverse proxy under a path, and keep the forum as its own presentation surface.
- What database does Flarum require, and can I use PostgreSQL with my Laravel app?
- In practice Flarum requires MySQL or MariaDB. If your Laravel estate uses PostgreSQL, adopting Flarum introduces a second database technology for your platform team to own. Verify current requirements in the Flarum documentation before planning, but do not assume PostgreSQL support.
- How should Laravel and Flarum share data: JSON:API, database, or webhooks?
- Integrate against Flarum's JSON:API rather than its MySQL schema, which is an internal detail being rewritten in 2.0. Outbound integration relies on third-party extensions such as webhooks or audit logs, not a first-party event bus, so each extension becomes a maintenance dependency. Keep integrations explicit and version-pinned.
- Does Flarum support multi-tenancy for per-tenant Laravel applications?
- Flarum has no native multi-tenancy; one forum runs per install. For a per-tenant Laravel product, plan for N instances or build a tenancy layer yourself. That is an operational and cost decision, not a configuration toggle.
- How do I test Flarum integration from a Laravel test suite?
- Test the integration boundary rather than Flarum internals: exercise JSON:API calls, SSO flows, and webhook payloads from Laravel HTTP tests against a disposable Flarum instance. Use a MySQL or MariaDB test database and pin the Flarum version used in CI. Avoid coupling tests to Flarum's database schema or extension internals.
- What production risks should I assess before adopting Flarum in a Laravel estate?
- Key risks include the 1.x to 2.0 extension API transition, maintainer concentration in third-party extensions, MySQL-only datastore, no native multi-tenancy, and questionable release metadata. Pin a minor version with a named upgrade owner and underwrite only core APIs. Verify release tags on Packagist and GitHub before committing to planning dates.
- Is Flarum a good alternative to a Laravel-native forum package, and how active is maintenance?
- Flarum is mature and self-sufficient, but its value comes from deploying and integrating it rather than extending deep into a Laravel codebase. If you need a forum inside your Laravel application, compare carefully with a Laravel-native package or a custom build. Check core release cadence and each load-bearing extension's author activity before adoption.
Weaver
How can I help you explore Laravel packages today?