Weave Code
Scheduling Bundle Laravel Package
novosga/scheduling-bundle
Scheduling bundle for Novo SGA that adds appointment booking, service and time-slot management, and queue-friendly workflows to PHP applications. Helps organize availability and connect scheduling with existing Novo SGA operations.
NovoSGA v2 Scheduling bundle
Frequently asked questions about Scheduling Bundle
- Is novosga/scheduling-bundle a Laravel package?
- It is a Symfony bundle for Novo SGA v2, not a native Laravel package. Direct Composer inclusion in a Laravel app is unproven and likely to conflict with Laravel's framework assumptions. The recommended pattern is to run it as a Symfony service and call it from Laravel over HTTP or queued events.
- How can I integrate novosga/scheduling-bundle with a Laravel application?
- Use the bundle inside an isolated Symfony 7.4 LTS service that exposes scheduling CRUD and sync operations through an API. Laravel then acts as a client for booking, availability, and confirmation workflows. Plan for auth, tenancy, and data synchronization work in the adapter layer.
- Which Laravel versions does novosga/scheduling-bundle support?
- There is no Laravel-specific support indicated in the release notes. Compatibility depends on the API or bridge you build between Laravel and the Symfony service. Treat direct package installation as unproven until a proof-of-concept validates it against your target Laravel version.
- What PHP and Symfony versions does the scheduling bundle require?
- Version 2.3.0 upgrades to Symfony 7.4 LTS, which generally implies PHP 8.2 or newer. You should confirm the exact PHP constraint and any Doctrine, Twig, or Symfony UX dependencies in Composer before adoption. Run a dependency audit as the first integration step.
- Does it depend on Doctrine ORM, Twig, or Symfony UX?
- The bundle is Symfony-based and likely carries Doctrine, Twig, and Symfony UX assumptions, but the exact dependency set should be verified in composer.json. These dependencies matter because they affect whether any code can be reused directly in Laravel. Audit them before designing a bridge or sidecar service.
- How does novosga/scheduling-bundle handle timezones and UTC?
- Release 2.3.0 includes a UTC datetime fix that reduces timezone-related defects in commands and confirmation display. Store schedule data in UTC and convert at the presentation boundary in your Laravel client. Add timezone regression tests around booking, confirmation, and sync flows.
- Can I use it for appointment booking and time-slot management?
- Yes, the bundle adds appointment booking, service and time-slot management, and queue-friendly workflows to Novo SGA. It is designed to organize availability and connect scheduling with existing Novo SGA operations. Laravel teams should consume those capabilities through a service boundary rather than in-process reuse.
- What is the safest way to evaluate novosga/scheduling-bundle before production?
- Start with an isolated Symfony 7.4 LTS proof-of-concept using version 2.3.0. Validate UTC behavior, the new sync button, and confirmation flows before defining a Laravel-facing API contract. Then add a Laravel client with auth and tenancy adapters and queue sync operations idempotently.
- What are the alternatives to using a Symfony scheduling bundle in Laravel?
- Laravel-first booking and scheduling packages avoid a second runtime and framework mismatch, but they may not match Novo SGA queue workflows. Another option is building a thin Laravel-native adapter around an API service. Compare maintenance cost, timezone handling, and tenancy support before choosing.
- Is novosga/scheduling-bundle maintained and production-ready for Laravel?
- The 2.3.0 release is a maintenance and UX update with Symfony 7.4 LTS, which improves supportability. Production use with Laravel carries medium-to-high risk for direct adoption and medium risk for a sidecar service. Assign internal ownership for the API bridge, timezone tests, and upgrade cadence.
Weaver
How can I help you explore Laravel packages today?