Greenlight provides you with the ability to set the branding image that you see on the left side of the header. By default this is set to the BigBlueButton logo. You can change this by setting the BRANDING_IMAGEoption in the env file to a public URL for a png or JPEG image.
BRANDING_IMAGE=https://www.example.com/example.png
But where is the file that contains BRANDING_IMAGE= value?
these are the things that i need to remove + plus the favicon

curl -sSL https://rvm.io/mpapis.asc | sudo gpg2 --import -
sudo gpg2 --keyserver hkp://pool.sks-keyservers.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 7D2BAF1CF37B13E2069D6956105BD0E739499BDB
curl -sSL https://get.rvm.io | sudo bash -s stable
=> Run `rails server -h` for more startup options Puma starting in single mode... * Version 3.11.4 (ruby 2.5.1-p57), codename: Love Song * Min threads: 5, max threads: 5 * Environment: production * Listening on tcp://0.0.0.0:5000 Exiting Traceback (most recent call last): 29: from bin/rails:5:in `<main>' 28: from bin/rails:5:in `load' 27: from /greenlight/bin/spring:16:in `<top (required)>' 26: from /greenlight/bin/spring:16:in `require' 25: from /usr/local/rvm/gems/ruby-2.5.1/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `<top (required)>' 24: from /usr/local/rvm/gems/ruby-2.5.1/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `load' 23: from /usr/local/rvm/gems/ruby-2.5.1/gems/spring-2.0.2/bin/spring:49:in `<top (required)>' 22: from /usr/local/rvm/gems/ruby-2.5.1/gems/spring-2.0.2/lib/spring/client.rb:30:in `run' 21: from /usr/local/rvm/gems/ruby-2.5.1/gems/spring-2.0.2/lib/spring/client/command.rb:7:in `call' 20: from /usr/local/rvm/gems/ruby-2.5.1/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in `call' 19: from /usr/local/rvm/gems/ruby-2.5.1/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in `load' 18: from /greenlight/bin/rails:11:in `<top (required)>' 17: from /greenlight/bin/rails:11:in `require' 16: from /usr/local/rvm/gems/ruby-2.5.1/gems/railties-5.0.7/lib/rails/commands.rb:18:in `<top (required)>' 15: from /usr/local/rvm/gems/ruby-2.5.1/gems/railties-5.0.7/lib/rails/commands/commands_tasks.rb:49:in `run_command!' 14: from /usr/local/rvm/gems/ruby-2.5.1/gems/railties-5.0.7/lib/rails/commands/commands_tasks.rb:85:in `server' 13: from /usr/local/rvm/gems/ruby-2.5.1/gems/railties-5.0.7/lib/rails/commands/commands_tasks.rb:85:in `tap' 12: from /usr/local/rvm/gems/ruby-2.5.1/gems/railties-5.0.7/lib/rails/commands/commands_tasks.rb:90:in `block in server' 11: from /usr/local/rvm/gems/ruby-2.5.1/gems/railties-5.0.7/lib/rails/commands/server.rb:104:in `start' 10: from /usr/local/rvm/gems/ruby-2.5.1/gems/rack-2.0.6/lib/rack/server.rb:297:in `start' 9: from /usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/rack/handler/puma.rb:70:in `run' 8: from /usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/puma/launcher.rb:184:in `run' 7: from /usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/puma/single.rb:87:in `run' 6: from /usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/puma/runner.rb:144:in `load_and_bind' 5: from /usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/puma/binder.rb:88:in `parse' 4: from /usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/puma/binder.rb:88:in `each' 3: from /usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/puma/binder.rb:105:in `block in parse' 2: from /usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/puma/binder.rb:270:in `add_tcp_listener' 1: from /usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/puma/binder.rb:270:in `new' /usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/puma/binder.rb:270:in `initialize': Address already in use - bind(2) for "0.0.0.0" port 5000 (Errno::EADDRINUSE)
--
You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-s...@googlegroups.com.
To post to this group, send email to bigbluebu...@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-setup.
For more options, visit https://groups.google.com/d/optout.
docker stop "docker stop" requires at least 1 argument. See 'docker stop --help'. Usage: docker stop [OPTIONS] CONTAINER [CONTAINER...] Stop one or more running containers
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-setup+unsub...@googlegroups.com.
To post to this group, send email to bigbluebu...@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-setup.
For more options, visit https://groups.google.com/d/optout.
oot@greenlight:/greenlight# rails assets:precompile root@greenlight:/greenlight# rails s -p 5000 -e production => Booting Puma => Rails 5.0.7 application starting in production on http://0.0.0.0:5000
=> Run `rails server -h` for more startup options Puma starting in single mode... * Version 3.11.4 (ruby 2.5.1-p57), codename: Love Song * Min threads: 5, max threads: 5 * Environment: production * Listening on tcp://0.0.0.0:5000
Use Ctrl-C to stop could you tell me what to do now?
root@greenlight:/greenlight# rails assets:precompile root@greenlight:/greenlight# rails s -p 5000 -e production => Booting Puma => Rails 5.0.7 application starting in production on http://0.0.0.0:5000
=> Run `rails server -h` for more startup options Puma starting in single mode... * Version 3.11.4 (ruby 2.5.1-p57), codename: Love Song * Min threads: 5, max threads: 5 * Environment: production * Listening on tcp://0.0.0.0:5000
Use Ctrl-C to stop
2019-01-16 20:07:55 +0000: Rack app error handling request { GET /b }
#<RuntimeError: Missing `secret_key_base` for 'production' environment, set this value in `config/secrets.yml`>
/usr/local/rvm/gems/ruby-2.5.1/gems/railties-5.0.7/lib/rails/application.rb:513:in `validate_secret_key_config!'
/usr/local/rvm/gems/ruby-2.5.1/gems/railties-5.0.7/lib/rails/application.rb:246:in `env_config'
/usr/local/rvm/gems/ruby-2.5.1/gems/railties-5.0.7/lib/rails/engine.rb:693:in `build_request'
/usr/local/rvm/gems/ruby-2.5.1/gems/railties-5.0.7/lib/rails/application.rb:521:in `build_request'
/usr/local/rvm/gems/ruby-2.5.1/gems/railties-5.0.7/lib/rails/engine.rb:521:in `call'
/usr/local/rvm/gems/ruby-2.5.1/gems/rack-2.0.6/lib/rack/urlmap.rb:68:in `block in call'
/usr/local/rvm/gems/ruby-2.5.1/gems/rack-2.0.6/lib/rack/urlmap.rb:53:in `each'
/usr/local/rvm/gems/ruby-2.5.1/gems/rack-2.0.6/lib/rack/urlmap.rb:53:in `call'
/usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/puma/configuration.rb:225:in `call'
/usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/puma/server.rb:632:in `handle_request'
/usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/puma/server.rb:446:in `process_client'
/usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/puma/server.rb:306:in `block in run'
/usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/puma/thread_pool.rb:120:in `block in spawn_thread'
trwer
2019-01-16 20:12:29 +0000: Rack app error handling request { GET /b }
#<RuntimeError: Missing `secret_key_base` for 'production' environment, set this value in `config/secrets.yml`>
/usr/local/rvm/gems/ruby-2.5.1/gems/railties-5.0.7/lib/rails/application.rb:513:in `validate_secret_key_config!'
/usr/local/rvm/gems/ruby-2.5.1/gems/railties-5.0.7/lib/rails/application.rb:246:in `env_config'
/usr/local/rvm/gems/ruby-2.5.1/gems/railties-5.0.7/lib/rails/engine.rb:693:in `build_request'
/usr/local/rvm/gems/ruby-2.5.1/gems/railties-5.0.7/lib/rails/application.rb:521:in `build_request'
/usr/local/rvm/gems/ruby-2.5.1/gems/railties-5.0.7/lib/rails/engine.rb:521:in `call'
/usr/local/rvm/gems/ruby-2.5.1/gems/rack-2.0.6/lib/rack/urlmap.rb:68:in `block in call'
/usr/local/rvm/gems/ruby-2.5.1/gems/rack-2.0.6/lib/rack/urlmap.rb:53:in `each'
/usr/local/rvm/gems/ruby-2.5.1/gems/rack-2.0.6/lib/rack/urlmap.rb:53:in `call'
/usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/puma/configuration.rb:225:in `call'
/usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/puma/server.rb:632:in `handle_request'
/usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/puma/server.rb:446:in `process_client'
/usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/puma/server.rb:306:in `block in run'
/usr/local/rvm/gems/ruby-2.5.1/gems/puma-3.11.4/lib/puma/thread_pool.rb:120:in `block in spawn_thread'--
You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-s...@googlegroups.com.
To post to this group, send email to bigbluebu...@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-setup.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-setup+unsub...@googlegroups.com.
To post to this group, send email to bigbluebu...@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-setup.
For more options, visit https://groups.google.com/d/optout.
docker run --rm bigbluebutton/greenlight:v2 cat ./sample.env > env
So it gets the files from... i have no ideaThis are all the commands I used to have greenlight running without docker, see if this works for you, and then I can tell you which files I modified:
This are all the commands I used to have greenlight running without docker, see if this works for you, and then I can tell you which files I modified:
Could you tell me what files are those?
--
You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-s...@googlegroups.com.
To post to this group, send email to bigbluebu...@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-setup.
For more options, visit https://groups.google.com/d/optout.
Hi there,If you take a look at the source code for GreenLightyou'll see the sample.env file. The docker command is running `cat ./sample.env` within the container to print `sample.env` to standard output.Regards,... Fred
On Fri, Jan 18, 2019 at 10:18 AMwrote:
--
You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-s...@googlegroups.com.
To post to this group, send email to bigbluebu...@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-setup.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-setup+unsub...@googlegroups.com.
To post to this group, send email to bigbluebu...@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-setup.
For more options, visit https://groups.google.com/d/optout.
This are all the commands I used to have greenlight running without docker, see if this works for you, and then I can tell you which files I modified:
======================
rails s -p 5000 -e production
=======================================Regards,German
--
You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-s...@googlegroups.com.
To post to this group, send email to bigbluebu...@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-setup.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-setup+unsub...@googlegroups.com.
To post to this group, send email to bigbluebu...@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-setup.
For more options, visit https://groups.google.com/d/optout.
Unable to find image 'greenlight:v2' locallydocker: Error response from daemon: pull access denied for greenlight, repository does not exist or may require 'docker login'.
Found a temporary fix using nohup