Hi,

some time ago I did something similar to have a kind of POC for connecting 
guacamole to active directory and using ad for connection management. 
(https://github.com/maennlse/vagrant-guac-ad/blob/master/Vagrantfile)

But the actual question to the list...

As I like to have it as „simple“ as possible, I switched to use docker/podman 
instead of compiling from source and maintaining tomcat.

 So, is there any reason to not use docker/podman?

Maybe any Performance issues?


> On 19. Nov 2020, at 17:03, Olivier Berger 
> <[email protected]> wrote:
> 
> Hi.
> 
> In case that could be useful to some, I've assembled a Vagrant setup
> allowing to start 2 Virtualbox VMs (running CentOS) to test Guacamole
> between a Guacamole 1.2.0 server, and a desktop Linux system (XFCE),
> through RPD, with xrdp and xorgxrdp.
> 
> Its a bit raw, and was just tested a little bit. Expect inconsistencies
> ;-)
> 
> https://github.com/olberger/Vagrant-Guacamole/
> 
> I plan to use such a setup to do some tests and try to reproduce issues
> we're facing in production.
> 
> It was initially based on https://github.com/inframate/Vagrant-Guacamole
> which used the old Provision-script.sh by Hernan Dario Nacimiento. I've
> adapted it to change some parameters (mainly installing Tomcat from
> upstream).
> 
> I've actually just noticed the
> https://github.com/Zer0CoolX/guacamole-install-rhel-7 script after I
> started, so maybe this one could be used instead.
> 
> In any case, feel free to reuse, and improve.
> 
> Best regards,
> 
> P.S.: I'm new to the list, so sorry if this work is a duplicate of
> someone else's... I didn't do my homework and research the archives for
> a similar Vagrant setup.
> -- 
> Olivier BERGER
> https://www-public.imtbs-tsp.eu/~berger_o/ - OpenPGP 2048R/0xF9EAE3A65819D7E8
> Ingenieur Recherche - Dept INF
> Institut Mines-Telecom, Telecom SudParis, Evry (France)
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 

Reply via email to