- What does mpociot/illuminate-contao do?
- It bridges Contao CMS and Laravel by bringing Illuminate components into Contao projects. In practice that means you can use Eloquent models, database migrations, validation, and other familiar Laravel tools without leaving Contao. It is aimed at developers who want modern PHP patterns inside an existing Contao installation rather than a full framework migration.
- How do I install mpociot/illuminate-contao?
- Install it with Composer, for example composer require mpociot/illuminate-contao:0.1.0. Pinning the exact 0.1.0 release is safer than a caret range because the package carries no semantic-versioning guarantees at 0.x. After installing, verify whether the service provider is auto-discovered or must be registered manually, and confirm the Illuminate constraints resolve against your project's PHP version.
- Which Laravel and PHP versions does mpociot/illuminate-contao support?
- The declared constraints live in the package's composer.json, and that file is the authority rather than any README summary. Because 0.1.0 shipped without release notes, check which combinations are actually exercised in CI, not just declared. Test the exact Laravel major and PHP version your application runs before assuming compatibility.
- Is version 0.1.0 safe to use in production?
- A 0.x release carries no semantic-versioning promise, so any 0.2.0 could rename methods, move namespaces, or change config keys without a deprecation cycle. Treat minor bumps as incompatible by default and pin the exact version in composer.json. If you adopt it, require an explicit, reviewed upgrade rather than letting Composer drift you forward.
- Can I use Eloquent models inside a Contao project?
- Yes, using Eloquent is the core purpose of the package: it wires Laravel's Illuminate database layer into the Contao environment. You get the familiar model, query builder, and relationship APIs instead of hand-written database access. Confirm the connection and configuration wiring in a scratch project first, since documentation is thin at 0.1.0.
- Does it support migrations and validation like Laravel?
- The package advertises migrations and validation alongside Eloquent as part of the Illuminate toolset it exposes to Contao. If it ships migrations, review them before running: they should be additive and reversible, and any tables or config keys should be namespaced to avoid colliding with Contao's own schema. Run them against a disposable database first.
- What are the alternatives to mpociot/illuminate-contao?
- If you only need a database layer, pulling in illuminate/database or Capsule standalone is a lighter option than a full bridge. If you need the whole framework, running Laravel proper and integrating Contao content is a different and larger architecture. The package's value is specifically staying inside Contao while borrowing Laravel ergonomics, so evaluate it against that goal rather than against a full framework.
- Is mpociot/illuminate-contao actively maintained?
- It is effectively a single-author package from mpociot, which is common at this stage but represents bus-factor exposure. Check commit cadence, issue responsiveness, and whether CI runs a matrix across Laravel and PHP versions. Before committing, decide what maintenance signal would make you comfortable and whether you could vendor or fork the package if needed.
- How should I evaluate this package before adopting it?
- Run a timeboxed spike of one to three days in a non-production branch of an application that genuinely needs the capability. Exercise the primary use case end to end and record the integration cost in engineer-days. Where it would replace in-house code, keep both paths behind an interface for one release cycle so you can back out without a rewrite.
- Does it work across multiple Laravel major versions?
- Because the package is at 0.1.0, assume it is pinned to a narrow slice of Laravel until you verify otherwise. If your organisation runs several Laravel majors across services, a package tied to one major becomes a blocker at the next framework upgrade. Check the declared upper bounds in composer.json before standardising on it.