Staging @ AWS

Moving from the Engine Yard into the Clouds

Docker images (build)
Web UI "Click" Deployment
CLI Deployment
Deployment logs
Rails Console
Rails logs

What we need

The case of Kamal

Kamal is to deployment what handplanes are to hipster woodworkers.

It works, but it's a limited view of what one can do with the current and mature set of orchestration layers we have at our disposal.

Yet, it's simple, tweak-able and we can learn a ton from it.

It's basically an "automated developer's deployment steps".

Kryptis

Using Kamal as a boilerplate to reach our destination.

Rails 8.0 app as UI on top of Kamal.
Handles config generation, SSH, ...
Kamal is a deployment strategy (can be replaced)
API integrated
DF has the client CLI now

1

Commit

[build-staging]

2

Push

3

Wait for CI to Build & Push image

5

https://s2.designfiles.co

4

Trigger deploy with Kryptis

Deployment steps

Demo TIME

Text

until demo, the app is both working and not working at the same time

– E. Schrödinger,
some other timeline

Kryptis is ours

Work in progress

Some features are not polished yet

Own it

While I have poured some hours in there it's primarily aimed to be our tool

Don't break it

Usual rules apply: make PRs, test locally ...

1

Use it to deploy staging (AWS)

2

Polish Web & CLI

to our needs

3

Use it to deploy production (AWS)

5

Review and Iterate on the designs with testing of ideas

4

Polish Web & CLI

further

6

Migrate off Kamal

A plan

Thank you - Have fun !