Fork of with Debian packaging.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
This repo is archived. You can view files and clone it, but cannot push or open issues/pull-requests.
Mohamad Abras 018cd2568f
remove duplicate commented code (#2682)
2 years ago
.github Fix CI gem cache (#2673) 2 years ago
app use rails action_name & controller_name methods (#2666) 2 years ago
bin GRN2-241: Moved assets precompile to start script (#927) 3 years ago
config remove duplicate commented code (#2682) 2 years ago
db Add optional moderator codes (#2413) 2 years ago
lib Complete refactor of Gemfile and upgraded gems (#2553) 2 years ago
log initial commit 5 years ago
public Remove extra favicon (#2648) 2 years ago
scripts added sqlite to Gemfile (#2528) 2 years ago
spec Moved moderator access setting to Room Configuration (#2579) 2 years ago
test/mailers Added valid until text to invite email (#2599) 2 years ago
tmp initial commit 5 years ago
vendor/assets GRN2-253: Added the ability to share rooms across multiple users (#912) 3 years ago
.dockerignore Removed old travis stuff (#2531) 2 years ago
.gitignore Fix workflow cache (#2493) 2 years ago
.gitlab-ci.yml GRN2-112: Default language fallback fails with a 500 error (#469) 4 years ago
.rake_tasks~ Fixed loading of error pages (#310) 5 years ago
.rspec rework tests 5 years ago
.rubocop.yml make rubocop target Ruby 2.7 (#2671) 2 years ago
.ruby-version Update to Ruby 2.7 (#2292) 2 years ago
Dockerfile Upgrade to Rails 5.2.5 (#2638) 2 years ago
Gemfile Upgrade to Rails 5.2.5 (#2638) 2 years ago
Gemfile.lock Fix newline/whitespace in Gemfile.lock (#2640) 2 years ago
LICENSE add LICENSE file 5 years ago Readme PR template (#2632) 2 years ago
Rakefile Fixed #267 Email verification feature (#268) 5 years ago Create 3 years ago
cloudbuild-dev.yaml Fix session isssues (#730) 4 years ago
cloudbuild.yaml added cache layer to cloudbuild (#672) 4 years ago adhere to rubocop guidelines 5 years ago
docker-compose.yml GRN2-354: Switch default database to Postgres 13.2 (#2563) 2 years ago
greenlight.nginx Allow uploading larger presentations (#1977) 3 years ago
sample.env enable SMTPS: SMTP over direct TLS connection (#2485) 2 years ago
yarn.lock GRN2-176: Create a role editor that allows admins to specify what permissions each role has (#709) 4 years ago


Coverage!Status Docker Pulls

Greenlight is a simple front-end interface for your BigBlueButton server. At its heart, Greenlight provides a minimalistic web-based application that allows users to:

  • Signup/Login with Google, Office365, OpenID Connect, or through the application itself.
  • Manage your account settings and user preferences.
  • Create and manage your own personal rooms (BigBlueButton sessions).
  • Invite others to your room using a simple URL.
  • View recordings and share them with others.

Interested? Try Greenlight out on our demo server!

Greenlight is also completely configurable. This means you can turn on/off features to make Greenlight fit your specific use case. For more information on Greenlight and its features, see our documentation.

For a overview of how Greenlight works, checkout our Introduction to Greenlight Video:

GreenLight Overview

Installation on a BigBlueButton Server

Greenlight is designed to work on a BigBlueButton 2.0 (or later) server.

For information on installing Greenlight, checkout our Installing Greenlight on a BigBlueButton Server documentation.

Source Code & Contributing

Greenlight is built using Ruby on Rails. Many developers already know Rails well, and we wanted to create both a full front-end to BigBlueButton but also a reference implementation of how to fully leverage the BigBlueButton API.

We invite you to build upon Greenlight and help make it better. See Contributing to BigBlueButton.

We invite your feedback, questions, and suggests about Greenlight too. Please post them to the Greenlight mailing list.

To help with organization and consistency, we have implemented a Pull Request template that must be used for all Pull Requests. This template helps ensure that the project maintainers can review all PRs in a timely manner. When creating a Pull Request, please provide as much information as possible.