GithubHelp home page GithubHelp logo

bigbluebutton.github.io's Introduction

BigBlueButton Docs have transitioned to a new home (starting March 22, 2023)

The source of the documentation: https://github.com/bigbluebutton/bigbluebutton/tree/develop/docs (branch v2.6.x-release for BBB version 2.6, etc)

The docs website URL remains https://docs.bigbluebutton.org/

Please send any edits/report issues to the new source of the docs; this repository will remain available (in read-only form) for some time to ensure a smooth transition.

For the latest docs starting with BigBlueButton 2.6.0, please use the new documentation (linked above)



BigBlueButton Documentation

This repository contains the documentation for BigBlueButton located at docs.bigbluebutton.org.

This repository uses Jekyll to build the documentation site. When making changes to the docs, you should setup Jekyll to build it locally. That way, you can preview any changes before creating pull requests.

The easy way to preview (using Docker)

An easy way to generate the BigBlueButton documentation locally and see the effect of your changes before committing is to use Docker to run Jekyll.

docker run --rm -p 127.0.0.1:4000:4000/tcp --volume="$PWD:/srv/jekyll" -it jekyll/jekyll:3.4 jekyll serve --incremental

And you can now view the site using the URL http://localhost:4000/. If the Docker approach does not work, you can setup Jekyll using the steps below.

Note: If you're having troubles with page changes (especially page categories) not being correctly updated and symptoms similar to cached files, try to remove _site/* and re-run the docker command. The entire _site/ directory will be recreated using the local files.

Ruby

To install Ruby, we suggest the use of rbenv.

But you have other options:

  • Using RVM: see this page.
  • Using apt packages.
  • From source.

From now on, we will assume you will use rbenv, so if you decide for another method you might have to adapt some of commands in the rest of this guide.

The commands below will show you how to install rbenv. In short, this is what you will be doing:

  • Install rbenv
  • Install the plugin ruby-build plugin, that will actually be used to install ruby
  • Install the target ruby
  • Install bundler

Important: if you have RVM installed, you should remove it first!

# Install rbenv
$ git clone https://github.com/rbenv/rbenv.git ~/.rbenv
$ echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bash_profile
$ echo 'eval "$(rbenv init -)"' >> ~/.bash_profile
$ source ~/.bash_profile

# install ruby build
$ git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build

# clone this repo
$ git clone https://github.com/bigbluebutton/bigbluebutton.github.io.git

# install the targeted version of ruby
$ cd bigbluebutton.github.io
$ rbenv install
$ rbenv rehash
$ rbenv version
> 2.2.1 (set by (...)/bigbluebutton.github.io/.ruby-version)

# install bundler
$ gem install bundler
$ rbenv rehash

At this point you have the correct version of Ruby installed, now you have to install the site dependencies. Enter the directory bigbluebutton.github.io and type

bundle install

This will install all the Jekyll components. Next, type

bundle exec jekyll serve --host=0.0.0.0

Jekyll will run a server on port 4000 that lets you see a live update of the site after you make a save of any file.

 Freds-Air:bigbluebutton.github.io ffdixon$ jekyll serve
Configuration file: /Users/ffdixon/bigbluebutton.github.io/_config.yml
            Source: /Users/ffdixon/bigbluebutton.github.io
       Destination: /Users/ffdixon/bigbluebutton.github.io/_site
      Generating...
                    done.
 Auto-regeneration: enabled for '/Users/ffdixon/bigbluebutton.github.io'
Configuration file: /Users/ffdixon/bigbluebutton.github.io/_config.yml
    Server address: http://0.0.0.0:4000/
  Server running... press ctrl-c to stop.

You can now edit files locally, review changes locally, and push commits to GitHub.

bigbluebutton.github.io's People

Contributors

antobinary avatar basisbit avatar bkmgit avatar capilkey avatar daronco avatar farhatahmad avatar fcecagno avatar ffdixon avatar ghazitriki avatar guileme avatar gustavotrott avatar hajar1 avatar hiroshisuga avatar jfederico avatar jiama843 avatar joshua-arts avatar kdsbrowne avatar kepstin avatar lkiesow avatar matiasilva avatar maximkhlobystov avatar ozhurbenko avatar paultrudel avatar pedrobmarin avatar perroned avatar prlanzarin avatar ramonlsouza avatar ritzalam avatar samuelwei avatar zach-chai avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

bigbluebutton.github.io's Issues

docs.bigbluebutton.org still shows v2.2

The new v2.3 got released a couple days ago, and since 2.2 is based on ubuntu 16.04 which is EOL there will probably never be another bugfix release for it. Hence 2.3 should move from 2.3-dev to default and get some upgrade guide (or advise to backup greenlight DB if in use and recordings and do a clean install ...).
It's likely someone is already working on this but since there was no issue tracking progress ...

"Join" Documentation error?

Shouldn't this section say "There is only an XML response for this call if the redirect parameter is set to false" (instead of true)?

image

"Reduce bandwidth for webcams" instructions invalidated by BBB update

With BigBlueButton 2.22, dynamic video profiles were introduced and as a result several cameraprofiles were added in front of the existing profiles in /usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml

The instructions for reducing webcam bandwidth describe a way to automatically reduce the bandwidth for the four camera profiles low, medium, high and hd. However, since the first 4 profiles are targeted, the described commands now point at the profiles low-8, low-12, low-15 and low-20 instead.
0, 1, 2 and 3 should be changed to 6, 7, 8, 9 to restore its intended use. Alternatively, the profiles would need to be reordered in BigBlueButton.

Obselete fixed issues links

Moderator mute all users

As per the document :

Expected output: Moderators once mute all the users. The users should not be able to unmute themselves when the settings are being applied and the new user (who joins the meeting afterwards) should not be able to see the microphone option.

Issue: The users can unmute themselves even when they have been unmuted by the moderator and the new user is able to see the options to join as microphone while joining the meeting.

Issue_usersettings.docx

404 link in "Upgrading from BigBlueButton 2.2"

As I went through the docs I've found a dead link.

If you'll go this link you'll see the following text:

If you installed a previous version of BigBlueButton 2.2 using the step-by-step instructions, then you should backup any custom changes first (or setup https://docs.bigbluebutton.org/2.2/customize.html#automatically-apply-configuration-changes-on-restart to automatically apply your updates), and then upgrade using the commands below.

The link in this section gives me a 404 error.

As I dont' really know where this link should point to I didnt' fix it myself and it would be great if you'll fix this.

Use rbenv to install and manage the required ruby version

As far as I understand, there's nothing that really requires Ubuntu 14.04 to develop this site, correct? The only real requirement is a specific version of Ruby. We use rbenv (https://github.com/rbenv/rbenv) to install and manage multiple Ruby versions in the same machine, which makes very easy to install and test a deployment using a different version. The only thing we'd need to do is to create a file .ruby-version with the Ruby version inside, and install that version with rbenv (easily done by a single command). On another project, you can have a different version of Ruby on .ruby-version, and both versions can co-exist in the same system without any conflict.

Port range for FreeSWITCH is wrong in diagram

In images/22-connections.png, the external port range for FreeSWITCH ranges from 15634, however the real FreeSWITCH configuration begins its range at 16384.
I would fix that, but the sources of the diagram are not available.

Also, both the RAP scripts and bbb-web seem to connect to etherpad, those connections are missing as well.

Additional recording formats documentation is missing a required step.

Describe the bug
In the documentation pages, at section https://docs.bigbluebutton.org/2.3/install.html#installing-additional-recording-processing-formats the instructions do not mention a required "systemctl restart nginx" after installing the additional recording formats.

Installation type
bbb-install script?

Symptoms
when trying to listen/view/download an additional recording format, nginx results in 404 "not found": restarting nginx fully solve the errors.

Documentation for GDPR compliant setup

The goal of this issue is to collect suggestions + tasks for a documentation page on how to set up BBB in compliance to GDPR and similar data privacy & protection regulations around the world.

Tasks

  • collect various configuration files where to change logging settings to not log any "private" / person-identifiable data and how to change them
  • collect various places where legally required data (contact data, Terms of Service,....) can be added to Greenlight, BigBlueButton and the various BBB-Plugins
  • create best practices documentation and explain how to set up the system so that a BBB-service can be operated in compliance with GDPR or similar regulations

Results so far

  • Logfiles for nginx: /var/log/nginx/* can be changed to only log ERROR in /etc/nginx/sites-enabled/bigbluebutton and /etc/bigbluebutton/nginx/*
  • sed -i 's/ access_log.*/access_log \/dev\/null;/g' /etc/nginx/sites-available/bigbluebutton
  • sed -i 's/ error_log.*/error_log \/dev\/null;/g' /etc/nginx/sites-available/bigbluebutton
  • freeswitch? /opt/freeswitch/conf/vars.xml - logs to /opt/freeswitch/var/log/freeswitch
  • meteor/nodejs? - how to limit/disable? Is this what logs to /var/log/tomcat7?
  • red5 ? logs to /var/log/red5 - how to limit/disable?
  • Kurento logs to /var/log/kurento-media-server - how to limit/disable?
  • bbb-webrtc logs to /var/log/bbb-webrtc-sfu - can be disabled by setting log.level: none in /usr/local/bigbluebutton/bbb-webrtc-sfu/config/default.yml
  • Logging best practice: set appLogLevel=Error in /usr/share/bbb-web/WEB-INF/classes/bigbluebutton.properties
  • if recording feature is not needed, set disableRecordingDefault=true in /usr/share/bbb-web/WEB-INF/classes/bigbluebutton.properties and also breakoutRoomsRecord=false in /usr/share/bbb-web/WEB-INF/classes/bigbluebutton.properties
  • consider setting keepEvents=false in /usr/share/bbb-web/WEB-INF/classes/bigbluebutton.properties
  • set your own STUN server stunServers: \[\x27stun:.*/stunServers: \[\x27stun:stun.yourdomain.tld:3478\x27\], in /usr/share/meteor/bundle/programs/web.browser/app/compatibility/sip.js so that BBB-HTML5 client users don't send data to Google without consent
  • set your custom stun/turn instead of Freeswitch STUN sed -i 's/stun:stun.freeswitch.org/stun:stun.yourdomain.tld/g' /usr/share/bbb-web/WEB-INF/classes/spring/turn-stun-servers.xml
  • in /etc/cron.daily/bigbluebutton set history=1 and unrecorded_days=1 and published_days=1 and log_history=1 or similar values and also uncomment the line remove_raw_of_published_recordings close to the ending of the file, so that recording raw data actually gets deleted (if you didn't completely disable recording)
  • customize Greenlight to contain your Terms of Service documentation and also a data protection and data processing information documentation: Greenlight code customization and Greenlight Terms of Services

Would be nice if more people could help and add their suggestions and so on in this issue here, so that a good quality documentation can be created.

Possible error in sed command while installing greenlight following docs.

What is happening.

In the section for installing greenlight there is the following command:

export pass=$(openssl rand -base64 24); sed -i 's/POSTGRES_PASSWORD=password/POSTGRES_PASSWORD='$pass'/g' docker-compose.yml;sed -i 's/DB_PASSWORD=password/DB_PASSWORD='$pass'/g' .env

The problem is that the $(openssl rand -base64 24) part of the command can generate a / character, which will enter in conflict with the slashes already from the sed -i command.

My suggestion:

Replace that command for:

export pass=$(openssl rand -base64 24); sed -i 's\POSTGRES_PASSWORD=password\POSTGRES_PASSWORD='$pass'\g' docker-compose.yml;sed -i 's\DB_PASSWORD=password\DB_PASSWORD='$pass'\g' .env

that way, I don't think that a string can be generated with the counter-slash in it. But either way, we can also add a minor note warning the user that this error is likely to appear.

Edit:

Some logs of the original error:

image

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.