edumeet / moodle-mod_edumeet

Multiparty Meeting Moodle integration

WebRTC meeting service

Official website: edumeet.org

Try it online at usually.in

Join our discord server here

Main features

Feature	Description
A/V streaming	Share your microphone and camera + additional video stream
Screen sharing	Share your screen to make some presentation right from your desktop
File sharing	Share your files with the peers (torrent solution under the hood)
Chat messages	Text conversation with other participants
Local Recording	Record window/tab/screen content in browser supported formats with room audio and save them (disabled by default)
Authentication	Supported types: OIDC, SAML, Local DB

Installation

Prerequisites

• Docker and docker-compose
• Curl
• If you want to access the service from the internet, you need a public IP address
• 2 fqdns (one for the main service and one for the turn server) that point to the public IP address
• Ports 80/tcp, 443/tcp need to be open on the public IP address
• Ports 40000-40249/udp and 40000-40249/tcp are not strictly necessary, but are recommended for better connectivity

Installation steps

1. Run the installation script

./run-first.sh

This will ask you for a main domain and a media domain. It will also ask you for an email address for the certificates, but you can leave it empty if you don't want to receive notifications about the certificates. The script will also ask you for the listen IP of the server as well as the external IP. If you don't have a separate external IP, you can use the same IP for both.

The script will then prepare the certificates and the services. You may inspect and change the values in the .env file as needed. The script will read the .env file and use the values from there if they are present, so you can also set the values in the .env file before running the script. You may delete the .env file to start from scratch.

2. Docker compose

docker-compose up -d

This will start all the services. And you are done. You can now access the service at the main domain you provided.

Configuration

The configuration for the client is in the client folder. You may change it as needed, but no changes are necessary for the service to work. The configuration for the room-server is in the room-server folder. You may change it as needed, but no changes are necessary for the service to work.

Community-driven support

Type
Open mailing list	[email protected]
Subscribe	lists.edumeet.org/sympa/subscribe/community/
Open archive	lists.edumeet.org/sympa/arc/community/

Authors

• Håvar Aambø Fosstveit
• Stefan Otto
• Mészáros Mihály
• Roman Drozd
• Rémai Gábor László
• Piotr Pawałowski

License

MIT License

Contributions to this work were made on behalf of the GÉANT project, a project that has received funding from the European Union’s Horizon 2020 research and innovation programme under Grant Agreement No. 731122 (GN4-2). On behalf of GÉANT project, GÉANT Association is the sole owner of the copyright in all material which was developed by a member of the GÉANT project.

GÉANT Vereniging (Association) is registered with the Chamber of Commerce in Amsterdam with registration number 40535155 and operates in the UK as a branch of GÉANT Vereniging. Registered office: Hoekenrode 3, 1102BR Amsterdam, The Netherlands. UK branch address: City House, 126-130 Hills Road, Cambridge CB2 1PQ, UK.

moodle-mod_edumeet's Issues

missing privacy api

Moodle implements a privacy api - it would be nice if you could implement this in your plugin. Sites that use continuous integration processes will not be able to use your plugin as Moodle includes unit tests to check that all installed plugins contain appropriate privacy classes.
more information on the privacy api is here:
https://docs.moodle.org/dev/Privacy_API

please note - this is not a blocker for approval in the plugins db but would be nice to add at some point.

incorrect camel case in strings

Moodle uses sentence case - eg:

$string['multipartymeetingname'] = 'Room Name';

should be:

$string['multipartymeetingname'] = 'Room name';

incorrectly defined settings.

https://github.com/misi/moodle-mod_multipartymeeting/blob/master/settings.php#L31
settings like "multipartymeeting_baseurl" should be defined as "multipartymeeting/baseurl" - this puts them in the correct location within the config_plugins table - you should not be using the global $CFG variable but using the get_config('multipartymeeting') function to obtain settings within the correct location.

more information on this is available here:
https://docs.moodle.org/dev/Admin_settings

invalid install.xml

your install.xml file looks incorrect and may cause issues for some sites.

You need to use the built-in xmldb editor UI in Moodle to fix this - easiest way to do this is to open it in the xmldb editor and make a change to a comment on a field or table to trigger a change - then use the xmldb editor built-in functions to save the file (you may need to change file-level permissions to allow xmldb editor to save the file.)

missing capability checks

All pages should implement appropriate capability checks - I can see you have added require_course_login, but this is not enough. see here for a summary of our security guidelines:
https://docs.moodle.org/dev/Security#Summary_of_the_guidelines

ideally you should implement a mod/multipartymeeting:view capability -and check that before displaying a meeting or a link to the meeting etc.

Missing Backup api

Moodle activity modules must implement the backup api so that they are included in the course backup/restore process.

This is a blocker for approval in the plugins db.

consider adding travis ci support

Some of the tests run by the Moodle.org plugins db can be run via travis-ci on each commit in your github repo. Enabling Travis integration helps you to make sure future changes to your plugin will continue to follow the guidelines.

More information on this is here:
https://moodle.org/mod/forum/discuss.php?d=323384

but the short version:
grab this file:
https://github.com/moodlerooms/moodle-plugin-ci/blob/master/.travis.dist.yml
rename it as .travis.yml and put in the root of your github directory.
Go to:
https://travis-ci.org/profile/YOUR_GITHUB_USERNAME
Flick the switch for this repo.

then on every commit you make to github it will fire off a request to travis to run the tests in .travis.yml and will give you traffic lights beside each commit and generate a report.

something else you might want to change:
in .travis.yml the default file has this line:

env:
global:

MOODLE_BRANCH=MOODLE_35_STABLE
you might want to add other branches to that list - so you might want to change it something like:

env:
global:
MOODLE_BRANCH=MOODLE_35_STABLE
MOODLE_BRANCH=MOODLE_36_STABLE
MOODLE_BRANCH=MOODLE_37_STABLE