Here's an example post-install script which replaces the Jitsi logos and some branding copy using a combination of downloading files and editing configuration files. You could include a block there and use CSS to, for example, hide any page elements you didn't want. It's empty by default, and is included into the main landing page, so anything you add there is appended to the page. One quick way to do some light branding is using the body.html file. The core UI files are stored in: /usr/share/jitsi-meet/ on the Meet server for each shard. Here are some resources for implementing UI customizations: Or, you can fully whitelabel a custom interface with the iframe API.
Alternately, you can use the interface.js API to provide customization parameters in URL parameters when creating a room.
PERSONALIZING JITSI MEET CODE
You can fork the code for the Jitsi Meet UI (it's a React app), compile a new app bundle with npm and webpack, and replace the stock one with a post-install script. UI customization can be accomplished a number of ways. It's recommended to develop scripts using something like a self-contained Docker image of Jitsi to increase familiarity with the different config files, then add them to the CloudFormation template when ready.
PERSONALIZING JITSI MEET INSTALL
in an S3 bucket), and provide the URL to the CloudFormation template as a parameter, which will download and run that script as part of the install process, so you have a repeatable build/launch process for all of your customizations.Īll post-install scripts are run as root. You then host that setup script somewhere public (e.g.
You write a bash script that does additional config, which can include things like using command line tools to modify the core jitsi config files, downloading a custom frontend, etc, it's completely up to you. The CloudFormation template gives you post-install hooks to make additional modifications to the deployment on launch. Also include hints and tips for less technical readers.Customization Using Post-install Scripts #
We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Service: Blogger - Alternative: WordPress Service: Google Reader - Alternative: Tiny Tiny RSS Service: Dropbox - Alternative: Nextcloud While you're here, please Read This FirstĪ place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
0 kommentar(er)
