GitLab / What can you do with Server Runtime?

I wanted to do something new this week. I wanted to take the existing Server Runtime / Remote Dev architecture and see what we can do with it. I will mostly be making changes to Devfiles in these updates and therefore these changes should work both on DWO as well as Server Runtime.

This is a continuation of the "What can you do with Server Runtime Series?". This is **Part 4 - Airflow**. Airflow is one of the most common tools used by Data Engineers. Typically you orchestrate ETL/ELT pipelines via Airflow. Airflow can get hard to work with when you're working in large teams. There is always the fear of overwriting each others changes. Server Runtime can create a dedicated Airflow instance from a branch or a MR that can then be used to test your changes so that you don't accidentally interfere with the work that someone else might be doing at the same time.

This idea needs to be credited to Fred who is working on making Airflow better on GitLab in the Airflow SEG.
You can find out more about the SEG at:
https://about.gitlab.com/handbook/engineering/incubation/airflow/

0:00 - Introduction
0:57 - Demo

I wanted to do something new this week. I wanted to take the existing Server Runtime / Remote Dev architecture and see what we can do with it. I will mostly be making changes to Devfiles in these updates and therefore these changes should work both on DWO as well as Server Runtime.

This is a continuation of the "What can you do with Server Runtime Series?". This is **Part 3 - Workspaces for Designers**. In this example I create a workspace that runs [PenPot](https://penpot.app/). PenPot is an excellent OpenSource collaborative tool for designers. The PenPot architecture consists of several components including the frontend, backend and exporter (written in Clojure) and database (postgres) and a broker (redis).

The Devfile for this project can be found [here](https://gitlab.com/gitlab-org/incubation-engineering/server-runtime/penpot/-/blob/main/devfile.yaml).

0:00 - Introduction
1:05 - Devfile overview and creating a workspace
2:25 - Authentication
2:49 - Penpot

I wanted to do something a bit new this week. I wanted to take the existing Server Runtime / Remote Dev architecture and see what we can do with it. This is Part 2 of this series in which I create an isolated workspace using Sysbox. The workspace is "rootless" and can run insecure workloads such as docker and kubernetes

0:00 - Introduction
1:39 - Creating a workspace
3:08 - Building a docker container in the workspace
4:32 - Docker compose example
5:01 - Running k8s in the workspace
6:32 - Workception

I wanted to do something a bit new this week. I wanted to take the existing Server Runtime / Remote Dev architecture and see what we can do with it. This is Part 1 of this series in which I create a Devfile so that I can create a dev workspace where I can make handbook updates.

Chapters
0:00 Introduction
0:41 Demo