- How do I install modstore/connection-manager in Laravel?
- Install it with Composer using composer require modstore/connection-manager. Because version 1.0.4 adds Laravel 12 support as a patch release, the change is semver-compatible and no migration code is expected. After installing, commit your composer.json and composer.lock changes and run your existing test suite. There is no published service provider configuration confirmed in the available evidence, so check the repository README for any publish steps.
- Does modstore/connection-manager support Laravel 12?
- Yes. Release 1.0.4 is a patch release whose sole change is Laravel 12 support, which suggests the package tracks Laravel's annual release cadence. That support is likely expressed as a widened illuminate/* Composer constraint rather than proven against a full Laravel 12 CI matrix, so verify it in a staging branch. Running your application test suite on Laravel 12 is the safest confirmation.
- What PHP version does modstore/connection-manager require?
- The available evidence does not state an explicit PHP floor for the package itself. Because Laravel 12 requires PHP 8.2 or higher, adopting the Laravel 12-compatible 1.0.4 release implicitly raises your runtime to PHP 8.2+. Check the published composer.json for any platform or minimum-stability requirements before upgrading.
- Can I use modstore/connection-manager for multi-tenant applications?
- Yes, that is a primary intended use case. The package is designed for dynamic-connection and multi-tenant setups where you define, switch, and configure multiple database connections from one place. It focuses on runtime connection management rather than full tenant lifecycle tooling, so pair it with your own tenant resolution logic. Benchmark it if connection switching happens on a hot path such as middleware or queue workers.
- How do I switch database connections at runtime in Laravel with this package?
- The package centralizes connection definition and switching so you can change the active connection at runtime instead of editing config files. The exact API is not documented in the available evidence, so review the repository README and source before wiring it into your code. Keep switching logic behind a small internal abstraction so you can swap the package out later if needed. Always cover switching behavior with integration tests against a real database.
- Is upgrading to modstore/connection-manager 1.0.4 a breaking change?
- No, it is a patch release under semver, and the only noted change is added Laravel 12 support. That pattern implies a widened Composer constraint with no public API breakage for existing consumers. To be certain, diff the published composer.json between 1.0.3 and 1.0.4 and run composer update --with-dependencies in a branch. Confirm that Laravel 10 and 11 support is preserved rather than narrowed.
- Does modstore/connection-manager still work with Laravel 10 and 11?
- Most likely yes, since framework support added at patch level is usually implemented by widening the constraint to include the new major alongside existing ones. However, the release note does not explicitly confirm that Laravel 10 and 11 remain supported. Verify by inspecting the composer.json require block in the tagged release. If you are on Laravel 11, this release is forward-looking and not immediately required.
- What are the alternatives to modstore/connection-manager for dynamic database connections?
- Laravel's built-in config and DB facade already let you add and switch connections at runtime with config(['database.connections.name' => ...]) and DB::connection('name'). Many teams also use tenancy packages such as stancl/tenancy for full multi-tenant lifecycle handling. modstore/connection-manager is narrower, focused on defining and switching connections from one place. Compare its abstractions against anything you already have internally to avoid duplication or conflict.
- Is modstore/connection-manager production ready and actively maintained?
- Same-cycle Laravel 12 support indicates active maintenance and framework-version awareness. Release cadence, issue throughput, long-term maintainer commitment, and code quality could not be verified from the available evidence. Before adopting it in production, require a documented security disclosure channel or explicitly accept the risk. Pin the version and keep a rollback path to the previous release.
- How do I test Laravel 12 compatibility with modstore/connection-manager before deploying?
- Pin 1.0.4 in a staging branch and run composer update --with-dependencies, then execute your full test suite against Laravel 12 on PHP 8.2+. Audit the dependency tree against your lockfile for conflicts or unmaintained transitive packages. Also check whether the package's CI actually tests Laravel 12 or merely declares it in composer.json. Promote to production only after the suite passes, keeping a pin to the prior version for rollback.