Once you have written some YAML describing your application, you’ll need to begin actually
testing the application on a test server. You can do so by setting up a Vagrant machine
or by starting a virtual machine in your preferred cloud provider.
The process for testing a Replicated application requires a bit of iteration. The key
- Promote a build to the unstable channel from the releases page
Hint: During this iteration process we recommend marking all releases as optional in
order to avoid getting stuck.
- Create a developer license for the unstable channel from the licenses page
- Download the license to your local machine
curl -sSL https://get.replicated.com/docker | sudo bashto install Replicated
on your server.
Upload your license and see if your application works as you expected. If not, you might
need to reset the server by running:
yum remove -y replicated replicated-ui replicated-agent replicated-updater rm -rf /var/lib/replicated curl -sSL https://get.replicated.com/ | sudo sh
dpkg --purge replicated replicated-ui replicated-agent replicated-updater rm -rf /var/lib/replicated curl -sSL https://get.replicated.com/ | sudo sh
For this reason we often recommend working with Infrastructure as a Service machines that are disposable during
the early development/testing phase.
If you need to make changes to your application, you can simply create a new release on
the releases page, update the YAML and then
promote it to the top of the unstable channel.
From there you return to your server & click the check for updates button on the dashboard.
If your new release doesn’t show up, there might be an error in the YAML. Then just
promote a new release to the top of unstable and check for updates again on your test