Installing and Testing A Release
This guide will walk you through installing the “Learning Replicated” application create and promoted in the previous guide. If you haven’t yet created this release, head back to the Create And Ship A Release guide and complete that first.
Now that we’ve created a release and promoted it to the Unstable channel, the next step is to create a customer license, and use this license to install the application on a test server.
A customer license (
.rli file) is required to install any Replicated application. To create a customer license, log in to the Vendor Portal and select the Customers link on the left. You will see a screen that says you haven’t created any customers. Click the “Create a customer” button to continue.
On the Create a new customer page, fill in your name for the Customer name field, and click Create customer. The defaults in all other fields will be fine – the license will be assigned to the Unstable channel because that’s the only channel with a release in it.
After creating the customer, click the “Download license” link in the upper right corner. This will download file file with your customer name and a
.rli extension. This is the license file you would deliver to your customer, if this was a real customer.
To test this installation, we need a server. I’m going to create a test EC2 instance in AWS to try this out, but you can use any cloud provider or Vagrant box you’d like. For this guide, let’s create an Ubuntu 16.04 server with at least 2 GB of RAM and 1 core.
Next, ssh into the server we just created, and run the install script:
$ curl -sSL https://get.replicated.com/docker | sudo bash
You should be able to select the defaults for any prmopts that are presented.
Once the installation script is completed, it will show the URL you can connect to in order to continue the installation.
Operator installation successful To continue the installation, visit the following URL in your browser: https://126.96.36.199:8800
You can exit the ssh session at this point, the rest of the setup will be completed in the browser.
To complete the installation, visit the URL that the installation script displayed when completed. Replicated automatically provisions a self-signed certificate on every installation, so you’ll have to accept this cert to continue. We recommend that every installation change this to a trusted cert, and that can be completed in the browser, at the next step.
On the next screen, you have the option of uploading a trusted cert and key. For this demo, let’s continue with the Replicated-generated self-signed cert. Click the orange button to continue, and then Proceed Anyway in the popup.
Now we are on the screen that expected a license file. Until this point, this server is the same as any Replicated server. Once we put a license file on it, the server will become our test application (redis). Click the Choose License button and select your
.rli file to continue.
Because this server is on the public Internet, we should put a password on the admin console. This will prevent unauthorized changes from being applied to our test application. Go ahead and enter any password you’d like, confirm it and click Continue.
Preflight checks are designed to ensure this server has the minimum requirements and environment to run the application. We didn’t choose any additional requirements when shipping Redis, so this is the default Replicated requirements. Everything should pass, so click Continue to proceed.
Finally, the settings page is here with default configuration items. These can all be changed when we ship updates, but nothing is required.
Click the Dashboard link on the top to see the default, most basic Replicated installation possible running. If you are still connected to this server over ssh,
docker ps will show a few containers, one of them is the redis container we just deployed.
In the next guide, we’ll walk through creating and shipping an update to the application we just installed.