Fork of https://github.com/bigbluebutton/greenlight 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.
 
 
 
 
 
 
Jinesh edc29ede02 added cache layer to cloudbuild (#672) 4 years ago
app Removed left over testing code 4 years ago
bin Added step for precompiling assets (#302) 4 years ago
config Translate '/config/locales/en.yml' in 'pl_PL' (#643) 4 years ago
db Added Indexs to improve db performance (#551) 4 years ago
lib Fixed issues with endpoint and conf check (#553) 4 years ago
log initial commit 5 years ago
public add favicon 5 years ago
scripts Improve container build: GRN2-156 (#582) 4 years ago
spec GRN2-192: Made error pages more descriptive (#620) 4 years ago
test Rspec and rubocop fixes 4 years ago
tmp initial commit 5 years ago
vendor/assets Replaced old colour picker with a cleaner one (#617) 4 years ago
.dockerignore Adding Jenkinsfile to dockerignore 5 years ago
.gitignore GRN2-6: Added the ability for admins to specify registration method (#520) 4 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) 4 years ago
.rspec rework tests 5 years ago
.rubocop.yml GRN2-6: Added the ability for admins to specify registration method (#520) 4 years ago
.ruby-version set .ruby-version to 2.5.1 5 years ago
.travis.yml GRN2-159: Changed the inception of the version tag (#574) 4 years ago
Dockerfile Improve container build: GRN2-156 (#582) 4 years ago
Gemfile GRN2-30: Add custom ldap sign in page (#619) 4 years ago
Gemfile.lock GRN2-30: Add custom ldap sign in page (#619) 4 years ago
Jenkinsfile GRN-37: Externalized scripts for building/deploying docker images though CI (#375) 4 years ago
LICENSE add LICENSE file 5 years ago
README.md Small updates to ReadMe to better match the current state of Greenlight (#612) 4 years ago
Rakefile Fixed #267 Email verification feature (#268) 5 years ago
cloudbuild-staging.yaml added cache layer to cloudbuild (#672) 4 years ago
cloudbuild.yaml added cache layer to cloudbuild (#672) 4 years ago
config.ru adhere to rubocop guidelines 5 years ago
docker-compose.yml GRN2-162: Revert to sqlite in docker compose (#594) 4 years ago
greenlight.nginx make upgrading from 1.0 easier 5 years ago
sample.env GRN2-107: Add office365 auth (#616) 4 years ago

README.md

Greenlight

Travis CI Coverage!Status Docker Pulls

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

  • Signup/Login with Google, Office365, 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 developer mailing list.