GitLab Incubation Engineering, 15 Sep 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Incubation Engineering Jamstack -- Update September 15th 2022

Description

Summary: https://gitlab.com/gitlab-org/incubation-engineering/jamstack/meta/-/issues/55

A

A

Just a quick update about what I've been working on in the jamsack area, I've Now default enabled the new gitlab pages onboarding screen, so that self-hosted will have the feature with 15.4 I've, also written documentation for that new onboarding process, including a troubleshooting step. If something doesn't work, as expected, I've also taken this opportunity to add documentation for pages. That explains the so-called public folder issue.

A

That's a caveat. We have in Pages where we need the build output or the finished HTML Pages Etc in a root folder with the name public.

A

This wasn't too well documented, before especially not particularly explained so I've now added an entire page about this to the documentation.

A

This also includes examples on how to configure some popular static site generators. For that caveat, ultimately, I want to remove this caveat entirely, but I think this is a very good first step with all that documentation done. I could finally write a release post.

A

That's all done and merged this last week, so we can finally say we release gitlab Pages onboarding wizard with 15.4 this week, then I've worked on the initial steps of server-side, rendering using Edge workers I've realized in the past few weeks, that I was missing some deep understanding of the differences between say, a node.js environment and a JS worker environment. This affects the way that server-side rendering applications create output and especially handle State and in turn, what is going to be possible and impossible with a dynamic gitlab pages, I forget to get that deeper understanding.

A

It's best to build something I've recently come across the information that there is no spell ticket adapter for fastly. So it's this seemed like a really good way to get a very deep understanding very quickly.

A

Just for those who don't know spell to Kit is a rather new framework that is to swelt what remix is to react: a server-side rendering framework with full stack capabilities written in JavaScript.

A

It's able to run on different JavaScript environments using a so-called adapter there's one for node.js, one for cloudflare and so on. One for Matt fastly is missing. So I went ahead and started building it. It's a very small task, so a very good way to get this deep understanding that I mentioned earlier very quickly.

A

The information I gather is obviously transferable. It also helps me understand the intricate problems users are facing that we might be able to solve. Ultimately I'll publish this adapter as an npm package, if I'm able to finish it, which wasn't even the core point of this exercise.

A

My next step is now to build an example, application that I can publish to an edge worker and then document the steps from there I can work on reducing or simplifying these steps. One at a time I'll keep you posted on the progress in two weeks time. Until then, bye.