11.4 Setup for Test & Production Systems GitHub (single Target instance)

This set up is for when you will be deploying your application into your own test and production systems, whether they are on-premise or in the Cloud and using GitHub for the git distribution repository.  (Also see 11.3 Setup for Test & Production Systems (Target is a LANSA Stack in AWS) and 11.5 Setup for Test & Production Systems GitLab (single Target instance)).  Deployment to Test, and especially to Production should be a controlled act from a specific machine that is solely used for build and deployment.

Only the very latest Web technology is supported. WAMs and older technologies are not supported, though older technologies may be configured to work. If you wish to use older technologies you will need to enter into a beta agreement with LANSA. Please contact LANSA Support for more details.

Presumed Knowledge

First some set up is required. It requires manual configuration. As such you require some skills in using Git, GitHub, and the Windows command line to configure it correctly. If you are an existing GitHub user it should not be difficult for you to do this successfully. It is also preferable that you have used Git Extensions previously.

Overview

You will need to create the central git repository and install and set up the target system. This is done on a one to one basis. That is, each Build Machine has its own central git repository and target system. Thus environments are isolated from each other and, once configured, can use DevOps deployment at any time without conflicting with other deployed applications.

Summary of Steps

Here is a summary of the steps involved. Click on the links for more detail:

• 11.7.3 Before you Start non-AWS On the Target System, open ports 22, 80 and 8101 and ensure port 8101 is accessible from the Internet. Setup git security.

• 11.7.4 Central Git Repository Setup Simply create an empty git repo in your git server of choice. Examples have been provided for GitHub.

• Install a new instance of Visual LANSA with all EPCs applied, and choose the options to install git, Git Extensions and Deployment Automation. This is the 'Build Machine'. Note that the Visual LANSA install will not contain the Deployment Automation option until a release after EPC142030. Until such time 11.7.5 Connect the GitHub Repository to the Development Machine

• 11.7.11 Set up the Target system with the Git Deployment Hub and the MSI and run your application on the target. This involves cloning the lansa Cookbook repository to obtain access to the Powershell scripts, and then executing one of them. Any partition may be used.

• 11.7.12 Check the Web Server Hook on the Target system by browsing to localhost:8101.

• 11.7.14 Connect the GitHub Repository to the Target system. Configuration of the git server repository web hook to point it at your Target system

• 11.7.16 Test the IDE is Configured Correctly

• 11.7.17 Deploy Your Application. Click the Deploy button.

• 11.7.18 Custom Configuration

• When you upgrade your IDE build machine to a new LANSA release, also 11.8 Update the WebServer Installation to the latest LANSA Release