Deployment and Security: Difference between revisions
Jump to navigation
Jump to search
| (One intermediate revision by one other user not shown) | |||
| Line 13: | Line 13: | ||
= Ports = | = Ports = | ||
Please see [[Deployment_Scenarios#External_Access_and_Ports |External Access and Ports]]. | |||
= Other aspects = | = Other aspects = | ||
Latest revision as of 23:11, 22 January 2020
Typical Deployment of the Lingoport Suite and Ports
Setting up the Suite on a Customer's system 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 code repository needs to be able to work with the Continuous Globalization Server. This is done through the Jenkins jobs and Lingobot.
- The Continuous Globalization Server needs to be able to access the Globalyzer rulesets that are located either on our hosted server or on a local server.
- The Continuous Globalization Server needs to be able to send and receive resource files with the Translation Management System.
- The resource files are also stored in the code repository.
- Additionally, there are administrative needs for Continuous Globalization Server to be able to access Jenkins plugins, SMTP email, and SSH access.
Ports
Please see External Access and Ports.
Other aspects
- Jenkins installation requires access to the Jenkins update site, http://updates.jenkins-ci.org
- Dashboard may require access to the SonarQube update site, http://update.sonarsource.org
- Notifications are sent using an SMTP account: The system must allow access to an SMTP server (e.g. smtp.gmail.com for Google)