# moderated-meetings **Repository Path**: mirrors_jitsi/moderated-meetings ## Basic Information - **Project Name**: moderated-meetings - **Description**: Jitsi Moderated Meetings microservice - **Primary Language**: Unknown - **License**: Apache-2.0 - **Default Branch**: master - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 0 - **Created**: 2020-08-09 - **Last Updated**: 2026-01-03 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README # Jitsi Moderated Meetings microservice Example of a standalone microservice that can generate tokens for Jitsi Moderated Meetings. ## Usage 1. ``npm install`` 2. Generate a keypair to sign JWT tokens. The public key will be used by `prosody` to validated moderated tokens, as described in: https://github.com/jitsi/lib-jitsi-meet/blob/master/doc/tokens.md 3. Create a `.env` file with environment variables in the following format: ``` DEPLOYMENT_URL= PORT= PRIVATE_KEY_FILE= PRIVATE_KEY_ID= TARGET_TENANT= ``` To generate the der file used for `PRIVATE_KEY_FILE`: ``` openssl rsa -inform pem -in jitsi-private.pem -outform der -out PrivateKey.der ``` 4. ``npm start`` 5. Open ``http://localhost:[PORT]/`` Note: - please see package.json for further npm run scripts. - the `npm start` script expects the `.env` file to exist, but the app can be ran with out that too. For details, see the `start` script in `package.json`. ## Local Image Testing The `./docker-local.sh` script is used for local testing in a Docker image. It expects the certificate file in the project root, named `moderated.der` (and it has to be reflected in the env variables too), and also expects the `.env` file to exist. ## Deployment The `deploy` script can be used to build and deploy a docker image to AWS ECR. Rigging associated with such a deployment is left as an exercise for the reader. Usage is ``./deploy.sh [version] [ecr_registry] [[ecr_region]]``