Deployment Scenarios

From Lingoport Wiki
Jump to: navigation, search

The Lingoport Suite is composed of a number of components. You may need some of the components for a set of users and other components for Continuous Globalization.

Typical Deployment and Ports

Setting up the Lingoport Continuous Globalization System at a customer's can be done in many ways, as shown in the different deployment scenarios. The following is meant to show the necessary access to the system.


  • The Customer's systems are shown in Light Blue; CentOS for the main system where Jenkins and Dashboard reside.
  • Access from outside the Customer's system are shown in Light Green.

Deployment and Security.gif

Installation Components

  • The Globalyzer Server is hosted by Lingoport.
  • The Continuous Globalization System includes the Lingoport Dashboard although they could be on different machines. It is recommended to be installed using the Stack Installer
  • The Developer Machine is not shown in this diagram. The developer will push source code to the code repositories and may not have any Lingoport Software on their machine.

Ports

  • Jenkins is accessed via port 8080
  • Lingoport Dashboard is accessed via port 9000
  • The Translation Vendor may be accessed by different means, for instance port 21 for FTP or port 22 for SFTP.
  • Access for the Lingoport (or internal) installation team can be done in many ways, such as SSH for Telnet or Putty.
  • The system must be able to access https://globalyzer.com.

Other aspects

Additional deployments

In this section, we illustrate some possible deployments.

Team Members

Continuous Globalization

Code Verification