Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix #1 - #2 - #3? - #5 #7

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Fix #1 - #2 - #3? - #5 #7

wants to merge 2 commits into from

Conversation

BrutalBirdie
Copy link

No description provided.

@g33kex
Copy link

g33kex commented Jul 8, 2022

greenlight_letsencrypt_api is not defined, it should default to https://acme-v02.api.letsencrypt.org/directory as for the bbb role

@BrutalBirdie
Copy link
Author

Thanks for the extra pair of eyes.
I had so much other stuff to do this week.
Maybe I can find the time later to fix and merge this.

@BrutalBirdie
Copy link
Author

@g33kex just out of curiosity, how did you end up here? :D

@basisbit
Copy link
Member

basisbit commented Jul 8, 2022

@g33kex just out of curiosity, how did you end up here? :D

You are not the only one here 😝

@g33kex
Copy link

g33kex commented Jul 8, 2022

@g33kex just out of curiosity, how did you end up here? :D

I've been using https://github.com/ebbba-org/ansible-role-bigbluebutton for a while before it was split with ebbba-org/ansible-role-bigbluebutton#272 so I'm guessing the development of the greenlight part of the role continues here?

@BrutalBirdie
Copy link
Author

Ahhhh makes sense.

Yes I recently had the need again for a custom deployed greenlight that's why I started the work on this repo again.

Nice to have you on board.

@g33kex
Copy link

g33kex commented Jul 8, 2022

I'm trying to install this along side the bigbluebutton server on the same host like the old role did, but it doesn't quite work out yet. This role seems to creates a new conflicting nginx config instead of adding a new virtual host.

@BrutalBirdie
Copy link
Author

Hmmm yes understandable.
Mostly it's recommended to keep greenlight on a separated host the the BBB node.

I have no information about your setup tho, we mostly have clusters with load balancers and only need one greenlight.

@@ -3,7 +3,7 @@ limit_req_zone $binary_remote_addr zone=req_zone:10m rate=30r/s;
limit_conn_zone $binary_remote_addr zone=conn_zone:10m;

server {
server_name {{ ansible_host }} {{ greenlight_aliases|join(' ') }};
server_name {{ ansible_host }} {{ greenlight_aliases|join(' ') }};
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be greenlight_endpoint_name? I think that's what was causing an issue on my end, since ansible_host is not necessarily the hostname of the greenlight endpoint. There is the same problem line 14.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you tested this with another solution and it works for you please suggest a change.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see the difference between greenlight_hostname that you added to setup the https certificates and the greenlight_endpoint_name that was already used in env.j2 I think these two are the same and refer to the hostname of the greenlight endpoint. I'll make an issue and a pull request later for that and add that same hostname to the nginx config.

@toabi
Copy link

toabi commented Oct 18, 2022

Is there any way already to use this role to install greenlight on the same host as bigbluebutton. I also have a v2.3 setup running which I somehow have to upgrade, but the split makes it a bit confusing.

Or is there any other good greenlight role out there? I didn't really find one…

@BrutalBirdie
Copy link
Author

@toabi This could work on the same host (not tested but you could do/test that :) ) but in a now days setup you split BBB and Greenlight separate instances.
Because when it comes to businesses / bigger hosting of BBB you normally have X amount of BBB servers which are scaled up and down (deployed/deleted) and automatically assigned to a loadbalancer and have a separate hosting of Greenlight.

Because you want to have BBB instances to be independent.
In the history of BBB, with big version upgrades, it was common practice to do a fresh setup.
If you have Greenlight on the BBB Node you would have to go threw migration and stuff.

If you want some further insights we could also start a private chat and I could go more into detail about best practice hosting of BBB. :)

@toabi
Copy link

toabi commented Oct 19, 2022

Well, I don't need a huge setup. I now use the ansible role to create the basic BBB server setup and just installed greenlight by following the manual. It was easy enough and all the state is the .env file and the postgres db. Just moved it all to a new server.

One thing which somehow doesn't work properly in the ansible bbb role is a change of the hostname. Somehow it doesn't really work until manually doing a bbb-conf --setip new-hostname.

In the future I'd probably like to run my greenlight in our kubernetes cluster but as there's not really a popular helm chart yet I'll wait for it :D

Thanks for the offer, but for now all works well enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants