- What is ort-interactive-gmbh/laravel-couchbase used for?
- It is a Laravel adapter that exposes Couchbase documents through an Eloquent-style model and fluent query builder for buckets and collections. It also advertises Couchbase cache and session drivers. Treat it as a narrow legacy integration rather than a full ORM replacement.
- How do I install laravel-couchbase with Composer?
- Install it with Composer using composer require ort-interactive-gmbh/laravel-couchbase, then confirm the package's service-provider registration and configuration steps. Because the last release is from 2018, run the install in a disposable Laravel app first and verify Composer constraints against your PHP and Laravel versions. Do not assume auto-discovery or current framework compatibility without a spike.
- Which Laravel and PHP versions does this Couchbase package support?
- The package targets Laravel 5.x-era behavior and PHP 7.x runtimes, with a compatible ext-couchbase and matching Couchbase SDK/server. The available context does not provide a current support matrix, and PHP 8.x plus modern Laravel are unproven. Confirm exact version constraints before adoption.
- Does it support Couchbase 7 scopes and collections?
- The overview advertises support for Couchbase 7 scopes and collections, but the technical evaluation flags compatibility with Couchbase SDK 3.x and Couchbase Server 7.x as unproven. Test scope and collection queries against your exact cluster and SDK build. Do not rely on the marketing blurb alone.
- How do I configure a Couchbase connection in Laravel?
- Configure Couchbase like any Laravel database connection, typically by adding a connection entry in config/database.php with host, bucket, credentials, and scope or collection settings as documented by the package. Then validate service-provider registration, authentication mode, TLS, and connection pooling in a proof of concept. Exact environment variable names should come from the package docs or source.
- Can I use Eloquent relationships, migrations, and transactions with Couchbase?
- Expect only partial Eloquent semantics: document models and a fluent query builder, not full relationships, migrations, or relational transactions. Couchbase index deployment and JSON schema evolution happen outside Laravel migrations. Inventory joins, constraints, atomicity, and reporting needs before migrating from a relational store.
- Does the package support N1QL, pagination, aggregates, and consistency controls?
- N1QL coverage, parameter binding, pagination, aggregates, scans, and consistency controls are key validation points, not guaranteed features. The technical evaluation specifically recommends proving CRUD, N1QL, index, consistency, and failure scenarios. Do not assume query-builder parity with Eloquent or the official SDK.
- Is laravel-couchbase maintained and production ready?
- It is effectively unmaintained: the last release was in 2018, community validation is limited, and compatibility with current Laravel, PHP 8.x, and Couchbase SDK 3.x is unproven. Production adoption requires a named internal owner willing to fork, pin dependencies, and maintain CI. For greenfield or strategic systems, prefer the official Couchbase SDK behind your own adapter.
- Are there Couchbase cache and session drivers for Laravel in this package?
- Yes, the package advertises Couchbase cache and session drivers alongside the model and query builder. Validate driver behavior, key design, expiration, concurrency, and failure handling against your cluster before using them in production. These drivers are part of the same unmaintained codebase, so treat them with the same risk assessment.
- What alternatives should I consider to laravel-couchbase?
- The main alternative is the official Couchbase PHP SDK wrapped in an application-owned repository interface, which avoids leaking this package into domain code. A relational database may be the better choice if Couchbase itself is not clearly justified. Forking this package is reasonable only for a constrained legacy stack where its Eloquent-style API delivers measurable migration value.