Weave Code
Source Laravel Package
redaxo/source
REDAXO is an easy-to-learn, flexible open-source CMS with content built from custom modules and full control over input and output. Multilingual, highly extendable, and adaptable to your workflow, it has been powering websites since 2004 and is backed by a friendly, helpful community.
REDAXO, a PHP-based CMS since 2004. Both simple and flexible.
Frequently asked questions about Source
- Is redaxo/source a Laravel package?
- No. redaxo/source is the distribution payload for REDAXO 5.21.5, a standalone PHP CMS that ships its own application framework and system addons. It does not register a Laravel service provider, publish config, or expose facades, and it owns the request lifecycle end to end.
- Can I install redaxo/source with Composer in Laravel 11 or 12?
- You can require the Composer package, but it is not designed as a library consumed by a Laravel monolith, so Laravel version support is not applicable. There are no Laravel integration points, and its SQL, templates, users, sessions, and permissions replace rather than complement Eloquent, Blade, and Laravel auth. Treat it as a separate application or content service, not a drop-in content module.
- What PHP and database versions does redaxo/source require?
- REDAXO has a PHP 8.3+ baseline and includes forward-compatibility work for PHP 8.5/8.6 deprecations. It runs on MySQL or MariaDB on commodity LAMP infrastructure, with Apache or nginx. rex_sql_table normalizes column types and defaults across MySQL and MariaDB to reduce schema churn.
- How do I integrate REDAXO with Laravel authentication or SSO?
- This is the costly seam. Bridging Laravel auth into REDAXO requires a custom addon built on session-ID and remember-key rotation, the passkey table, and admin-right revocation semantics that change over time. If you need identity integration, plan for SSO via a dedicated addon or run REDAXO as a separate content service and integrate over HTTP/JSON.
- Can I use Eloquent, migrations, or Blade with redaxo/source?
- No. REDAXO uses rex_sql and rex_sql_table instead of Eloquent and Laravel migrations, and fragments, templates, and modules instead of Blade. It also uses rex_list for grids and rex_escape for output encoding. You can selectively reuse MIT-licensed patterns such as rex_sql_table's idempotent ensure semantics as a migration reference, but not as a Laravel package.
- Is redaxo/source production-ready and secure?
- It is a mature CMS with a responsive security process, but its cadence is high and occasionally urgent. Version 5.21.4 was an emergency release for an unauthenticated backend session takeover via structure/history, and 5.21.5 fixed package-API privilege escalation, CSRF on safe-mode toggling, stored XSS, and permission-scope issues. Operationally, you need a patch SLA that can deploy core and addon security updates within 72 hours and a plan for addon-level kill switches.
- What license does redaxo/source use?
- There is ambiguity to close: Packagist reports NOASSERTION, while LICENSE.md and the README badge say MIT. Get the MIT licensing recorded in writing before any legal sign-off. Do not rely on the Packagist metadata alone.
- What are Laravel-native alternatives to redaxo/source for content management?
- If the requirement is content inside a Laravel monolith, redaxo/source is not a fit. Use a Laravel-native CMS or content package that integrates with Eloquent, Blade, and Laravel auth, or adopt a headless content service and integrate over HTTP/JSON. REDAXO fits only when you need a full standalone CMS.
- How should I evaluate redaxo/source before committing?
- Run a two-week spike with one throwaway instance from the release tarball. Install demo_base, the only demo fully translated to English and designed to explain major concepts, and test editorial workflows, multilingual content, permissions, and patch deployment. Confirm the named internal owner can read PHP and REDAXO addon idioms, and check whether German-language community support is acceptable.
- Is redaxo/source actively maintained and well tested?
- Yes, maintenance is active and security releases are coordinated with GHSAs, though the patch cadence can be frequent and occasionally urgent. The project wires Psalm including taint analysis, PHPStan, PHPUnit, Rector, and php-cs-fixer into composer check, with regenerable baselines. The community is mainly German-speaking but known for being helpful, and the software ships in several languages including English.
Weaver
How can I help you explore Laravel packages today?