Traditional (SSH) Deployments How-tos
An overview of traditional deployments using Harness.
Connect to Your Repos and Target SSH Platforms
Traditional (SSH) deployments typically pull application packages from artifact servers and then deploy to target virtual machines on a cloud platform. They can also target physical servers. Harness…
Add Artifacts and App Stacks for Traditional (SSH) Deployments
The Harness Secure Shell (SSH) Service contains the application package artifact (file or metadata) and the related commands to execute on the target host. It also included scripts for installing and…
Add Scripts for Traditional (SSH) Deployments
When you create the Harness Secure Shell (SSH) Service, Harness automatically generates the commands and scripts needed to install the app and stack on the target host, copy the file(s) to the correc…
Define Your Traditional (SSH) Target Infrastructure
Harness Infrastructure Definitions specify the target deployment infrastructure for your Harness Services, and the specific infrastructure details for the deployment, like VPC settings. In this topic…
Create a Basic Workflow for Traditional (SSH) Deployments
Traditional (SSH) deployments involve obtaining an application package from an artifact source, such as a WAR file in an AWS S3 bucket, and deploying it to a target host, such as a virtual machine. T…
