Owncloud Uploader Bundle Laravel Package

Product Decisions This Supports

• Storage backend selection for user-generated content. If the product needs to write uploaded files to a self-hosted ownCloud/Nextcloud instance instead of S3/GCS (data residency, on-prem enterprise deals, air-gapped deployments), this bundle is one data point on the "how hard is that, really?" question.
• Build vs. buy for a narrow integration. The package is a thin adapter that plugs ownCloud into VichUploaderBundle, the de facto Symfony upload-mapping bundle. Its existence tells you the integration is small — roughly a custom Vich uploader handler wrapping a WebDAV client — which argues for building it in-house rather than taking a dependency.
• Framework-fit check before roadmap commitment. Despite being submitted against a Laravel/PHP brief, this is a Symfony bundle (VichUploaderBundle is Symfony-only). That is itself a decision input: if the stack is Laravel, this package is not adoptable, and the equivalent path is league/flysystem-webdav behind a Laravel filesystem disk — a well-maintained first-party-adjacent option.
• Compliance/sovereignty feature framing. "Ship files to the customer's own storage" is a recurring enterprise requirement. This package is useful as prior art when scoping that feature, not as the implementation.
• Prior-art review for a fork. With 0 stars, 0 dependents, and a single release in June 2023, the realistic product use is reading the source to confirm the shape of the integration, then owning the code.

When to Consider This Package

Consider it only when all of the following hold:

• The application is Symfony, already standardized on VichUploaderBundle, and you want per-entity upload mapping to ownCloud without changing that architecture.
• The target is a WebDAV-compatible ownCloud instance and you have verified PHP and Symfony version compatibility yourself (last release 2023-06-13; assume Symfony 5/6-era and validate against your constraint set).
• You are prepared to vendor or fork the bundle into your repo and own its maintenance, security patching, and WebDAV client upgrades.
• The integration is non-critical — internal tooling, back-office, a migration bridge — not a customer-facing upload path with an availability SLO.

Look elsewhere when:

• The stack is Laravel. Use league/flysystem-webdav with a custom filesystem disk; it is maintained, widely deployed, and composes with the rest of Laravel's storage API. This bundle does not apply.
• You need supply-chain assurance. 0 stars, 0 dependents, and no ecosystem signal means no community CVE surfacing and no bus factor. Do not put this on a regulated data path.
• You are on Nextcloud. Nextcloud's WebDAV surface is compatible, but its own app ecosystem and the official clients are the better-supported integration story; a 2023-era unmaintained bundle is the wrong abstraction to lean on.
• You need modern Symfony (6.4/7.x) or PHP 8.3+. Verify or expect to patch; budget for that in the estimate.
• Uploads are a core product surface. In that case build the adapter internally against a maintained WebDAV client, so you control retries, timeouts, chunked uploads, and error semantics.

How to Pitch It (Stakeholders)

For executives: This is a small, unmaintained community adapter that connects Symfony's file-upload machinery to ownCloud. It has no adoption, no dependents, and no release in over a year, so we should not treat it as a supply-chain dependency. What it does tell us is that self-hosted-storage support is a small, well-understood piece of work — on the order of a few engineering days — which is good news for the on-prem/sovereignty roadmap. Recommendation: build the adapter ourselves against a maintained WebDAV library, and use this package only as a reference. Note also that it is Symfony-only, so for our Laravel services the equivalent is a supported Flysystem WebDAV disk, not this bundle.

For engineering: Treat meloflavio/owncloud-uploader-bundle as a design reference, not a dependency. It demonstrates the shape of a custom VichUploaderBundle upload handler backed by WebDAV to ownCloud. If we need the capability, implement an in-house handler over a maintained WebDAV client (or, on Laravel, a flysystem-webdav disk), with explicit ownership of retry, timeout, and failure handling. Adoption risks to log if anyone pushes for the package directly: single-author project, zero dependents, last release June 2023, unverified Symfony/PHP compatibility, and no security-response process.