- How do I install escolalms/webinar in a Laravel application?
- Require the package with Composer (composer require escolalms/webinar), then publish its config and migrations using the package's vendor:publish tags and run php artisan migrate. Seed the webinar permissions and assign them to the roles that should host or attend sessions. The service provider registers models, repository bindings and API resources automatically in a standard Laravel install. Because it is a module of the EscolaLMS suite, it expects the surrounding LMS packages (users, auth/roles, courses, notifications) to already be installed.
- Which PHP and Laravel versions does escolalms/webinar support?
- The package targets modern Laravel on PHP 8.x, typically Laravel 9/10-class applications backed by MySQL or Postgres, Redis queues and the Laravel scheduler. Always confirm the exact constraints in the package's composer.json before upgrading, since the EscolaLMS core packages it depends on move in step with it. The release line is 0.1.x, so pin an exact version in composer.json rather than relying on a caret range in production.
- Which video providers does EscolaLMS/Webinar support for live sessions?
- The package provides live video streaming with Jitsi and YouTube support, so webinars can be delivered either through a self-hosted or hosted Jitsi room or via a YouTube live stream. You supply the provider credentials and a publicly reachable callback/webhook route in the package config. Confirm with the maintainers which provider features (recording, waiting rooms, attendance reporting) are actually implemented before committing to a provider, and request a sandbox or test tenant for staging.
- Can I connect a webinar session to a course in EscolaLMS?
- Yes. The package is designed to connect sessions with courses so learners can join meetings directly from the platform, and it ships Eloquent models and API resources that map webinar entities into the wider LMS. In practice you install it as an additive module behind your existing auth guard and user model, then link webinar records to your courses or trainings. No backfill is needed because the package owns its own tables.
- Does escolalms/webinar work standalone without the EscolaLMS platform?
- No. EscolaLMS/Webinar is a modular package built to be dropped into an existing EscolaLMS (Wellms) application, not run on its own. It depends on the shared auth and roles layer, the user model, and typically the notifications and courses modules for a coherent experience. If you are not already running EscolaLMS, budget for installing and configuring the core suite first, or evaluate a standalone webinar solution instead.
- How are permissions and roles handled for webinar hosts and participants?
- Access is gated through the shared EscolaLMS auth and roles layer, with policies and permissions checked in the package's controllers and API resources. After installing, seed the package's permissions and map them to your existing roles so hosts can create and manage sessions while participants can only view and join. Smoke-test CRUD endpoints as each role, including edge cases like a participant trying to edit a session. Review the default permission set with the maintainers if your role model differs from the standard EscolaLMS one.
- Is the new order by sorting in escolalms/webinar 0.1.44 safe to expose?
- Version 0.1.44 added order by support to listing endpoints, which is an additive change with no migration or config signature change. User-supplied sorting is a classic injection and performance vector, so verify the implementation whitelists sortable columns and validates direction before anything reaches the ORDER BY clause. Also check that sorting unindexed columns on large attendance tables does not force expensive filesorts, and test how it interacts with pagination and existing filters.
- Do I need queue workers and a scheduler to run webinars with EscolaLMS?
- Yes. The package uses queued jobs for reminders, notifications and webinar lifecycle transitions, and relies on Laravel's scheduler for time-based work, so run queue workers and the scheduler in every environment where webinars are live. You also need a publicly reachable endpoint for provider callbacks and webhooks, including in staging, otherwise session status will not update. Confirm your callback handlers are idempotent so duplicate or replayed provider events cannot double-process attendance or status changes.
- How do I upgrade escolalms/webinar safely within the 0.1.x line?
- 0.1.44 is a drop-in for ^0.1 consumers, so a composer update with no data migration is normally enough. The compatibility work is horizontal: align your EscolaLMS core package versions, keep a lockfile, and confirm new query parameters such as order by do not clash with existing front-end query strings or cached list responses. Because the project is pre-1.0 with frequent patch releases and no SemVer guarantee, pin exact versions and read the changelog before every bump.
- Is escolalms/webinar production ready and what are the main risks?
- It is functional and follows solid EscolaLMS conventions, but it is pre-1.0 with frequent patch releases, no SemVer guarantee, limited published test coverage and maintainer concentration, so treat it as a calculated risk. The dominant runtime risk is the external video provider's API, OAuth token lifecycle and rate limits rather than the PHP code itself. Mitigate by pinning versions, staging with provider sandbox credentials, adding API contract tests that cover permissions and the new sorting parameters, and capturing licence and maintenance signals before you commit.