Weave Code
Registry Bridge Laravel Package
fleetbase/registry-bridge
fleetbase/registry-bridge is a Laravel package that acts as an integration bridge to Fleetbase's registry, offering a simple way to connect your PHP application and work with registry data. It suits developers needing a lightweight package-level bridge for Fleetbase registry integration.
Internal Bridge between Fleetbase API and Extensions Registry
Frequently asked questions about Registry Bridge
- What is fleetbase/registry-bridge used for?
- It is the integration layer that connects a Fleetbase application to the external Fleetbase registry service. It wraps authentication, HTTP request handling, and response mapping behind a configurable Laravel API so you do not duplicate service-provider or HTTP boilerplate. Typical use is working with registry data such as engines, registry extensions, installed and purchased items, and categories through the host Fleetbase app.
- How do I install fleetbase/registry-bridge?
- Install it with Composer using composer require fleetbase/registry-bridge inside a Fleetbase Laravel host application. This release has no migrations, artisan commands, or config publish step, so the practical install is a Composer update plus an Ember asset rebuild where the Fleetbase UI is used. Confirm your Fleetbase core and ember-ui/ember-core versions resolve before deploying.
- Is fleetbase/registry-bridge a standalone Laravel package?
- No. It is best treated as an application extension for a Fleetbase deployment rather than a general-purpose installable library. It ships Laravel registry models and API endpoints, console and engine wiring, and Ember UI components such as ExtensionCard. The Ember UI and core version pins mean it cannot be upgraded independently of the Fleetbase front-end build.
- Which Laravel versions does fleetbase/registry-bridge support?
- The release notes provided do not state an explicit Laravel version matrix or a minimum Fleetbase core version. Because the package is coupled to a Fleetbase host app and pinned Ember UI/core versions, the practical answer is the Laravel version supported by your Fleetbase baseline. Check the composer constraints and confirm the Fleetbase core baseline with maintainers before upgrading.
- How do I configure registry endpoints, credentials, and timeouts?
- The package exposes configurable endpoints, credentials, and timeouts through its Laravel integration layer. Configuration is intended to live with the Fleetbase host application; this release does not include a config publish step. Review the package config keys and verify the target environment's registry endpoint after any upgrade.
- Does fleetbase/registry-bridge support retries and error handling?
- Yes. The package provides typed request and response handling with error and retry support, which is one of its main advantages over hand-rolled HTTP calls. You should still validate failure behavior for your registry endpoints, especially around authentication and timeouts. Because the package is pre-1.0, test retry behavior after each patch upgrade.
- Can I use fleetbase/registry-bridge outside a Fleetbase application?
- It is not designed as a generic registry client for any Laravel app. The package is coupled to Fleetbase registry models, API routes under registry/v1, console and engine wiring, and Fleetbase Ember UI components. If your team is Laravel-only, half the package is out of scope and the Ember ExtensionCard changes are irrelevant. For a non-Fleetbase app, use a direct HTTP client or a dedicated integration package instead.
- What changed in fleetbase/registry-bridge v0.1.11?
- v0.1.11 includes PHP/Eloquent connection routing changes and an Ember template/component argument fix. The notable change is connection pinning: registry models and category queries now always use the live connection, even in sandbox mode. The release has no migrations, commands, or schema changes, but it does require a front-end asset rebuild for the Ember fix to land.
- Does sandbox mode make real calls to the production registry?
- Based on the v0.1.11 connection-pinning change, registry models and category queries always use the live connection even in sandbox mode, so sandbox installations can make real outbound calls to the registry. That fixes the reported 500s but creates a split-brain topology where operational data is sandbox and registry metadata is live. Ask the maintainers whether a documented override exists before using sandbox against production credentials.
- How do I upgrade fleetbase/registry-bridge safely?
- Bump the package with Composer, then ensure fleetbase/ember-ui is at least 0.4.6 and fleetbase/ember-core is at least 0.3.26 so the host front end resolves. Rebuild and redeploy the Ember assets because the ExtensionCard fix only lands after the asset build. Then re-verify registry endpoints in the target environment and confirm the Fleetbase core baseline, which the release notes do not state.
Weaver
How can I help you explore Laravel packages today?