Deploy a Sinatra application

​

At a glance

​

Environment variables

​

Before you begin

• A Sevalla company with a payment method, and a GitHub, GitLab or Bitbucket account for the repository. See Git providers.
• Ruby 4.0 on your computer.

​

Create the project

mkdir storefront && cd storefront
bundle init
bundle add sinatra puma

require "sinatra/base"

class Storefront < Sinatra::Base
  get "/" do
    "Hello from Sinatra on Sevalla"
  end
end

require_relative "app"

run Storefront

​

Prepare the project for Sevalla

source "https://rubygems.org"

ruby "~> 4.0.0"

git init
git add .
git commit -m "Prepare for Sevalla"
git branch -M main
git remote add origin https://github.com/acme/storefront.git
git push -u origin main

​

Deploy to Sevalla

​

Verify the deployment

1. On the Deployments tab, click the deployment. Its Build log shows Ingot’s build plan: Ruby 4.0 from the Gemfile, Sinatra from Gemfile.lock, and the start command from config.ru.
   Build log

   ╭─ ■ Sinatra · Ruby 4.0 ───────────────────────────────────────────────────────╮
   │ Ruby       4.0                                            Gemfile "~> 4.0.0" │
   │ Bundler    4.0.20                                         Gemfile.lock       │
   │ Framework  Sinatra                                        Gemfile.lock       │
   │ Start      bundle exec puma --bind "tcp://0.0.0.0:$PORT"  config.ru          │
   ├─ Image ──────────────────────────────────────────────────────────────────────┤
   │ Build      ruby:4.0-trixie                                                   │
   │ Runtime    ruby:4.0-slim-trixie                                              │
   │ User       1000:1000                                                         │
   │ Init       tini                                                              │
   │ Port       $PORT, default 8080                                               │
   ╰─────────────────────────────────────────────────────────────── Ingot v0.4.1 ─╯
   
2. Wait for the deployment’s status to change to Deployed. The application’s status next to its name changes to Running.
3. Click the domain under the application’s name, for example storefront-x7k2m.sevalla.app. The page shows Hello from Sinatra on Sevalla.

​

Check from a terminal

1. The deployment’s status, from Get deployment (getDeploymentV3):
   curl -s "$API/applications/$APP_ID/deployments/$DEPLOYMENT_ID" -H "$H" | jq -r .status
   
   success
   
2. Puma’s start, from Get application runtime logs (getApplicationRuntimeLogsV3), which searches the last hour by default:
   curl -s "$API/applications/$APP_ID/runtime-logs?search=Listening" -H "$H" | jq -r '.[].message'
   
   * Listening on http://0.0.0.0:8080
   
3. The application, with your domain:
   curl -s https://storefront-x7k2m.sevalla.app/
   
   Hello from Sinatra on Sevalla
   

​

Deploy with a Dockerfile

port ENV.fetch("PORT", 9292)

FROM ruby:4.0-slim-trixie AS base

WORKDIR /app

# jemalloc keeps the memory of Puma's threads from fragmenting.
# hadolint ignore=DL3008
RUN apt-get update -qq && \
    apt-get install --no-install-recommends -y libjemalloc2 && \
    rm -rf /var/lib/apt/lists /var/cache/apt/archives

ENV RACK_ENV="production" \
    BUNDLE_DEPLOYMENT="1" \
    BUNDLE_PATH="/usr/local/bundle" \
    BUNDLE_WITHOUT="development:test" \
    LD_PRELOAD="libjemalloc.so.2" \
    PORT="8080"


FROM base AS build

# hadolint ignore=DL3008
RUN apt-get update -qq && \
    apt-get install --no-install-recommends -y build-essential && \
    rm -rf /var/lib/apt/lists /var/cache/apt/archives

COPY Gemfile Gemfile.lock ./
RUN bundle install && \
    rm -rf ~/.bundle/ "${BUNDLE_PATH}"/ruby/*/cache "${BUNDLE_PATH}"/ruby/*/bundler/gems/*/.git


FROM base

RUN groupadd --system --gid 1000 app && \
    useradd app --uid 1000 --gid 1000 --create-home --shell /bin/bash

# Gems from the build stage, then the code, both owned by root.
COPY --from=build "${BUNDLE_PATH}" "${BUNDLE_PATH}"
COPY . .

USER 1000:1000

EXPOSE 8080
CMD ["bundle", "exec", "puma"]

.git
.bundle
.env*
vendor/bundle
log
tmp
Dockerfile
.dockerignore

​

Deploy changes

​

Use environment variables

​

Add a custom domain

​

Deploy with the API

• An API key with the Company developer role, or the capabilities to create, read and update applications, in SEVALLA_API_KEY.
• The repository pushed to GitHub, and a GitHub account with access to it connected to Sevalla. Connecting one is a dashboard step, and the API has no call that reports it: if no connected account can read the repository, the step that creates the application fails with 400 and a message that starts with Cannot access repository and says where to connect one.
• curl and jq.

API=https://api.sevalla.com/v3
H="Authorization: Bearer $SEVALLA_API_KEY"
REPO_URL=https://github.com/acme/storefront
BRANCH=main

CLUSTER_ID=$(curl -s "$API/resources/clusters" -H "$H" \
  | jq -r '.[] | select(.location == "eu-frankfurt-1") | .id')

H1_ID=$(curl -s "$API/resources/process-resource-types" -H "$H" | jq -r '.[] | select(.name == "h1") | .id')

APP_ID=$(curl -s -X POST "$API/applications" -H "$H" -H "Content-Type: application/json" \
  -d "$(jq -n --arg cluster "$CLUSTER_ID" --arg repo "$REPO_URL" --arg branch "$BRANCH" \
    '{display_name: "storefront", cluster_id: $cluster, source: "privateGit", git_type: "github",
      repo_url: $repo, default_branch: $branch}')" \
  | jq -r .id)
for i in $(seq 1 30); do
  APP_HOST=$(curl -s "$API/applications/$APP_ID/domains" -H "$H" | jq -r '.data[]? | select(.is_primary) | .name')
  [ -n "$APP_HOST" ] && break
  sleep 2
done
echo "$APP_HOST"

WEB_ID=$(curl -s "$API/applications/$APP_ID/processes" -H "$H" | jq -r '.data[] | select(.type == "web") | .id')
curl -s -X PATCH "$API/applications/$APP_ID/processes/$WEB_ID" -H "$H" -H "Content-Type: application/json" \
  -d "$(jq -n --arg size "$H1_ID" '{resource_type_id: $size}')" | jq -r .resource_type_id

DEPLOYMENT_ID=$(curl -s -X POST "$API/applications/$APP_ID/deployments" -H "$H" -H "Content-Type: application/json" \
  -d "$(jq -n --arg branch "$BRANCH" '{branch: $branch}')" | jq -r .id)

for i in $(seq 1 120); do
  STATUS=$(curl -s "$API/applications/$APP_ID/deployments/$DEPLOYMENT_ID" -H "$H" | jq -r '.status // empty')
  case $STATUS in success|failed|cancelled|skipped) break ;; esac
  sleep 15
done
echo "$STATUS"

curl -s -X PATCH "$API/applications/$APP_ID" -H "$H" -H "Content-Type: application/json" \
  -d '{"auto_deploy": true}' | jq -r .auto_deploy