- Does meloflavio/owncloud-uploader-bundle work with Laravel out of the box?
- No. The package is a Symfony bundle that plugs an ownCloud storage backend into VichUploaderBundle, so it ships no Laravel service provider, facade, or publishable config. VichUploaderBundle itself relies on Doctrine entity mappings and Symfony's DI container, neither of which exists in a Laravel app. For Laravel you would need to rewrite the upload logic against the Storage/Flysystem layer or ownCloud's OCS API.
- How do I install and register the bundle in a Symfony application?
- Install it with composer require meloflavio/owncloud-uploader-bundle, then register the bundle in config/bundles.php. After that, point a VichUploaderBundle mapping's uploader key at the service the bundle provides and add your ownCloud settings to a file under config/packages/. No database schema changes are required, so the install is a small, contained change.
- How do I configure the ownCloud server URL and credentials?
- You supply the ownCloud host, user, and an app password or token plus a base path through the bundle's container configuration. Keep those values in environment variables or Symfony secrets rather than committing them to the repository, since the package holds write access to your storage. Confirm whether your server requires HTTPS-only access and whether the configured user has upload rights in the target directory.
- Does this bundle replace VichUploaderBundle or does it depend on it?
- It depends on it. The bundle occupies only the storage driver slot, implementing Vich's storage interface so uploaded files land on ownCloud instead of the local filesystem. Vich still handles entity mapping, lifecycle listeners, and file naming strategy. That narrow surface area is the main appeal: you can migrate one entity mapping at a time while existing local filesystem mappings stay untouched.
- Which Symfony and PHP versions does this package support?
- The declared constraints are unverified, and the last release was June 2023, so treat compatibility as unproven until you check. Run composer why-not against your PHP and Symfony versions before committing, since a 2023-era bundle may not resolve on Symfony 6.4 or 7.x with PHP 8.3+. Also verify which VichUploaderBundle major version the storage implementation targets, because that interface has changed over time.
- Does it support chunked uploads for large files?
- This is not documented in the package overview and needs to be verified in the source. The bundle is described as a lightweight wrapper around ownCloud file transfer, which suggests single-request PUT over WebDAV rather than chunked uploads. Chunked transfer matters above roughly 100 MB, so if you expect large media files, confirm the behaviour before you build on it.
- What is the best way to upload files to ownCloud from a Laravel app?
- Do not try to adapt this Symfony bundle. Instead, register a Flysystem WebDAV adapter as a custom disk in config/filesystems.php, or call ownCloud's OCS API directly with Laravel's HTTP client. Both approaches fit Laravel's existing Storage abstraction and keep uploads testable with Storage::fake. Budget this as a small custom build rather than an integration.
- Is this package actively maintained and safe for production?
- There are warning signs: zero stars, zero dependents, a single maintainer, and no release since June 2023. There is also no visible CI, test coverage, security policy, or issue triage, so the code is effectively unvetted. Pulling an unaudited dependency that holds credentials with write access to your storage is a real supply-chain risk. If you adopt it, pin the version, review the source, and scope credentials to a single upload directory.
- How are deletes, overwrites, and file collisions handled?
- This is not documented and must be checked in the implementation. You need to know whether removing a Doctrine entity also deletes the remote file, and what happens when a partial failure leaves the two out of sync. Collision behaviour on same-name uploads is equally important, since silent overwrites can destroy user data. Test these paths against a real ownCloud instance before going live.
- Is there a test suite, and does it mock the ownCloud client?
- The repository shows no evidence of CI or automated tests, which means there is no safety net for upgrades or interface changes. Ask the maintainer whether any tests exist and whether they mock the ownCloud client or require a live server. If none exist, write your own integration test against a disposable ownCloud instance so you can detect regressions when you bump PHP or Symfony.