Flynn is one of the most popular and powerful open source Docker PaaS solutions around. Flynn is the single platform that ops can provide to developers to power production, testing, and development, freeing developers to focus.
One of the things we love about Flynn is when you run a cluster of three or more servers, Flynn will automatically set everything up to be highly available. This means that if a server goes down, your apps and all of Flynn's components will recover immediately and keep on working on the remaining servers.
Start installing Flynn by provisioning one or 3+ new servers on Packet to be the servers in your Flynn cluster. They should all be the same type, running Ubuntu 16.04 LTS, and in the same datacenter.
Also required is an Internet-accessible domain name for the cluster (it can be a subdomain).
Once the servers are up and running, SSH in and set up a firewall to block all external access to the servers with the exception of ports 80, 443, and 22.
Once the firewall is running and your iptable rules are in place, you may start to setup your Flynn cluster. First, install Flynn on all your nodes.
After Flynn is installed you need to generate a discovery token on your primary node as the identifier for the other nodes in your cluster. In our example, we have the minimum cluster size which is 3 nodes.
The built-in dashboard can be accessed at http://dashboard.demo.packetflynn.com
When you access the dashboard, you will need to install the certificate in your browser before you can proceed and navigate through the other functions. You can refer to the screenshots below on how to install the SSL certificate in your browser, or just simply follow the guide shown in the Flynn dashboard.
We are pleased to offer a complete deployment technical guide. This will assist you through the entire process & get your first cluster up and running.