Weave Code
Google Spreadsheet Bundle Laravel Package
asgoodasnu/google-spreadsheet-bundle
A Symfony bundle for integrating Google Spreadsheets into your application. It provides configuration and container services for authenticating with Google APIs and reading or writing spreadsheet data, simplifying Google Sheets access in Symfony projects.
Integrates asimlqt/php-google-spreadsheet-client with Symfony2 and google/apiclient
Frequently asked questions about Google Spreadsheet Bundle
- Can I use asgoodasnu/google-spreadsheet-bundle in a Laravel app?
- No. Despite often being filed under Laravel/PHP, this is a Symfony2 bundle: it ships a Bundle class, a DependencyInjection extension and a config tree meant for app/AppKernel.php. Laravel consumes Symfony components, not bundles, so it is not installable into a Laravel application in any meaningful sense. You would have to vendor the underlying asimlqt/php-google-spreadsheet-client and re-wire it by hand, at which point the bundle contributes nothing.
- Does google-spreadsheet-bundle support the Google Sheets API v4?
- No. It targets the retired legacy Spreadsheets API via asimlqt/php-google-spreadsheet-client, which speaks GData feeds and ClientLogin/OAuth1 bearer tokens. Sheets API v4 is REST/JSON with OAuth2 and a completely different resource model of spreadsheet, sheet, range and value range. Moving to v4 is a rewrite, not a configuration change.
- How do I install and configure asgoodasnu/google-spreadsheet-bundle?
- In a Symfony2 project you would require it with Composer, register the bundle in app/AppKernel.php and supply credentials through the bundle's configuration tree. It pulls in asimlqt/php-google-spreadsheet-client plus a pinned google/apiclient, which is where most of the dependency trouble starts. That whole setup path does not exist in a Laravel application, which has no kernel bundle registration or extension config tree.
- Which Laravel versions does this package support?
- None. There is no Laravel service provider, no facade and no config publishing in the package, so no Laravel version is supported. It belongs to the Symfony 2.x generation, and Symfony 2.8 itself lost security support in November 2018. Treat any Laravel compatibility claim you see for it as inaccurate.
- Is asgoodasnu/google-spreadsheet-bundle still maintained?
- There is effectively no maintenance signal: 0 stars, 0 dependents and a score of 0, sitting on top of a client library that targets a removed API. Upstream patches and security responses are not something you should expect. The framework generation it was built for is also end-of-life, so a host app inherits unrelated unremediated risk.
- Why does composer require conflict with google/apiclient?
- Versions of this vintage predate the Google_Client to Google\Client namespace migration, so their constraints will not co-install with a current google/apiclient without a fork. The bundle's pinned dependency locks you to an old client generation. If your app already uses a modern Google client for any other API, resolution fails or you end up with duplicate, conflicting installs.
- What should I use instead to read and write Google Sheets from Laravel?
- Use google/apiclient directly against Sheets API v4, wrapped behind your own interface such as SpreadsheetWriter::append(string $sheetId, array $row). The direct client call is roughly 30 lines and keeps one fewer dependency inside your trust boundary. A maintained wrapper like revolution/laravel-google-sheets is optional sugar, but nothing above your domain interface should know Sheets exists. This bundle is at most a pattern reference for the DI and credential plumbing.
- Should I use a service account or user OAuth for Google Sheets access from a server?
- Default to a service account JSON key for server-to-server access, and share the target spreadsheet with that service account address. Only choose delegated user OAuth if per-user Drive access is a hard requirement, because it adds token storage and refresh handling to your risk surface. Either way, keep credentials out of container params and config files that get committed or dumped.
- How do I test a Google Sheets integration without hitting the live API?
- Define the interface your domain actually needs, such as exportReport or syncRows, then fake that interface in tests so nothing above it touches Sheets. For the adapter itself, run a one-day spike against a throwaway sheet using a service-account key, read a range and append a row to prove the whole risk surface. Keep live-credential calls out of CI and assert the request payloads your adapter builds instead.
- Is it safe to store production data in a Google Spreadsheet?
- Treat a spreadsheet as an unmanaged data store, not a database. PII or financial data living in a sheet that ops staff edit freely is a compliance finding waiting to happen, so classify the data before you build the sync. Also plan for quota ceilings rather than PHP performance as the real limit: if you need sub-second reads or large row counts per sync, the design is wrong regardless of which client you pick.
Weaver
How can I help you explore Laravel packages today?