Weave Code
Minervaclient Bundle Laravel Package
ice/minervaclient-bundle
Symfony bundle that integrates the Minerva client into your app, with configurable service wiring, authentication, and HTTP transport for calling Minerva APIs with minimal setup. It centralizes connection settings, supports dependency injection, and keeps API usage consistent across environments.
Client for the ICE Minerva API
Frequently asked questions about Minervaclient Bundle
- Is ice/minervaclient-bundle a Laravel package?
- No. The -bundle suffix, the ice/ vendor namespace, and the Symfony DependencyInjection extension and Configuration tree indicate this is a Symfony bundle, not a Laravel package. It does not ship a Laravel ServiceProvider, a Minerva facade, or a publishable config/minerva.php file. Laravel teams should evaluate it as a Symfony artifact and not expect the usual composer require plus php artisan vendor:publish onboarding path.
- How do I integrate and configure ice/minervaclient-bundle in Laravel?
- You cannot register the bundle itself in Laravel; instead, strip the Symfony glue and reuse the underlying client classes if they are plain PHP with constructor injection. Register the Minerva client as a singleton in a small MinervaServiceProvider, move connection settings into config/services.php, and expose it through a typed wrapper. If the service classes are coupled to Symfony kernel parameters or event dispatchers, integration cost rises sharply and a sidecar may be safer.
- How do I install ice/minervaclient-bundle?
- Install it with composer require ice/minervaclient-bundle. In a Symfony app you then register the bundle in the kernel and let its extension load the service definitions from your configuration. In Laravel there is no vendor:publish step for this package, so treat installation as the first spike: check the package's composer.json constraints and confirm what classes are actually usable outside Symfony.
- Does ice/minervaclient-bundle support Laravel 10 or 11?
- There is no official Laravel support. The package is a Symfony bundle, and its Symfony and PHP version pins may come from the Symfony 3.x or 4.x era, which can conflict with Laravel 10 or 11's dependency graph. Run composer why-not and a resolution test early, because a failed dependency solve is a common blocker for this kind of university-internal artifact.
- What does ice/minervaclient-bundle actually do?
- It is a transport and DTO layer over the ICE Minerva HTTP API, part of Cambridge's ICE authoring and rendering toolchain. The durable value is the endpoint contract, request and response handling, and authentication plumbing, not the Symfony bundle glue. The bundle centralizes connection settings, supports dependency injection, and keeps API usage consistent across environments.
- Is there a framework-agnostic Minerva client I can use without Symfony?
- Possibly. Check whether ice/minervaclient-bundle depends on a sibling package such as ice/minervaclient that contains the real client logic. If that library exists, require it directly and bind its client in Laravel, ignoring the bundle entirely. That is the best-case integration path and can reduce the work to a one- or two-day spike.
- How does ice/minervaclient-bundle handle Minerva authentication?
- The package provides configurable service wiring and authentication plumbing, but the overview does not specify whether Minerva uses API keys, OAuth, or mTLS. Confirm the authentication model and whether it assumes a Cambridge identity provider before planning the integration. Treat credentials, network reachability, and licensing for the Minerva endpoint as blocking questions, not details.
- How do I test or mock Minerva API calls in a Laravel app?
- Do not try to boot the Symfony bundle in your test suite. Instead, bind a fake implementation of your typed Minerva wrapper or inject a mock PSR-18/Guzzle client so feature tests never hit the live Minerva API. Keep a small contract test around the request and response DTOs, and record real Minerva responses as fixtures if the API contract is undocumented.
- Is ice/minervaclient-bundle actively maintained and production ready?
- Treat it as high risk. Stars, dependents, and community score are all zero, which means no third-party de-risking and little issue history to search. It is a university-internal artifact, so check whether the repository is archived, when it was last committed to, and whether the Minerva API itself is documented, versioned, and supported. For production, assume you own the maintenance burden.
- What are the alternatives to ice/minervaclient-bundle for Laravel?
- The preferred alternative is to call the documented Minerva HTTP API directly from Laravel using Guzzle or any PSR-18 client, with your own DTOs and a typed wrapper. If a framework-agnostic ice/minervaclient library exists, consume that instead of the bundle. A Symfony sidecar that hosts the bundle and exposes a thin internal API is possible but adds two to three weeks plus ongoing operations overhead.
Weaver
How can I help you explore Laravel packages today?