- Is gdbots/ncr a Laravel package?
- No. gdbots/ncr is framework-agnostic and is not a Laravel package; it ships no service provider, facade, or config stub. You can still use it inside Laravel as an isolated content domain module, but you must write the container bindings, configuration, and lifecycle wiring yourself.
- How do I install gdbots/ncr with Composer?
- Run composer require gdbots/ncr; the package is PSR-4 compliant and Apache-2.0 licensed. Expect transitive dependencies such as gdbots/pbj, gdbots/pbjx, gdbots/common, and a storage driver like gdbots/ncr-eloquent or gdbots/ncr-dynamodb. There is no Laravel auto-discovery, so installation is only the first step; wiring is manual.
- What Laravel and PHP versions does gdbots/ncr support?
- The provided material does not state a validated Laravel/PHP support matrix, and it warns that PHP and illuminate/database constraints may lag current Laravel majors. Check the package's composer.json and test against your exact Laravel and PHP versions before committing. Treat version compatibility as a pinning risk, not an assumption.
- Does gdbots/ncr work with Eloquent?
- Not in the usual sense. NCR does not sit underneath Eloquent; it competes with Eloquent for ownership of the content domain. The gdbots/ncr-eloquent driver uses Laravel's database layer for storage, so connections and transactions stay familiar, but Eloquent remains appropriate for everything outside NCR-managed content nodes.
- What storage backends can I use with gdbots/ncr?
- The documented options are gdbots/ncr-eloquent for SQL-backed storage and gdbots/ncr-dynamodb for DynamoDB; an in-memory repository is useful for early modeling and tests. Choose the backend before designing your integration, because the DynamoDB path adds AWS coupling that is hard to reverse. Confirm latency and hydration behavior at your expected node counts.
- How do I set up PBJ schema compilation in a Laravel project?
- PBJ schemas define your content types and are compiled to PHP classes, so schema compilation must be added to your build pipeline and CI. In Laravel, teams typically wrap that codegen and any reindex jobs in Artisan commands. This is unusual for a Laravel shop and needs deliberate CI work.
- Is gdbots/ncr safe for production?
- The evaluation rates technical risk as high, driven mainly by ecosystem maturity rather than code quality. gdbots/ncr has zero stars and zero dependents, no Stack Overflow corpus, concentrated vendor bus factor, and documentation that is README-plus-source. For production, demand a validated support path, version matrix, and migration plan before adoption.
- What changed in gdbots/ncr v3.1.2?
- v3.1.2 hardens GetNodeRequestHandler so aggregate-synced nodes with empty event streams are no longer treated as valid. It is a read-path correctness fix, not a risk-profile change. The underlying data condition can still exist in your store, so you need a detection and repair path.
- How does gdbots/ncr handle events and writes?
- NCR models content nodes with a UUID NodeId, slug, etag, and curation status, with event-sourced writes handled through gdbots/pbjx. Queue workers are the natural place for event dispatch and curation transitions. The team should have event-sourcing experience or budget for a learning curve.
- What are alternatives to gdbots/ncr for content in Laravel?
- The obvious alternative is staying with Eloquent-based content modeling and the surrounding Laravel ecosystem such as Nova and Scout. NCR is only a strong fit if you genuinely want a schema-first content model, node references, curation workflow, and swappable storage. If those requirements are absent, NCR replaces Laravel primitives rather than integrating with them.