Dashamir Hoxha

@acsr > like @relecand mentioned: **Save settings and recordings before running the script!** If I am able to test this with another machine for fun and peace of mind, I...

> You should be able to start/stop either greenlight with their associated `docker-compose` command. I tried these: ``` bash cd /root/greenlight-v3/ docker-compose down cd /root/greenlight/ docker-compose up -d ``` Then...

> Then I had to fix the nginx configuration: You know what? It is possible to run both gl-v2 and gl-v3 at the same time. The only nginx modification that...

> Edit the file /usr/share/bigbluebutton/nginx/greenlight.nginx and replace Actually this modification is not needed either. So, no modifications at all on nginx. Just update the `BIGBLUEBUTTON_SECRET` on `/root/greenlight/.env` and then start...

> I'm not sure about breaking up the script just yet. There are probably ways to better structure the script and split the functionality. The running of the script would...

Maybe it is not too difficult to implement. Anyway, `sniproxy` is a very nice tool, especially because its configuration is very simple.

> This doesn't fit into my use case :+1: One of the advantages of sniproxy, in my opinion, is that it is a dedicated tool for a small task, instead...

> gays, I make a docker for this situtation. https://hub.docker.com/r/zhpjy/sniproxy-proxychains In my understanding, this docker solution does not provide any advantage over running a simple command with a bash script....

:+1: I would also say: **Improve TKLDev to build Docker images for each product (besides building ISO images)** This requires a Docker image for the TKLCore, and then a Dockerfile...

Building a Docker image from an ISO image is, as you say, a hackish solution, it does not use the powerfull features of docker. The other way around would seem...