Remote environment

In a remote environment, installation is done on the remote server and accessed by developers from their client machines.

  • Genero applications are compiled, debugged, and executed on a remote server.
  • Genero Studio Server must be installed on the remote server.
  • Allows for the preservation of C function calls/libraries and/or system calls.
  • Requires SSH access.

The relational databases that the applications access can be stored on the same remote server as Genero Studio server, or on separate servers.

You can connect to remote server files using either:
  • Samba/NFS mounts
  • Synchronization directories

Using mount points

With mount points, reference sources are stored on a remote server which is accessible to the client's local network. The local machine uses Samba/NFS to see the remote files.

Table 1. Mount Points
Option Advantages Disadvantages
Mount Points
  • Sources remain on the server.
  • Optimal for data transfer. Only files opened on the client side (by Studio) are transferred.
  • Can slow down or freeze when files are edited on fast networks (ping > 50ms).
  • Requires NFS/Samba setup on server.
Figure: Remote Genero Studio environment with mount points

This figure shows a remote environment. Developer PCs have Genero Studio, GDC, GBC, and SSH client. A remote server contains the Genero Studio Server, Genero DVM, and SSH Server, as well as Database Servers, and an Export file system (NFS, Samba) and a VCS repository.

Using synchronization directories

With synchronization directories, reference sources are on the local machine. They are synchronized to the server for building and running, and results are synchronized back to the local machine. Each user has its own temporary server directory. Because synchronization occurs in both direction (first local to server, then server to local) a lock prevents the user from performing two builds at the time.

Table 2. Synchronization Directories
Option Advantages Disadvantages
Synchronization Directories
  • All files are edited locally, so can be edited faster.
  • Preferred method for fast networks with latency (ping >50ms).
  • The server doesn't require setup.
  • Sources are local to each machine.
  • Heavy data transfer: All client files are synchronized to the server before the build, and all server files are synchronized to the client after the build.
  • Server operations cannot be run in parallel.
Figure: Remote Genero Studio environment with synchronization directories

This figure shows a remote environment. Developer PCs have Genero Studio, GDC, GBC, and SSH client. A remote server contains the Genero Studio Server, Genero DVM, and SSH Server, as well as Database Servers and a VCS repository.