Build, Deploy and Run a Ruby Application

Getting an application running on Fly is essentially working out how to package it as a deployable image. Once packaged it can be deployed to the Fly infrastructure to run on the global application platform. For this Getting Started article, we'll look at building a Ruby application from scratch.

The Helloruby Application

Our example will be a basic "hello world" example using Sinatra. We'll assume that you already have Ruby and Bundler installed.

You can get the code for the example from the helloruby Github repository. Just git clone https://github.com/fly-apps/helloruby to get a local copy. Here's all the code for our app.rb:

#!/usr/bin/env ruby

require 'rubygems'
require 'bundler/setup'
require 'sinatra'

get '/' do
  "<h1>Hello From Ruby on Fly!</h1>"
end

get '/:name' do
  "<h1>Hello From Ruby on Fly!</h1></br>and hello to #{params[:name]}"
end

We'll call this file app.rb. We also need to install Sinatra - bundle add sinatra and create a config.ru file for Rack to start up the server:

# config.ru

require './app.rb'

run Sinatra::Application

We're now ready to run the app locally.

Running The Application

Run rackup to start the application

rackup
[2020-08-18 14:46:21] INFO  WEBrick 1.4.2
[2020-08-18 14:46:21] INFO  ruby 2.6.5 (2019-10-01) [x86_64-darwin19]
[2020-08-18 14:46:21] INFO  WEBrick::HTTPServer#start: pid=39638 port=9292

And connect to localhost:9292 to confirm that you have a working Ruby application. Now to package it up for Fly.

Install Flyctl and Login

We are ready to start working with Fly and that means we need flyctl, our CLI app for managing apps on Fly. If you've already installed it, carry on. If not, hop over to our installation guide. Once thats installed you'll want to login to Fly.

Configuring the App for Fly

Each Fly application needs a fly.toml file to tell the system how we'd like to deploy it. That file can be automatically generated with the command flyctl init command.

flyctl init
? App Name (leave blank to use an auto-generated name) helloruby

? Select organization: Demo (demo)

? Select builder: ruby
    Ruby builtin
? Select Internal Port: 8080

New app created
  Name     = helloruby
  Owner    = demo
  Version  = 0
  Status   =
  Hostname = <empty>

Wrote config file fly.toml

You'll be asked for an application name first. We recommend that you go with the autogenerated names for apps to avoid namespace collisions. We're using helloruby here so you can easily spot it in configuration files.

Next you'll be prompted for an organization. Organizations are a way of sharing applications between Fly users. When you are asked to select an organization, there should be one with your account name; this is your personal organization. Select that.

Flyctl also asks you to select a builder. Builders are responsible for constructing the Docker image of your application which is then deployed to Fly's Firecracker VMs. The simplest to use are the builtin builders, which we recommend you use here. Select Ruby (Ruby Builtin). If you want to know more about the various builders, see Builders and Fly.

The last thing you will be asked for an internal port value. This is the port your application communicates over. If set incorrectly, Fly will be unable to connect to the application and it will fail health checks and be terminated. The default shown, 8080, is correct for the builtin builders which, by design, get applications to talk on port 8080. So, hit return and carry on.

Inside fly.toml

The fly.toml file now contains a default configuration for deploying your app. In the process of creating that file, flyctl has also created a Fly-side application slot of the same name, "helloruby". If we look at the fly.toml file we can see the name in there:

app = "helloruby"

[build]
  builtin = "ruby"

[[services]]
  internal_port = 8080
  protocol = "tcp"

  [services.concurrency]
    hard_limit = 25
    soft_limit = 20

  [[services.ports]]
    handlers = ["http"]
    port = "80"

  [[services.ports]]
    handlers = ["tls", "http"]
    port = "443"

  [[services.tcp_checks]]
    interval = 10000
    timeout = 2000

The flyctl command will always refer to this file in the current directory if it exists, specifically for the app name/value at the start. That name will be used to identify the application to the Fly platform. The rest of the file contains settings to be applied to the application when it deploys.

We'll have more details about these properties as we progress, but for now, it's enough to say that they mostly configure which ports the application will be visible on.

Deploying to Fly

We are now ready to deploy our app to the Fly platform. At the command line, just run:

flyctl deploy

This will lookup our fly.toml file, and get the app name helloruby from there. Then flyctl will start the process of deploying our application to the Fly platform. Flyctl will return you to the command line when it's done.

Viewing the Deployed App

Now the application has been deployed, let's find out more about its deployment. The command flyctl info will give you all the essential details.

flyctl status
App
  Name     = helloruby
  Owner    = demo
  Version  = 1
  Status   = running
  Hostname = helloruby.fly.dev

Allocations
ID       VERSION REGION DESIRED STATUS  HEALTH CHECKS      RESTARTS CREATED
d61b5d88 1       fra    run     running 1 total, 1 passing 0        2m21s ago

Connecting to the App

The quickest way to browse your newly deployed application is with the flyctl open command.

flyctl open
Opening http://helloruby.fly.dev/

Your browser will be sent to the displayed URL. Fly will auto-upgrade this URL to a HTTPS secured URL.

Bonus Points

  • If you want to know what IP addresses the app is using, try flyctl ips list:
flyctl ips list
TYPE ADDRESS                             CREATED AT
v4   50.31.246.176                       31m16s ago
v6   2a09:8280:1:ec33:28d:5d1c:e0e9:2839 31m16s ago

Arrived at Destination

You have successfully built, deployed, and connected to your first Ruby application on Fly.