GitLab Incubation Engineering, 17 Feb 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Incubation Engineering Jamstack -- Weekly Demo February 17th 2022

Description

TL;DR (including all MR Links): https://gitlab.com/gitlab-org/incubation-engineering/jamstack/meta/-/issues/33

getrepotype project: https://gitlab.com/gitlab-org/incubation-engineering/getrepotype

A

Hello, everyone and welcome to this week's stamp set incubation engineering update. This is a little pro quiz update. I've been busy all week getting component of the component of the new pipeline, wizard reviewed and merged. So that's great news special thanks to all the reviewers and maintainers so far that have helped polish the feature really up now. Just to give you a progress, update, there's two milestones I want to achieve the first one is to have the pipeline wizard ui as a usable as a component.

A

At that stage, it's not visible to the user yet, but it can be used by all contributors to kind of build their own feature on the pipe language, and I had split that part and down into 8. Mrs, so far we already got five of them merged and have another three to go.

A

The next milestone will then be to actually use that component in gitlab pages. I estimate that this change could take another 3mrs.

A

So that's the update for the pipeline wizard we're almost there now what else um I've spent a lot of time on those, mrs, so the rest of the time. I've just experimented a little bit some context. One of my long-term visions is a one click deploy for anything like static sites, runtimes apps and the foundation of all of that is a functionality that allows me to determine what kind of repository is in front of me like being gitlab.

A

All I know about a repository is that it's a folder of files, but how do I know whether this repo contains an ios app or a next static site or a rubygem?

A

I mean I can see what file extensions are in the code. That gives me a hint at the programming language and we already visualize that, but knowing the language isn't everything. I need to know that this folder full of view files, for example, is a next.js app. I need to know whether a ruby app is rails, so this is what I've been trying to solve. I've built a little prototype, cli tool in google, so let me demonstrate if I cd into a working directory that contains a next js application.

A

I can now run get repo type, which is the app, and it immediately gives me a json output of the frameworks up times that it has identified.

A

It can find multiple, so you see how this nox app is simultaneously a javascript project.

A

So how does it work? Well, the tool is actually pretty dumb. Its intelligence is this repository of so-called fingerprints.

A

This relies on the fact that almost most frameworks have some kind of unique file or a unique content of a specific file.

A

Each application type of framework has its own fingerprint file here, where we describe how to uniquely identify this particular framework.

A

For example, the next.js file, every nox app has a nux.config.js file, so if that file is present in the directory, we can make quite certain that we have a next app here.

A

In other cases, we might be looking at the contents of the package.json if we find the next package here, we can assume that this is a next js project if it gets more complicated than that, the fingerprint can define a whole rule set.

A

This expect property in the file is actually a rule. Object. That's pretty flexible because we can nest rules by specifying an operator.

A

If we use the any off prefix, we can specify a list of other rules, of which anyone needs to be true.

A

We can do the same with an all off or none of prefix, and since rules can be nested indefinitely, we can build really really intricate rules. Rule sets this way.

A

This fingerprint repo will be embedded in the binary, so it's super transportable, but a future version could allow the user to specify their own fingerprint repository, so they can identify additional application types for now. I only have a few application types in my fingerprint repository. This should definitely include a few more and I'm going to need some extra domain expertise for each of the more more unfamiliar frameworks, but if you want to contribute feel free to open an issue on the project it's linked below anyway, I'm super interested in hearing your feedback on this.

A

Even if you want to say this, isn't going to work, just go to the project open, an issue, and let me know what you think right. This was it for this week's update. I hope to see you again next week, bye, bye and have a great time.