- How do I install dcblogdev/laravel-dropbox in a Laravel application?
- Install the package with Composer using composer require dcblogdev/laravel-dropbox. Laravel package auto-discovery should register the service provider and facade, but you can publish the config file if you need to customize it. Then add your Dropbox app key, secret, redirect URI, and token settings to your environment or config.
- Does dcblogdev/laravel-dropbox support Laravel 13?
- Yes. The v3.0.8 release broadens the framework constraint to include Laravel 13. The supplied evaluation describes this as an additive-only change with no breaking API, signature, or config changes. You should still confirm the exact constraint in composer.json and that your PHP and Guzzle versions resolve cleanly.
- How do I configure Dropbox API credentials for this Laravel package?
- Publish the package config file and set the Dropbox app key, app secret, redirect URI, and token values in your .env or config files. The package uses Laravel's config repository and binds a Dropbox client through its service provider. Keep secrets out of version control and use separate Dropbox apps for local and production environments.
- Does this package handle Dropbox refresh tokens or long-lived access tokens?
- Dropbox now uses short-lived access tokens with refresh tokens, and the evaluation flags token lifecycle as a key item to verify before production use. The package is a wrapper around the official Dropbox PHP SDK, so refresh-token behavior depends on the pinned SDK version and how the package config expects tokens. Test token expiry explicitly in a sandbox account rather than assuming long-lived tokens will keep working.
- What Dropbox operations can I perform with dcblogdev/laravel-dropbox?
- The package provides a clean Laravel facade for Dropbox API v2 operations including OAuth, file uploads, downloads, folder listing, metadata, and sharing operations. The evaluation also lists delete as a basic operation to exercise during a spike. It is a thin infrastructure wrapper, so you call Dropbox operations directly through the facade rather than through domain models.
- Is dcblogdev/laravel-dropbox safe to use in production?
- It is a low-coupling Laravel wrapper around the official Dropbox SDK, which keeps the integration surface small. The main production risks are transitive SDK version drag, Dropbox token lifecycle handling, and single-maintainer governance risk. Accept those explicitly and verify the SDK version, PHP support, and refresh-token flow before relying on it for critical file operations.
- How can I test Dropbox uploads and downloads without hitting the real API?
- The overview does not document built-in fakes or HTTP recording helpers. A practical approach is to isolate Dropbox calls behind your own interface and mock the facade or underlying client in unit tests. Then run a small end-to-end spike against a Dropbox sandbox account for upload, download, list folder, and delete.
- What are the alternatives to dcblogdev/laravel-dropbox?
- You can use the official Dropbox PHP SDK directly if you do not need Laravel-specific wiring. Other options include Flysystem Dropbox adapters for Laravel filesystem semantics or a custom thin wrapper around the SDK. This package's value is its Laravel service provider, facade, and publishable config, not a separate Dropbox implementation.
- Do I need database migrations or a queue worker for this package?
- No. The evaluation describes the package as a standard Laravel service-provider and facade wrapper with a publishable config file, and it does not impose domain models, migrations, middleware, queues, or scheduled jobs. It slots into an existing Laravel app as an infrastructure adapter. You only need to configure credentials and call the facade where needed.
- How do I upgrade to dcblogdev/laravel-dropbox v3.0.8 and which versions are supported?
- The v3.0.8 release is described as a low-risk, additive constraint bump that adds Laravel 13 support without breaking API or config changes. Upgrade by adjusting your Composer constraint and running composer update, then confirm the package resolves with your framework, PHP, and Guzzle versions. Check the package composer.json and test matrix for exact supported combinations rather than assuming every Laravel and PHP pairing is covered.