If you do not want to have Adobe manage your hosted libraries, your other option is to have Launch deliver builds to a secured SFTP server that you host.
Launch connects to your SFTP site using an encrypted key. There are a few steps to set this up correctly:
- You must have a public/private key pair installed on your SFTP server. You can generate these keys on your server or generate them somewhere else and install them to your server. See here for an example of how to generate keys.
- You must encrypt the private key with Launch's public GPG key so that you can provide your private key to Launch during the SFTP host creation process. See Encrypting Values in the Launch developer documentation for instructions and Launch's public GPG keys. Unless you know you need a different one, use the Production Environment's GPG key. Finally, you can encrypt your private key from any machine, so you do not need to install GPG on your server to complete this step.
- You might need to approve the Launch IP addresses with your company firewall to allow Launch to be able to reach your SFTP server and connect to it. Those IP Addresses are:
The structure of Launch builds has changed over time. They use symbolic links (symlinks) internally to maintain backward compatibility so that previous embed codes will continue to work with the latest build structure. Your SFTP server must support the usage of symlinks in order to serve as a valid destination for Launch builds.
There is a full guide on how to setup SFTP servers for Launch delivery on the Launch blog .
Create an SFTP host
- Open the Hosts tab.
- Create the new Host.
- Name your host.
- Select SFTP as the host type.
- Enter the host, path, port, username, and encrypted private key.
- Click Save .
When you click Save , Launch tests whether it is able to connect and deliver files to your SFTP server. It creates a folder, writes a file within that folder, checks to make sure the file is there, then cleans up after itself. If the user account on your SFTP server (the one attached to the secure certificate you provided to Launch) does not have the necessary permissions to perform this action, then the Host goes into a "Failed" status.