Hi,

This is exactly what we do here. Our whole dev team environment is based on this kind of setup and this is very helpful for them but the whole stuff is quite complicated.

We have 40 devs with one dedicated VM per user running x2goserver + a stripped down MATE Desktop based on Ubuntu 14.04 LTS on ProxMox cluster. On these VMs, we deploy some dev tools such as Eclipse, Netbeans, Mysql-Workbench, DBeaver, POEdit, Firefox and a few other things. On top of these VMs, we deploy a bunch of LXC containers in order to match our dev and prod environment locally and we mount the VM's "/var/www" on these containers so that when they edit code on the underlying Eclipse, the code is immediatly visible on the containers side.

We chose a /16 vlan for the VMs and their containers, that way, they can all talk to each other without the need of complicated routing policies. The network plan is quite simple : * 10.9.0.xxx (ie. 10.90.0.200) : the VM IP * 10.90.xxx.yyy (ie. 10.90.200.1) : the VM's containers IPs and every same VM container (let's say a local proxy or an apache front) has the same IP at minus the subnet part (the "xxx" part)

Finaly, we deploy a local dns server on these VMs and with a small preg, we replace all the local-xxxxxx subdomains which normaly are targeted to 127.0.0.1 to their local proxy container.

This is needed because our devs didn't want to work in Linux so their using these environments remotely through X2Go in Published Application mode from their Windows local machine. They reconfigure their DNS settings to target the DNS server deployed on their own VM so that local-xxxxx is always correctly retargeted. This also has the advantage of beeing able to test the local-xxxxx of another dev just by reconfiguring the local DNS settings.

All this is deployed with Salt otherwise it would just be impossible to maintain properly.

This is just the global idea ... the detailed configurations are quite extensive and too long to detail here.

Regards,

Walid MOGHRABI

----- Mail original -----

De: "Raphael Bauduin" <rblists@gmail.com> À: x2go-user@lists.x2go.org Envoyé: Mercredi 16 Novembre 2016 14:10:43 Objet: [X2Go-User] remote development environment

Hi,

I have no experience with x2go but it seems to be a good fit to implement a remote development environment. Does anyone here have experience with such a setup? (Read below for more details)

I need to set up a remote development environment to be used by multiple employees of a company. The goal is to let employees work in their prefered environment. As users might need to have root access, I might go with one vm per user. That would effectively move the desktop system of the user to the 'cloud', which would be access through x2go. That way every dev can use the editor (s)he wants, compile on its vm, install packages, etc...

Would that be a workable approach? Which attention points would you highlight? If anyone has experience with this kind of setups, I'm very interested in getting your advices and opinions!

Thanks in advance

rb

x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user

DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you