Weave Code
Google integration settings and helpers for Laravel Enso
Frequently asked questions about Google
- What is laravel-enso/google used for?
- It provides Google integration settings and thin helpers for Laravel Enso applications. Its main job is to expose a settings surface for Google API credentials such as client ID, client secret, service account JSON, and project identifiers inside Enso's settings module, then let other Enso modules obtain a configured Google client without re-reading config. It is not a standalone Google SDK wrapper.
- Do I need Laravel Enso to use laravel-enso/google?
- You should treat it as an Enso-only package. It assumes Laravel Enso core, the Enso settings subsystem, and Enso conventions for service providers, routes, menus, and Vue-based settings forms. Outside an Enso application, the package is better used as a reference implementation than as a dependency.
- How do I install laravel-enso/google in a Laravel Enso app?
- In an existing Enso app, installation is a Composer require with an explicit version pin, followed by publishing config and migrations and granting the relevant settings permissions. You then seed or configure the Google settings group and enter credentials per environment through the Enso settings UI or a deployment seeder. Keep credentials out of the repository and out of shared database dumps.
- Which Laravel, PHP, and Enso versions does laravel-enso/google support?
- The package is versioned in lockstep with specific Laravel Enso core releases, so you must match it to your Enso version. The available assessment does not provide a definitive support matrix for Laravel, PHP, or Enso versions, so check the repository's composer.json and release history before adopting it. Enso generally targets modern Laravel on PHP 8.x.
- How are Google API credentials stored, and are they encrypted?
- Credentials are stored through Enso's settings abstraction, so you must verify how that abstraction handles secrets in your Enso installation. The assessment flags encryption at rest, exclusion from settings export and import, and permission gating as the highest-severity areas to audit. Do not assume the package alone guarantees secure secret storage.
- Does laravel-enso/google support service accounts, OAuth user consent, and domain-wide delegation?
- The package's stated role is to store Google credentials and hand back a configured client; the evaluation explicitly asks whether it supports service account, OAuth user consent, and domain-wide delegation. Those auth modes likely depend on the underlying Google client and how the helper is implemented. Review the source before relying on any specific mode.
- Does laravel-enso/google manage OAuth refresh tokens and quota errors?
- The assessment describes it as a thin helper, not a full Google SDK wrapper, and notes little defensive handling of token refresh failures and quota errors. It may hand back a configured client while leaving refresh-token management and error handling to the underlying library or your application. Audit that behavior before using it in production workflows.
- How should I test laravel-enso/google in a Laravel application?
- For testing, isolate the client factory behind an interface or mock the configured Google client so tests do not call Google APIs. In an Enso app, use the settings subsystem to provide test credentials and assert that permission-gated settings are enforced. If you are not using Enso, copy the credential schema and factory pattern into your own service layer and test that directly.
- Is laravel-enso/google safe for production use?
- The package has zero stars, zero dependents, and no observable production adoption, so treat it as a reference implementation rather than a proven dependency. The dominant risks are abandonment, bus factor, and version lockstep with Enso core. It is small enough to audit and fork, but you should own the credential-handling and token-refresh logic if you adopt it.
- What are alternatives if I am not using Laravel Enso?
- If you are not on Laravel Enso, skip the package and store Google credentials in config/services.php with environment secrets or an encrypted model cast. Implement your own GoogleClientFactory interface around google/apiclient and handle OAuth refresh and quota errors in your application layer. This avoids the Enso settings dependency and gives you control over maintenance.
Weaver
How can I help you explore Laravel packages today?