Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Jitsi Laravel Package

escolalms/jitsi

Laravel package from EscolaLMS that integrates Jitsi video conferencing into your application, letting you embed and manage Jitsi meetings within courses and other LMS features.

Deep Wiki
Context7

This package introduce just a facade that you can use to generate parameters for jitsi player

Frequently asked questions about Jitsi
What is escolalms/jitsi used for in Laravel?
It is a Laravel package that provides a facade for generating parameters used by a Jitsi player. It is aimed at EscolaLMS-style applications where you need to embed or manage Jitsi meetings inside courses and other LMS features. It does not host video infrastructure itself; it helps your Laravel app produce the data the Jitsi player needs.
How do I install escolalms/jitsi with Composer?
Install it with composer require escolalms/jitsi. Because it is a Laravel package, service provider and facade auto-discovery should normally register it, but you can add the provider and facade alias manually if your Laravel version or setup requires it. After installation, check the package source or README for the exact facade namespace and method names.
Do I need a Jitsi server or JaaS account to use this package?
The package only generates player parameters, so it does not replace a Jitsi deployment. You still need a Jitsi Meet server, a self-hosted Jitsi installation, or a Jitsi as a Service account to actually run meetings. Your Laravel app uses the generated parameters to connect the front end to that Jitsi environment.
How do I generate Jitsi player parameters using the facade?
Call the package facade from your controller, service, or view composer and pass in the meeting details your Jitsi player expects. The facade returns the parameters you can serialize into your front end or embed code. Because the package is intentionally lightweight, most integration work happens in how you supply and consume those parameters.
Is there a configuration file I can publish for escolalms/jitsi?
The package is described primarily as a facade for parameter generation, so it may not include a publishable config file. Check the package source or README for any config publishing command before assuming one exists. If configuration is minimal, pass meeting options directly to the facade methods in your application code.
Which Laravel versions does escolalms/jitsi support?
The exact Laravel version constraints are not stated in the provided package overview. Check the package composer.json on Packagist or in your vendor directory for the required PHP and illuminate/support versions. That file is the authoritative source for compatibility before you add it to a project.
Can I use escolalms/jitsi outside EscolaLMS courses?
Yes, the facade can generate Jitsi player parameters in any Laravel application where you can install the package. The EscolaLMS context describes its origin and typical use case, not a hard runtime requirement. You can use it for standalone meeting pages, event rooms, or other Jitsi embeds if the generated parameters fit your front end.
How do I test Jitsi parameter generation in my Laravel app?
Write feature or unit tests that call the facade with known meeting data and assert the returned parameters match your expected structure. You do not need a live Jitsi server for those tests because the package only builds parameters. If your app adds JWT signing or room provisioning around the package, test those separately with mocked HTTP calls or fixed keys.
Is escolalms/jitsi suitable for production use?
It can be suitable for production when used as intended: generating parameters for a Jitsi player that connects to your own Jitsi or JaaS environment. You should still review the package source, pin a tested version, and handle authentication, room security, and JWT signing in your own application where needed. Treat it as a small integration helper rather than a complete meeting management system.
What are alternatives to escolalms/jitsi for Laravel Jitsi integration?
Alternatives include using the official Jitsi Meet external API directly in JavaScript, generating JWT tokens with a dedicated JWT library, or using other Laravel packages that wrap Jitsi configuration. If you already use EscolaLMS, this package is the natural fit because it comes from the same ecosystem. For custom needs, a small in-app service that builds Jitsi options can be simpler than adding another dependency.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
jinas/dhivatar
store-doc/laravel-storage-driver
plus-it/laravel-translation-manager
diephp/perhaps
diephp/telegraph
osmaviation/spreadsheet
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console
pnscripts/filament-broadquill-lite
pnscripts/laravel-sentfold-lite
vleap/mx-sdk-laravel-internal
twidpay/utils
htetmyathlaing/scout-elasticsearch-driver
artisan-toolbox/front-awesome
ls/client-assistant
users-au/laravel-client
cgv/localized-resource