GitLab ⛅🌱 Cloud Seed, 17 Dec 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 2020-12-17 5 minute production app sync

Description

Direction: https://about.gitlab.com/direction/5-min-production/

A

Okay, let's go so. uh This is weekly five minute projection up sinkhole. My name is dmitry and my point is first on the agenda and this is a demo of what we were able to do in last week.

A

Let me start with sharing my screen.

A

Okay, so uh the main focus of uh this week was to make it work with uh ssl by default, so we kind of simplify this whole approach to certificates and don't have two different configs for http and for cps.

A

So if you go to the deploy team template to the redmi usage uh to the usage point in readme, uh you can see that template changed a bit. Now we require user to provide an email and we need this, so you can generate a correct certificate for you.

A

So by doing this, you get your application uh deployed with ssl by default, and I can show you some of example, projects that are using it right now. So let's go to the rails project environments.

A

And yeah, if we open it, we'll see that it takes the current ap address of your ec2 instance at nib.o, which is yeah domains that translate this address to the ap address and has a branch name which is equal to environment, name and it's running on the secure connection.

A

So now, right from the start right from your first use of five minute production, app, it's already running on https and you don't need your own personal domain to get it running. Now. If you want a nice domain, you can always do it by adding like buying a domain, adding an a record and taking this ip uh as a target but yeah from default. It works and it works on all environments. So if, let's say in this project, I have email environment where I'm testing the email.

B

A

And if I open it, it also runs on https and it just has a prefix of the environment name in it yeah. So that's main addition to uh just to play itself.

A

In the meantime, we recognized read me: beat fix improved security, a bit fixed few scenes and yeah one of the most important things we make the stable fit into the readme. So there is no horizontal.

B

C

A

uh Yeah, that's that's like that's where we spend the whole week. Basically,.

C

Well, the result the result is there should be proud.

A

Yeah yeah, I am, I am um yeah okay, so now there's four required items that you need to provide for five minute collection after work is aws credentials and certificate email, which is your email that you wish to use for generating ssl, and I'm going to stop screen sharing right here and yeah. It's pretty much for a.

C

Demo um thanks uh demiji, that's super cool, um I'm obsessively trying to get the number of clicks and configurations down. uh I think uh anytime. We can make it simpler. That's great!

C

I understand that forda that let's encrypt needs an email address. Can we maybe use the email address that the user has configured in gitlab? I'm not sure that gets passed through the ci job right now, but we can add that to gitlab.

A

Well, yeah yeah. We probably can.

A

We'll create a nation investigates an opportunity anyway, it doesn't change the matter of clicks yeah, but it's annoying that you need to retype and usually it'll, be the same email you use for gitlab, so yeah. It makes sense to cut this corner.

C

Yeah and also, I think, every project should get a service desk email by default. So that might be some another thing because with personal email you get maybe a bit of gdpr and stuff like that.

C

um If you expose that, but I think the service desk email, that should be fair game and then you any any kind of acme any. Let's encrypt feedback about an expiring certificate will create an issue in your project, which is like perfect.

A

Okay, that's that's an interesting idea. Can you just write it down and read me and uh not in documents document, so we can look into it.

D

Yeah, I'm just making an issue for that. I think that's a good.

A

D

C

uh So I have this in one a the note.

C

C

And then the readme says the assumption: is you have a doctorized web app with a docker file? Can we use cloud native build packs as well or how do you I'm not saying we should do it, I'm just asking how we how we think about that.

A

Yeah, I think we can use. Actually, I don't think the docker file is a requirement anymore because, uh probably for after devops, when we build like we take take a build stage from after devops and it's very likely that if a docker file is not found, it will build.

A

uh You know to make one, but I I need to check out this docker file dependency. um I have suspicion, it might not be relevant anymore.

C

Cool yeah. If so, then, let's update the readme.

A

C

D

All right uh I'll, if there are no more points on the first agenda, item I'll just uh move forward, um this one is actually from michael but I'll, just voice it out. uh He tagged us on uh issue, which is a call for proposals for hashitocks, feb, 18 2021..

D

So just adding that here we have our issue linked. We also, I also spoke to darby about it and we agreed to prepare a cfp. So there's a link for that.

B

Yeah the link is linked to the doc. Is there uh it's very, very light right now, but the uh idea that we're thinking of for this talk is to uh kind of walk through the five-minute production app as a demo, um just sort of like tell the story about why we're doing this and then and then kind of get into the technical implementations and as an uh as part of that, we have an opportunity to show off the get lab, terraform integration, which I think would be pretty relevant to that audience.

B

So that's kind of where we're thinking with this, uh if you have any feedback, uh feel free to throw it in that doc there and then we'll work on getting that cleaned up. The cfp date is yeah january 14th, so we'll get it in before then.

D

Cool uh the next one is also from michael he's, linked a few he's linked a blog post and then that blog post being shared on twitter, linkedin and the likes there's a lot of resources. There there's a youtube video as well. Just uh also, this is just an fyi point. uh Please go through them, share them like them and if any feedback please share.

D

Cool, uh finally, I have a point that I can raise, which unfortunately is also from michael, because this too was a result of an experiment that michael was doing. Michael was deploying a static, vue.js application and it there was like a bit of nginx inception going on, because uh we have a ec2 instance on which there is uh there is nginx, but then in michael's docker file there was also nginx that was exposing a static folder.

D

So uh so this led to the idea of why not have a variant of five minute production specifically for static applications, and that can be an extremely uh extremely stripped out version, because all we need is a s3 bucket to host the static files. So we had some discussions around that and I believe it is easy to implement. The question is: does it compete with gitlab pages and then, if it does, then, which way? Do we proceed? Do we want to build this at all? Or do we want to encourage the use of gitlab pages?

D

So those kind of questions? Does anybody have an opinion on this.

A

Yeah, I suggest that we just uh we create an asia and we like kind of produce this as a sub product of it like. We definitely don't need to make five minute production up template more complex because we want to bring it to the auto devops and now to devops is not for static websites. So I feel like it's just a good idea for another quick template that we can provide in a way like we provide five minute production app right now,.

C

Could be the one minute production app.

A

D

Even less okay, so then the second question is uh priorities, and when do we want to implement it? And things like that.

A

Yeah, I suggest we'll uh we'll discuss it uh next week or I don't know like right right now: let's, let's get five minute production up to the state where I uh yeah, I feel satisfied with it.

D

Cool right is here next.

A

uh Yeah, so I created the merch request: uh what it does uh it's merch request to the gitlab source code and it adds five minute production up template to the list of the templates, when you add through web editor or file, editor like gitlab.cml files, but there is a drop-down where you can choose android, ruby after devopswater kind of template and I'm adding five minute production up templates there, which is based on current state of scenes and yeah, we'll see it's in the review process right now.

A

If it gets more than great, if not like, we'll see what we can do with it, uh yeah that's fyi. I should have added it and second, one is my opinion uh on the current stage of development. So I think that we, like you, know with 20 percent of work. We kind of reached 80 percent of what this five-minute production app can do, because everything that we try to make from zero one will be like more efforts, but will be either platform specific or brings less benefits to our users.

A

So right now, in my mind, is uh we are looking into email uh because pretty much every web application need to send emails. Like I don't know you sign up information, email or whatever and uh after we managed to do that, uh we're going to revisit like you know, priorities and what what we want to do and uh who should lead the work on this and you know, and so on.

A

So uh summary of it, like demos, won't be that exciting, because it was like the majority of what casual developer like me would want from five minute production. App is already there.

C

um Yeah and I'm okay, with the demos not being exciting, I do think like most production, apps need redis and an email, so I think it's super worthwhile and uh I'll suffer through the boring demo. So far, I still find it very exciting.

A

Well, we'll we'll look into email radius, uh probably will be consideration after that and yeah and after that, we'll see we'll see what what we do from there on. But my idea is that I won't want to spend like you know. We did such amazing progress in you know one month, one and a half months and almost spent another year doing things that, like you know, three and a half people would use or anything like that.

A

C

Yeah, I think I think the current issue board is it that's that's what we're gonna do and then we need to see traction.

D

A

uh And even with current tissue board, like I'm revisiting occasionalizations, to see like what what still makes sense in amount of efforts and use and everything so anyway, if you disagree with any point, feel free to raise it or a discussion is issue.

A

uh Yeah number seven sweet is to have a scroll.

C

Yeah, um I still need to scroll.

A

C

The biggest the biggest the biggest innovation of this week, okay,.

C

I knew you were gonna say that and I was prepared just just there. I think, as I said last week, just add a space to this or something well.

A

We can just cut it down like few few symbols less it doesn't it's not it's just like.

A

Why okay, okay, never mind it's pro, it might be a browser ratio, I'm using firefox right now for work so that that might be it anyway. I will do some cross browser testing to ensure the quality.

C

Do you mind if I do it right now, I'm at a space there.

A

Yeah yeah, I don't mind, go for it thanks.

C

And then should we invite feedback in a readme, maybe link to I don't know sure we have a public slack channel, but if not like invite people like hey, please open up issues in the issue tracker or something like that.

A

Yes, I can read me: we should have the same like encourage people yeah tell us what they saying and I I think it's good to start with issue tracker. I'm I'm not sure slack like I don't know how others people do it, but I rarely use slack to to give feedback to other projects it's much easier to like use the platform. You are looking as a project at so if you're on gitlab, you already forgot an account you're already using it or trying it. We just create an issue and that's it. Okay,.

C

Let's, let's link the issue tracker.

C

Should we add our contributing file as well.

A

Yeah yeah we should we should I added a license added changelog, but it will forget about contributing.

C

Cool now 10, you probably shouldn't do, but I can't get the thought out of my head, so I thought I'd raise it should we add auto scaling so that if your ec2 instance gets removed by amazon, it auto-scales an ec2 instance back and then maybe triggers another pipeline run. This is a bad idea. We probably shouldn't do it.

A

Yeah, you know just again contribute it by creating an issue and we'll we'll look at it and tell you if it if it makes sense or not. I just deleted.

C

It immediately.

A

That's how you like kind of uh simplify your life, you just direct people through the bureaucracy process and half of the time.

C

You just gotta get it out of your mouth and then okay uh table is fixed, so it seems for on the home stretch regarding uh redis and and just read as an email. So I think that we're ready for more users- and I think michael already- did a good job inviting users, but um maybe it's. I think, what we should tickle hacker news a little bit and hacker news likes benchmarks.

C

So I think we should do a competition and take an app that I don't know, is popular and open source or some popular repo and say hey. This is how long it took me to set it up in production on heroku, and this has how long it took me to set it up with gitlab.

A

Yeah we can do such thing, but I don't know like about the time and the most important thing is like measuring. uh I don't know uh what is called in english uh anyway, a lot on your brain, and we just can compare like hey. I did. I haven't used command line interface at all, to deploy my application with gitlab with five minute production app.

A

I don't need ruby on my machine to install the heroku gm to do git push whatever like or such kind of thing, so we can take it in a different way like uh of uh not the time and because diamond probably would be on heroku side like uh we just uh do uh cognitive thought on your brain as a measurement or something like that and just yeah like.

C

I love it. Okay, like let's install the wire harness.

C

I'm sure that will attract an audience even better.

A

C

Yeah, we can call it the the no command line, production app.

A

Yeah yeah yeah. We can call it like that, no code, what it is kidding.

A

Anyway, I'm like uh yeah, I'm not I'm, not the one who who knows like. I don't like hacker news.

A

A lot like triggering them kind of things. If anyone wants to do that, like please, yeah take it and I will be glad to assist and give a comparison or whatever like help there.

B

Do you think this starts with a like a blog post, like a blog post of like the side-by-side comparisons and then yeah linking that in.

C

B

C

Yep that'd be great.

B

All right I can, uh I can try to get something going there.

C

Okay, let's see what parts of the flow we have we have this. I think we have this with this. Oh this is. This is still we need.

C

We need to red, as a male with this this this this this this this. This is the other thing that's still missing, sign in with sign in to getlab.com with your aws account. Are we uh I didn't see that on the issue board? Is that something we we want to do.

A

This is not that I want to do here right now, because uh three is good with like this terraform and everything- and this is like purely gitlab development with all stockings and everything, and I don't don't want to to do that either. I would rather create an issue, and you know, give it a product team to to work on it.

A

uh Use company, like uh you, know our engineering machine to process it, because I don't think it's like uh in our particular case.

A

uh I think that it's a lot of work and you know like uh yeah- it's not something we would be doing this for a month. Instead of all that, we've done we champion, I thought.

C

It would be easier, I thought like. Oh us, we already have five methods, so you just uh add adbr.

A

Yeah, you still need, like those secrets and everything you log in with aws, but then what like you still do? You need some api to like.

C

Together, our storyline just changed from you need an aws account to you, need aws and a gitlab.com account.

A

C

A

And like if we take any employee in gitlab and they apply for, like you know, for our uh corporate aws account and then they what's it, what they're getting is exactly those aws credentials and then that they will use to try out this five minute production app. So it's it's somewhat fine! For now the.

C

The the idea was that it's both easier to sign up for gitlab.com with your awms account, but also that those aws variables would automatically be generated.

A

Yeah yeah, I know so uh for those variables to be automatically filled out in gitlab project. You need a separate feature again that is like okay. It takes aws account that you sign into gitlab quiz. It asks users what project it wants to populate in and then it creates im user on aws through the api, gets those keys and go to this particular project and fill out ci cd variables.

A

So it's uh there is nothing like you know it's pretty straightforward, but this is like git lab development, and it's, like you know, with with proper process of product engineering, designers and uix, and everything and again it's like it's something that I would I can formulate into the issues and let gitlab implement it.

B

I just linked uh an issue that I think is uh in the issue tracker for aws authentication,.

C

So great- and I think that's regarding 11 and then dimitri, if you can make an issue for 12 with the whole im user creation, just describe what you think should happen. That would be helpful.

A

Yeah yeah we'll formulate this into the issue.

C

Yeah and the issue should be on the normal issue: tracker.

A

Yeah yeah, of course, of course, so those those are the gitlab.com plus aws. Those things are belongs to the cat lab project, so the issues will be there and uh that's one of the minority. My uh main reason why I didn't touch it at all: right.

C

Cool and you think uh yeah I won't be here for the next two weeks, I'm taking a time off. I encourage everyone else to take time off, but does someone know when the next meeting is.

A

So next meeting will be on january 7th, which is orthodox christmas day, but anyway, like the point is that it will be.

C

Yeah and then do we think we have we'll have uh redis and email by the.

A

Time uh for email, uh my plan is next week, but we don't have a demo, but I hope we get email working with freeze and I'll probably take. uh uh You know uh some few days day off around new year. If and then yeah then like january, we start looking at radius if, like and yeah- and I don't know like- maybe maybe we'll have it for seven- maybe not.

A

I don't want to plan anything for around new year.

C

A

C

D

Yeah, I would be optimistic because uh it's pretty easy to add more aws resources, so I think we can get it done dc.

A

Yeah yeah, the point is like adding those things are easy like what I'm trying always to achieve is not like you know to make it easy, uh like you know, in a way like to integrate into your application. So you don't need extra libraries, you don't need extraneous, and you saw my approach with email like I don't want people to like get aws libraries in this project if they can use some generic library for smtp and re use.

A

Aws, like you know, as as one of the smtp products anyway yeah the scene is like uh it's uh it's easy to make it happen, it's a bit less easy to make it easier and yeah, we'll see, we'll see what relationships.

C

We'll see oh good thanks great great progress and looking forward to january.