* implement first version of the recording authentication, redirecting to the playback URL with the jwt token * set default recording visibility by environment variable * use the http header, if present, to determine the client ip address * fix email verification when disabled * revert playback component to link_to, change method to get * remove unnecessary variable * Added "Add to Google Calendar" button on Room page * Added Google Calendar button enable to env.sample * Updated CSS for the Google Calendar Button row * Added correct translation when copying room link * Fixed new Google Calendar button mobile display * GRN-80: Allow local accounts on multitenant (#428) * Changed the way the omniauth providers are declared * Allow local authentication for multitenant mode based on customer settings * Cleanead up code mandated by rubocop * Completed implementation for signin and added the one for signup * Fixed issue with rubocop * Renamed customer_name to lb_user * Renamed lb_user -> user_domain, fixed issue with signup controller, email verification WAS NOT implemented * Completed implementation of email_verification * Fixed rubocop issue * Final update * Fix for test with loadbalancer * Make sure loadbalancer mockup is only used when env defined * Fix for test on rooms_controller * Fixed most of the test failing on multitenant env * Fixed issue detected by rubocop * Fixed issue with activation tockens not working on resend * Fixed new issue found by rubocop * Updated travis script * Harcoded credentials for mockup * Updated expectation on start_session * Fixed issue with duplication of home room * Updated script for rubocop * Restored Gemfile * Update sample.env * Update sample.env |
||
---|---|---|
app | ||
bin | ||
config | ||
db | ||
lib | ||
log | ||
public | ||
scripts | ||
spec | ||
test | ||
tmp | ||
vendor/assets | ||
.dockerignore | ||
.gitignore | ||
.gitlab-ci.yml | ||
.rake_tasks~ | ||
.rspec | ||
.rubocop.yml | ||
.ruby-version | ||
.travis.yml | ||
Dockerfile | ||
Gemfile | ||
Gemfile.lock | ||
Jenkinsfile | ||
LICENSE | ||
README.md | ||
Rakefile | ||
config.ru | ||
docker-compose.yml | ||
greenlight.nginx | ||
sample.env |
README.md
Greenlight
Greenlight is currently on version 2.0. If you are still running Greenlight 1.0 we suggest upgrading to 2.0.
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 Twitter, Google, 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:
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.