Compared to the original client, it also adds some additional features which improve usability: OpenNX is written in C++ and uses the excellent wxWidgets toolkit. OpenNX is distributed under the GNU Lesser Public License v2.1. It is compatible to the original client in that it uses the same syntax for the session configuration files (.nxs files).

At the moment, I would tend to use xrdp as remote desktop access.OpenNX is an open source drop in replacement for NoMachine's NX client. hits everybody.īoth solutions need a fast network and a fat server. SVN repositories might be local, meaning speedup.Ĭon: users are not isolated (potential security issues inside of the team), an apache restart etc.

Pro: easy to use, central data storage, software updates effective immediately, central control easy. Options are a real X client, xrdp, VNC and the like. Remote Desktop: everybody connects to a central ubuntu server, using a remote desktop from there.Potential security issues due to missing security updates and users using the box as root.

Updating software (new Eclipse versions etc.) does not affect everybody unless they start to use a new vm, which leads to fragmentation or lost working time again. Pro: quick setup, isolation of the users, new boxes added fast.Ĭon: as every user has its own OS, a little hungry for hardware. Virtualization: everybody gets an own virtual box on a central, fat server.I would like to centralize our infrastructure in the future, making everybody work on a central server. We have a samba share for shared files and central SVN repositories. At present, every dev works on his local machine (some windows, some ubuntu) using a local apache. We are a small web software company (~ 10 people).

Nomachine server linux