- How do I install graham-campbell/dropbox in a Laravel 5 application?
- Install it with composer require graham-campbell/dropbox. Because the package predates auto-discovery, manually add GrahamCampbell\Dropbox\DropboxServiceProvider to the providers array and 'Dropbox' => GrahamCampbell\Dropbox\Facades\Dropbox to the aliases array in config/app.php. Publish the config with php artisan vendor:publish and then verify the provider, config, token, and SDK are wired correctly with a synchronous call in artisan tinker.
- Does graham-campbell/dropbox support Laravel 5.5+ and package auto-discovery?
- There is no evidence that it supports Laravel 5.5+ or auto-discovery; the only release evidence is a Laravel 5.4 compatibility bump. You must register the service provider and facade alias manually. For Laravel 5.5 and newer, bind the official Dropbox SDK in your own small service provider instead.
- How do I configure Dropbox credentials and the default connection?
- Publish config/dropbox.php, which holds named connections with an app key, secret, and OAuth token plus the default connection name. Keep tokens in environment variables and read them from the config rather than committing secrets to the repository. Verify the resolved default connection before editing anything else.
- How do I upload a file or create a shareable link with the Dropbox facade in Laravel?
- Calls on the Dropbox facade are forwarded straight through to the official Dropbox SDK, so use SDK methods such as uploadFileFromString or uploadFile. You can select a named connection with Dropbox::connection('name') and call createShareableLink for sharing. Prove the full wire with one synchronous upload and link call in tinker before building queued jobs around it.
- Is graham-campbell/dropbox still maintained or deprecated?
- It is effectively dead: the repository sits under a GrahamDeprecated organisation with 0 dependents and a quality score of 0.3. There is no maintainer, no LTS commitment, no support path, and no evidence of test coverage or a security posture. Treat any defect escalation as your own team's responsibility.
- What Laravel and PHP versions does graham-campbell/dropbox support?
- Compatibility evidence stops at the Laravel 5.4 era, so it is only appropriate for legacy Laravel 5.x applications such as internal tooling or back-office jobs. Run composer why-not graham-campbell/dropbox 3.4.* to check whether the illuminate/support range or the Dropbox SDK pin conflicts with your lockfile before writing any code. If the target stack is modern, use the official SDK directly.
- Should I use graham-campbell/dropbox or the official Dropbox SDK directly?
- The package is only wiring: a service provider, a manager behind a facade, and a publishable config. All real capability comes from dropbox/dropbox-sdk-php, so the replacement cost is small and bounded. On any new build or modern Laravel version, bind the official SDK in a short service provider instead.
- How do I handle Dropbox rate limits, retries, and large chunked uploads?
- The bridge does not provide rate limiting, retry or backoff logic, chunked uploads, path normalisation, or exception translation. Those become your engineering scope as soon as you depend on the package. Wrap the SDK calls in your own client that handles 429 responses, backoff, and chunked upload sessions for large files.
- How can I test a Laravel Dropbox integration without hitting the live API?
- The package ships no testing helpers or fake transports. Mock the Dropbox facade or, better, introduce a DropboxClient interface and bind a fake implementation in your test container. Keep one optional synchronous smoke test in tinker or a staging environment to prove credentials and the SDK pin.
- How do I migrate off graham-campbell/dropbox to the official SDK?
- Introduce a DropboxClient interface on day one with just upload() and shareLink() methods. Bind it to a delegating implementation of the package today and later swap that binding to a direct dropbox/dropbox-sdk-php implementation. If you must stay on the package temporarily, hard-pin ^3.4 as an exact pin and register the provider and alias manually.