Weave Code
Laravel Sabre Laravel Package
monicahq/laravel-sabre
Laravel Sabre integrates the SabreDAV server with Laravel, making it easy to add WebDAV, CalDAV, and CardDAV endpoints using Laravel routing, authentication, and configuration.
Sabre.io DAV server adapter for Laravel
Frequently asked questions about Laravel Sabre
- What is monicahq/laravel-sabre used for?
- It is a Laravel adapter for the SabreDAV server, used to expose WebDAV, CalDAV, and CardDAV endpoints inside a Laravel application. It lets DAV requests flow through Laravel routing, authentication, middleware, logging, and exception handling instead of requiring a separate server setup.
- How do I install monicahq/laravel-sabre in a Laravel application?
- Install it with Composer using composer require monicahq/laravel-sabre, then follow the README for publishing configuration and defining DAV routes. Confirm the package version supports your Laravel and PHP versions before installing, and run your application tests after wiring the endpoints.
- Does laravel-sabre support WebDAV, CalDAV, and CardDAV endpoints?
- Yes. The package integrates the SabreDAV server with Laravel so you can add WebDAV, CalDAV, and CardDAV endpoints through Laravel routing and configuration. The 2.0 release keeps URL and configuration compatibility while moving the adapter onto Laravel's native request pipeline.
- Which Laravel, PHP, and SabreDAV versions does monicahq/laravel-sabre 2.0 support?
- The exact Laravel, PHP, and SabreDAV constraints are defined in the package's composer.json and release notes, so verify them against your platform before upgrading. The provided release information does not list specific version numbers, and version compatibility should be checked rather than assumed.
- Is upgrading to laravel-sabre 2.0 a drop-in replacement?
- Only for applications that use the package through documented configuration with no custom DAV code. The release notes say configuration, environment variables, and URLs do not need changes, but code that calls removed APIs or binds or extends internals requires migration.
- What breaking changes should I check before upgrading to laravel-sabre 2.0?
- Version 2.0 rebuilds the adapter on a framework-native request pipeline and removes previously public extension points and internal classes from the public surface. You should search for LaravelSabre::getNodes(), LaravelSabre::getPlugins(), InvalidStateException, and direct use or subclassing of LaravelSabre\Sabre\Server or LaravelSabre\Sabre\Sapi. Read MIGRATION.md and map each usage to its documented replacement.
- How does laravel-sabre handle authentication and middleware?
- It integrates DAV handling into Laravel's normal HTTP pipeline so routing, authentication, middleware, logging, and exception handling follow Laravel behavior. After upgrading to 2.0, regression-test middleware ordering, auth failures, error mapping, and request/response bridging because the pipeline was rebuilt.
- Can I use custom SabreDAV plugins or extend the Sabre server with laravel-sabre?
- You can only rely on extension points that remain public in the version you use. In 2.0, previous subclassing and container-binding patterns for LaravelSabre\Sabre\Server and LaravelSabre\Sabre\Sapi are not part of the public surface, so custom plugins and extensions must be validated against MIGRATION.md and the release notes.
- How should I test CalDAV/CardDAV endpoints after upgrading laravel-sabre?
- Pin your current 1.10.x baseline, capture current DAV behavior, then upgrade in a non-production branch. Run your unit and application test suite plus DAV-specific integration tests against real clients for discovery, sync, PUT, REPORT, PROPFIND, authentication failures, and error responses. Canary the release before full rollout.
- Is monicahq/laravel-sabre actively maintained, and what alternatives exist?
- The 2.0 major release and MIGRATION.md indicate ongoing maintenance, but you should check release cadence, issue activity, and supported Laravel versions before committing. Alternatives include integrating SabreDAV directly into Laravel routes or evaluating other maintained Laravel DAV packages against your CalDAV/CardDAV conformance requirements.
Weaver
How can I help you explore Laravel packages today?