Skip to content

Video Tutorial

Yuxiang Huang edited this page Sep 14, 2026 · 4 revisions

The following link is the video tutorial for ScottyStack: https://youtu.be/lMqBaOAAArk.

Transcript

0:01: Hello everyone. So welcome to the introductory video to Scotty stack and like just introduction to like Labador

0:08: tech stuff. So my name is Yuxiang. I'm a head of onboarding and documentation for this year Labrador 2026 to 2027.

0:16: I'm Haresh. I'm head of engineering for Labrador. And I'm Sam, head of AI from Labrador.

0:21: Okay. So you guys see our faces so we can let's get started. So first thing you want to do in Labrador when you want

0:29: to start a new project is to uh make a new team in goador. So god dooror is the skylabs lavador governance system and

0:36: you can see all the instruction here you can learn about like all the permissions you have and then here register you want to do all those steps and then like

0:45: create a fork and add yourself and make a pf to review. So for the simplicity of this demo I'm just going to like commit straight to man so it's going to be quicker. So today we're building meet.

0:58: So what it is is basically when to meet but for skylass. So I'll talk about the idea a little later. So you want to make

1:05: a new tunnel file in the things folder and then if you have right in extension installed it should like tell you like everything you need. So I just going to

1:13: copy everything from here. Uh this is going to be uh meets

1:21: when to meet for Sky Labs. And then let's change this meet. Uh those are your website URL uh server.

1:30: You can just select to rent uh random URL like just empty for now if you're just uh if you don't have a website

1:37: server yet. And then repost we need to create a repo ourself. Time frame the same thing. And if this is your first time making a team um like first time

1:46: you want to also add yourself in the members folder here and then let's save it and in GitHub

1:53: desktop let's create go to okay feed team add a meet team and then we can commit to man.

2:04: So this adds a new team. Yes. Mhm.

2:06: So this is like what you want to do again like ahead of like in boot camps we teach you guys how to like use do like a fork and then like make a PR and

2:14: we will review it oursel but for simplicity we're just going to commit straight to man for time sake. So let's see uh

2:22: so let's create the thing for website and server you can just leave it as empty string because you will not have a domain in the beginning of the semester.

2:30: You just develop locally first. So this is go to door really quickly.

2:35: And then here in the repo something failed

2:43: uh because the GitHub repo was not created. That makes sense because you want to create your GitHub repo. So let's go to Skyabs Labador. this link

2:52: and then everybody who's a you in the first book can you add yourself and then this will give you permission to create

2:59: repost in the Skyabs Labrador GitHub organization and after that you will create another PR to add your team and

3:06: all the members so it's helping two steps so you will have the permission to create a repo by then so I just call it meet uh oh so when creating a repo you

3:16: can use Scotty stack so this is our recommended stack this year for And then in the quick starts there's a link you can just press on it and it will just

3:24: create a template using it. So here uh owner you want to choose Skyab Labador meet. So this will create and then you

3:32: can make it just private should shouldn't be anything secretive and then we can just create a repo right now.

3:39: I'll call the camera meat looks better.

3:44: So this is generating the repo from a template for Scotty stack. So here you can and anytime something fails you can

3:52: just in the PR as well you can click into it to see the details. It should have a very like easy to rerun. It just says oh this repo is not found. So makes sense and you can just always rerun it

4:00: using this button here. Uh if you don't have permission to rerun it uh you can always push a new change new commit on the same PR. Do not make two PRs for the same thing.

4:12: Okay let's see. Okay we have meat. So it has like oh my god so many things set up already. I'll go through them in the rest of this video on like what each thing is. But let's first just like corn

4:20: the repo just regular get stuff. Let's go CD into Labrador and get Chrome this corner repo.

4:31: Let's see. Uh this thing finished running. Perfect.

4:35: Oh, perfect. Uh let's see. Uh everything's running. Everything's running right now. So this will provision you a lot of things which I'll

4:42: go over in a second in God. But for now let's open GitHub desktop add existing repository

4:50: scalas have whole lot of scal but this one's in labador emit and whether you capitalize or not capitalize is like

4:57: fine anyways open it repository. So this is our GitHub and then let's open a cursor as well. So we recommend cursor

5:05: because you're going to get like one year of like pro for free and you also get half half a year of pro plus for free if you're a CMU student. So more

5:13: details, we're going to send out the links on how to register in like boot camps and the emails. Okay, let's done with gold door. So we can open another

5:20: one for I hate how they open this. I just want to open the repo.

5:28: Okay. Uh Lavador meets.

5:32: Okay, we have everything here. So let's wait a second and then let's return back to this. Let's see if everything finish running. Let's go.

5:41: Everything passes. Okay. So let's go over everything you have that you should check for. So as a member

5:49: in the first work section you you add yourself as a member you you'll be member of a GitHub organization contributor to our Google drive and also

5:57: a member of our Google group team. So Google drive you're going to put a lot of your team documentation inside your folder in Google drive in labor folder and member of the Google group is also

6:06: good because you're going to receive email updates from us as like labors skylab.org. So this is for the email updates. This is to store a lot of your

6:15: file meeting notes. We also have documentation on like what to use to like do what kind of documentation like Google Drive is from meeting notes. And

6:23: then like you you're going to have a wiki for like your repo documentation similar to like Scotty Stacks. Like

6:30: Scotty Stack has a wiki. Let's put that up here.

6:34: That's all the documentation here. So you want to use that one. And like you you also want to create a project. Oh.

6:40: Yeah. You also want to create a project because uh this is going to you're going to do all your like scrum meetings. I like to use the second template comb

6:47: board just rep and then create projects on this stuff. Yeah. Also make the project public.

6:56: So this is like where you're going to do a lot of like the spring planning. You guys will cover that in boot camps. What? Like spring planning, agile development.

7:05: Oh yeah, that stuff. Yeah.

7:05: Like lo stuff like you're going to put your tickets there. Mhm.

7:08: So this is a lot of like where where you should put each thing and then as team member you're going to be a part of a GitHub team. So you're going to receive a email telling you you're going to be

7:16: in the Labor GitHub team. So one way to check is go to Sky Labor organization in teams. So in the new team it should be

7:23: called meet. So I'm in the meet team and like meet elements. I'm like in those teams like you can see it right here.

7:30: And what else? Scotty Labrador. Yeah. And then uh GitHub repo keycloak.

7:39: This is for O. I will talk a lot about O later. And then here, this one's important. Open bow. Also, you're going to get invited into your team stack

7:46: channel. We're going to create a channel for you and add you and everybody in the team to it. So bow, open bow. So this is how we manage secrets in Skyabs. Like we

7:54: do not want you guys to like slack secrets to each other, put in Google Docs to share it. So what you want to do like an Instagram group chat, we definitely don't want to do that.

8:04: Yeah. So what you want to do is uh in Sky in uh in secret management there's instruction how to do it.

8:12: So you want to open this link and uh okay I'm going to sign out so you can sign in with OIDC provider

8:20: and then here because I'm admin have permission to everything but for you you should only see one project the one you're in and you can see all generated

8:27: uh secrets. So there's like four environments for a labor project.

8:31: Usually you're only going to use local and prod for now. Local is for local development. Prod is for like production use. So actually you're going to use

8:39: local until you're ready to be to to deploy your projects. And um staging is like when you do a PR merge, you can use

8:47: staging if you want to. That's more a little more advanced. Deaf is like you rarely use it. It's like you want to fix something on the PR and you don't want to conflict with the staging branch.

8:57: Yeah. Yeah. like working on something a PR is staff and then you merging to staging and then you promote from staging to prod. That's like how a real

9:05: life project like really like deployed one will work but for now just focus on local and prod it has your ID and secrets. Uh I'm recording now so I'm not

9:13: going to show you the ID and secrets but you can copy them like this.

9:17: So yeah this is how you're going to see all your secrets and managing the secrets is through secrets back. So for

9:24: example in like server you can see that we have like all those default value for you. There's a lot in this file

9:31: description for each of them like ID it come from here. So you do not need a MV file because secret spec will automatically pull the secrets from open bound to your local running process.

9:42: It's just all automatic. You never need to like you basically don't need to worry about it. Any question on that?

9:47: No I think that's yeah that's how we manage the question. How did you sign in through open bow to so once you sign in

9:54: there how does your repo already know to go to open bow my repo? Oh so it get connected how it connected so like let's like here

10:02: uh in secret spec we mention like which way it is like there's a URL right there. So this connects through labor one

10:11: so it works once as long as you're in labor.

10:13: Is there any way that it connects to individual members?

10:16: Uh it doesn't. So basically what you can do is like you can change like the ref.

10:20: Mhm. So you have a lot of ref items. If you change like but like the issue is like this file is like it's on git. Yeah.

10:26: What you can do is you can change something this file. You can change the default values or like just delete ref and then just use the default values and then use it locally and just never push that file.

10:35: So you can use your own secrets that way. Yeah. Just make sure to not push it. Get ignore. Yeah.

10:39: Because like merge that much conflict that way.

10:41: Yeah. Get ignore will not work because this file is like staged on get already.

10:45: So you can actually ignore a file that's already like st like already pushed. And then um if you want to let's say add an open router key, how would you work through the process for that?

10:53: Oh like a open router key. Yeah. So so just make like a fake key like one two three four. Say you want to add it.

10:59: So like a new key, right? So you want to add it to the corresponding one. So let's like there's multiple secrets back like server the front end back end and DB. So you want to add it in the correct

11:07: place and then you want to add like every time you see it, you can add a default value here. You can add a local value here. And you want to add a new

11:14: value inside your team. So not make a dummy version where's meat. Meat is right here.

11:21: So you want to create a new key and you want to put like web ser like let's see the format. It's like local server. So

11:28: you want to do like local server and you put like k andv and you want to just like save it. Mhm.

11:36: Okay.

11:36: So this is how you can do it but everything is in the UI and it's pretty pretty easy to use like like this thing where you self-host. Yeah.

11:42: You mentioned different kinds of secrets. So is there like secrets for front end and back end or is it just like one sec one place to put all this?

11:48: There's two place like there's like Scotty stack local server and there secrets back uh local web.

11:56: Okay.

11:57: So the the item you put just different location it's a folder. Okay.

12:00: So wherever you put it will be this is a folder this is like a field. So you want to put in the exact same place.

12:06: Okay cool. And one as I noticed like one thing you really want to do as your first step is just replace just do uh you want to exclude all the MD files

12:14: because they have good links like links in them which we don't want to break.

12:18: So you want to do this and then remember to put on the case match. So you want to replace all Scotty stack with Scotty stack sorry with meat and then there is

12:27: scotty stack capitaliz which you want to replace with a meat which is like more formal. So this is what you want to decide on a name for your project and then do that.

12:34: Okay. Uhhuh. So we will do that first and go to the uh oh yeah so one thing

12:41: about it I didn't mention is let's go here ad meet team. So right here you can see like the name of the repo. Sorry the

12:49: name here basically you want to use the name here in your tamo file is your team slug. It's called a team sl you want to use that in place of the lowerase scotty stack.

12:57: So you don't want uppercase lower case because there's a convention for like the team slug. You can use hyphens instead. And then here the name you want

13:05: to use the cap like this one you want to replace the capitalized Scotty stack basically. Okay let's see uh amazing you

13:12: know that can be our first commit we use conventional commit here. So you can read about conventional commit on this page called conventional commits.

13:22: You want to like you can read about it.

13:24: Basically this is a troll and like you can put like in it and be like renames

13:30: project names and then you want to if I commit now oh that's really quick.

13:36: So you see right now committing is really quick but uh one thing you want to set so you want to set up your repo.

13:42: Now what do I want to do? Set up my repo. So one thing you can use is dev containers.

13:48: So I mean let's go to rei. So that's the first thing I want to talk about the quick start.

13:55: You can use a dev container which basically only requires you to install Docker and one like VS Code extension.

14:01: You can Oh, there's a push. You can do you can do command shiftp command shiftp bring up this on Mac and

14:10: then you just want to do reopen in container. What it would do is you it will just automatically set up like it will create a DB for you in Docker and

14:18: like copy over all your files do a bunch of like configuration for you. You'll create like you'll create like a a homebrew like image. So it really

14:28: probably works better for uh for Mac because Mac use brew for installing things. But if you have Windows Windows question you can ask our like two people

14:36: like like Hash and like Sam who you have both have a window computer. So um and it will run through this post create

14:44: script that will install everything for you. you install bun. You'll set out the bun completion like like this like all

14:51: the completion stuff and then install all the dependencies. Uh it'll install more things for you. Install more things more things.

14:59: It's just install everything even do the DB migrations for you.

15:02: So just a really good way of getting started on project if you have nothing installed. But another way you can just do it is like if you have a Mac computer, if you have homebrew, you can

15:10: just do uh what is this? Postr you can just run a script like outside which will install

15:18: everything for you as well. So right now it's doing the bind install. So I don't want to really use another like dev content because uh I just have

15:25: everything set up already. So it's fine for me.

15:27: But basically install everything. If you have a window you just want to go through each of those links like I have all the links here. You just want to follow the window instruction installing everything. Oh even log into open b for me. So it has access to all the secrets.

15:39: So it has all my permissions. Oh, maybe I should not show you the token, but it will probably expire by the time I post it. How many days things that is like it

15:46: has show you all your permission. Make sure you have like the one you register for such as like meet admin and meet for me. I should talk a little bit about

15:55: that. So each team will choose a team lead. They have more permissions. They will do more of the DevOps stuff. They like probably they'll review PR for the

16:03: team members. So you'll probably want to choose the tech lead then. But we'll talk more about that in the info in like the first for session because yeah it

16:12: probably change year to year. Anyways conventional commit done you set up everything. What do I want to do now? So

16:20: uh any questions so far while I figure out what to do on like setting up things.

16:27: Um so what was the thing with so the docker thing is like already set up but you also have to install that right?

16:32: You need to install Docker. Yeah. Like prereg is like install Docker for your computer. Mhm. So yeah, good way of learning Docker.

16:39: Uh, okay. So, okay, I I I don't remember next step. Next step is like see if your thing works, right? So, okay, here's the issue. Okay. Oh my god, DB migration

16:47: failed. Why? Because I don't have a DB because the DB try to use here is let's look at the DB try to use here. Secret spec DB. You try to use this one in

16:56: Postgress. That one is set to the this one is set to the how should I say like the darker one. So, I it's default to

17:04: that one. But you I have one running right here in postquest like the one for Mac. So I have a I created DB already meat.

17:12: So I just want to uh change it to local host like so it uses the one locally. So now I can rerun all of this. Hopefully

17:19: it be faster this time. Yeah it's like skipping a lot of steps. Oh my not skip the logging.

17:27: Usually you loging once you just save it locally so you don't reloging every time. this done. See the DB migration passed this time.

17:35: Actually, is that a DB migration here? Migration applies successfully.

17:40: And then you just want to make sure everything succeed. Oh, let's say yes.

17:43: Everything succeeds without like things like like a X and like exit code one. Yeah.

17:48: What is this? This installing more things. Now, this thing I'll just push.

17:52: Okay. Uh and while I push it, I'll I'll show you something interesting as well. I'll make a note. I'll make a push soon.

18:00: Okay. Perfect. So now what we want to do is like make sure everything works right. So first you want to check if your DB works. So you want to cd the

18:07: package DB and you want to b run using the tab key. You can do the completion which is which we get set up

18:15: for you. You can run DB studio. So this is a good way of checking your database.

18:21: So you can go here you can see your entire database here which is empty for now which makes sense but make sure you can see this page. Usually you want to

18:28: implement like a seed function like a C.ts. Uh oh yeah Scotty stack has uh two

18:37: has branches. There's a demo branch which is the one that get deployed on stack.skylaps.org that has like everything has like a

18:45: functional like a foreign which is used to like test like if scotty stack actually works.

18:51: And so this one has like more details like for example there's a c.ts ts which you will probably implement that just like se your database with data so

18:59: that's one thing you can implement but that depends on your project what should I see okay so first you want to make sure the studio is running so

19:07: you can access database and then you can run bundev in the root so b run dev will run the

19:14: web and the server together so you can see your server is listening on port 80 and this is your front end right here so

19:21: one thing you can check is like if the signing works yo The sign works. It knows that I am. This is my email.

19:28: And know it knows that I'm an admin as well. So the techd will see the admin dashboard and everybody else will not see the admin dashboard.

19:35: So if you go to the admin dashboard, what's on it by default?

19:39: Just like the usernames, all the users in the app. Okay. So yeah.

19:43: Oh, how do you add new users? Do you want to go over like the adding team members? I know you talked about it on Oh. Oh yes. So in Oh, team members.

19:50: Key already set up now. Yeah, Kiko is already set up for you. Okay.

19:54: So team oh team member just go here like tammo in the team. So say you want to add someone new then you go here

20:01: and then you just follow the tamo format and you add another like members and you add a github name usually there's a title I can see a better example

20:10: which is do we have a good one something like title you'll put a title it's like optional just if your team wants to have it

20:17: okay and just like go like this like each entry goes in here if you install an extension it will tell you like you see the rest if it doesn't work

20:25: okay cool so once you add it everyone gets automatically added to um added to everything and they're able to log into the website and have access accordingly.

20:34: Yes. Cool. Okay. Let me see.

20:35: So, this part has their GitHub but not their Android ID. How does it know their Android ID?

20:40: Oh, it's in like the top in the team e members in members. You tell them your Android ID. Connect the Android. Okay. Cool. So, it's required.

20:48: So, there's two places you have to add yourself.

20:50: Yeah. Uh yeah, you want to add yourself in the members in the first boot camp and then like after you create your team, you can create other one. Okay.

21:00: Okay.

21:00: How does it link the two link?

21:04: Like if you add yourself as a team member with your GitHub and you or your android ID and your name and then you have your GitHub and your title. Those three are two separate things, right?

21:14: So how does it link?

21:15: We can walk through it like this is the implementation detail of Golden Door in that point which you don't need to concern yourself of. But basically listing is a key, right? You know your

21:23: GitHub. So you go to members and then you go you have a file called us.com so you can access it.

21:28: Oh it's like a hash table. It's like a hash table implement implementation detail of go to door.

21:34: Yeah go governance for lavador go to door. Mhm.

21:38: Okay. So next step we're going to make a push. I just realized that.

21:42: So let's do like ch init update uh db uh URL. So you'll notice this time will

21:50: take much longer. It's like taking much longer. Oh, something even failed. So let's see.

21:57: So one thing to do is like here you can do control shift P. You can do task run task pre-commit hook. So after you

22:04: install B install it will run a precommit hook every time you you every time before every time you commit it will run a pre-commit hook. What it runs

22:13: is everything here. You can comment everything out if absolutely necessary you want to commit something without going through a check but those will

22:20: fail the CI checks on GitHub as well. So like the CI check on GitHub is like uh let me go to repo meet

22:28: Scotty labs. Uh let's just go to labor first meet. So those are the CI checks here.

22:37: Even if you like force push like if you force push that like without going through the commit then these things will fail and your team member will be mad at you. Mhm.

22:46: Don't make when you open a PR, make sure everything all the checks are passing. CI/CD basics.

22:51: And then let's see. Uh because I Okay, that's fine. Let's see. Uh what was I talking about this, right?

22:59: Oh, pre-commit. So, pre-commit hook fails. So, it does a lot of checks. So, we know this one fails specifically because it was running this like you

23:07: would know like which one failed like sync pack failed. So, we can run it run sync pack. Uh okay, we need DB folder.

23:14: So we need to run from root. So it's saying like things are not sorted. Why?

23:18: Because we scotty stack to meet and s and m are not the same letter. So you can run a different command. You can see all the command package.json in the

23:25: script. You can see all the commands here. There's a sync pack fix command which is automatically fix it for you.

23:32: Basically you can see in git it just sort everything for you. Yeah. Keep your things. Mhm.

23:39: So like Yeah. So now we can do another commit here. You can also commit in a command line. I have a I have a alias

23:46: setup that's like GAC just commit everything. So you can see everything actually running here. So it has a so you don't need to wait with a blank screen if you don't like that. But there's some bugs like this one. Okay.

23:56: It's like trying to run all the tests.

23:58: We have an end to end test. Oh my god, so many test tit uh update DB URL.

24:10: Yeah, usually if your team member uh if your team member can choose which one to use again, just like specify here and don't commit it and you'll be fine. And then just don't put something here.

24:20: Yeah. Okay, perfect. Uh this is a bug.

24:24: Okay, we're done through the initial setup and now it's time to use AI. Mhm. Guys, it's AI time.

24:33: Wait, last thing. Uh when you did that, you said you need to not commit that file. Uhhuh. Which file specifically?

24:40: Like the secret spec like if you want to use a different secret than the rest of your team. Oh, okay.

24:45: Like someone want to use like the Mac thing. Someone use one window thing.

24:50: Someone to use like the Docker thing and this file get committed. So like you just don't want too much like merge conflict all over the place. Okay.

24:56: And even if there's a problem like this file is so simple. I think merge conflict on this file will be easily like fixable.

25:02: Okay. So for the rest of the session, we want to go through uh let's let's pause right here.

25:14: Hello guys, welcome back to part two. So at part in part two, what we're going to do is we're going to use AI to implement the app actually called when like sim

25:22: like meets skylass.org and while AI runs, we're going to have like a Q&A again go through like this like wiki section basically each part of it. So

25:30: let's start it. So first part, how to prompt.

25:36: That's uh what's the key? Okay, let's expand it so it's larger. Let's look at AI section. Oh my god, we have context in agents.m MD file. What's in agents MD? Oh. Oh, just links to Scotty stack.

25:48: That's why I told you guys to not replace the links because the link will be broken if you replace this.

25:54: What else? Skills. What skills are we using? Oh, we put all of our skills in the Asians folder. There's so many skills. What are they? It's this AI

26:03: hero.dev. So the issue with AI is that like things change so often. Like last year people told me about like what is an MCP server. This year everybody's

26:10: like told me about the skills. So like we don't we don't want this like to be limiting. But this year we just want to use like this amazing resource. Found

26:18: this person. You can find him also on YouTube. He make a lot of like teaching videos. So he's like up to date. like he

26:24: has like a repo like Matt P uh Pak skill and he has like let's see how many he

26:32: has like a skill um skill repo he has like 254,000 stars it's like one of the most star repo and like like his gui gmy

26:41: like ski if you heard about it was like the meta like skill like it was really good skill like everyone was talking about it in the past few months like gui skill so we're going to use this one for

26:49: now so does it auto update like based on like Scotty's stack uh we need to update Scotty stack ourself but like you can install it very easily. There's a command on this page

26:57: where just install and update all the commands.

26:59: So we need we can just trust this guy with get his things out. Okay.

27:02: He makes so much money with AI courses nowadays.

27:05: Yeah. So he's just going to use his skills. So you can restore like this is a good like resource to just go through like so today we're going to go like the main flow. So we're going to grill with

27:14: docs and then change it to a spec and then change to GitHub tickets and then implement each of them and it will be code review for each of them. So let's

27:22: look at so and then we also have a code rabbit for um for for like code review stuff. So every

27:30: single those like dot files is like a config file which we set up for you.

27:34: This one's for co- rabbit. Uh hopefully we have enough usage for everyone. Co- rabbit is our sponsor. So hopefully give us some credit. So each of you get some

27:42: AI reviews in your PRs. I think it's running sometimes. uh if you want to use like basically if you are chat if you want to build a chat chat or something

27:50: we give you like open router keys so you can like call LMS for your users and then I told you guys like the AI credits for developers is like the stu the

27:59: cursor students there'll be more resources on that updated by head of AI later okay

28:07: send out the prompt oh yeah oh no uh so we want to I just explaining like what to what to like before we send out prompt let's enlarge this so first

28:14: we want to do great with dogs docs and then just like write as much as we want on this. So, what's the key?

28:22: What is the what's the what's like the talking button? Like the the whis thing. Whisper. Yeah. I don't know if cursor that's built in.

28:29: Just use your like the Mac version. Oh, it's right here. Oh, okay. Here it is. Okay. I guess I need to do this first.

28:35: Okay. Uh build me when to meet. But for

28:42: actually, we just need to build when to meet. Yeah. Well, I say to be when to meet, right?

28:47: And say don't like don't add unnecessary code because we want this to go quickly and also we don't like Yeah. Why don't you do a when to meet

28:55: where it links people's Google calendars as well.

28:58: There's too much features. Yeah. Create when to meet with the existing with existing o system.

29:06: Okay.

29:06: Yeah. Because we want the default O is like you can it's like the default as you see is just logging

29:13: through SSO CU like SL so because in to meet the actual website you you create a password for every one of them who's who's been creating your website like

29:22: uh so you you some you mostly want to like discuss with your team initial idea and do a like do you want to link the when to meet like website

29:31: I'm sure I know when to when to meet okay and then let's just do this oh wait uh we want to do plan mode.

29:38: Mhm.

29:40: So they will run. So like what model are you using?

29:42: Uh I just use the default one, but you can use like a better one. This one. 6.

29:46: Oh, okay. Wait, how do been doing pretty well? Like actually I use like Opus. Opus takes longer. This one is very fast. Yeah, faster now.

29:54: Yeah, we're faster than now. Yeah. And then my usage like use like I use Opus yesterday to build like Wikipedia Sky though use like 50% of the usage.

30:02: Oh, wait. I have like fair. You have pro plus. Yeah, it's my last month doing Pro Plus. We have Clad Max.

30:09: We have Cloud Pro Max startups.

30:13: Oh my god, I should have go to I should have went there, bro. What am I doing?

30:17: They give us like I was I was in the $3 a month for six months a month, bro. It's like insane, bro. I needed that. Oh my god, that's I need to go to like the court like

30:25: what's the one with resource? You need to tell me resource to give me like some credit. I need to go to this build. Okay, wait. Everything's in my notion. I'll add it in.

30:32: Okay, I just add it after session. Yeah.

30:34: So right now like AI will take some time like looking through your codebase looking through what is happening and then like uh what we do it will like ask you questions and you want to answer

30:42: with your team. So initial session like you're going to get your team together on the initial v vision and then so you guys can create tickets and then you can

30:50: assign a ticket to each person in your team. So that's why how you vision you guys going to work as a team skylabs lavador.

30:57: Uh why roster can go through those things. I think we went through the first page home. Welcome to Scotty stack

31:03: wiki. Yes, philosophies. Uh you can read through this. I don't think

31:11: it's I don't think explain any of those but like we do not use ros for back end.

31:16: And uh for a third party oh this is uh so for development for deployment we usually if you use a we use railway if

31:24: you don't use we're going to demonstrate how to deploy our app also in the next session in a few minutes in the end of the session. But uh if you want to use your third party service, it's okay.

31:33: Just like make sure you maintain yourself and it'll be harder for you to move to tech that way because tech has a standardized like in like a standardized way of doing things. So if you use like

31:42: g cloud platform and tech doesn't use it. It's like a hassle to move off it.

31:47: It's right here. So let's use a home and uh oh yeah we have some wiki.skylabs.org now. So you can ask any question you have here. So what is

31:56: okay Scotty stack?

31:59: You ask questions. You have like 60 prompts per minute and just like totally per per hour. Per hour refresh every

32:07: hour. Refresh every hour. Yeah. One one per minute. That's what I meant to say.

32:10: Yeah. Side the document. You can see like to fact check it. Mhm.

32:14: Yeah. We need to add more documentation there.

32:16: And then okay, let's go to uh I think Oh, I heard a sound. That means cursor is finished.

32:22: So um Oh, who is this for? Okay. Yo guys, what is this? Which one it is? CM community.

32:31: Yeah, recommended.

32:33: Alice, quit a poll and text Bob the link. Bob is not signing. What happens when you try to mark availability? Sign in required to create. Yeah.

32:41: Yeah. Sign required. Yeah. What should we call a thing people? Oh, this is like a good thing like this skill will ask you on like terminologies. So, it's good for you guys. Yeah.

32:50: So, um Okay, let's make sure. So, repo is meet when to meet cause an event. Meeting is

32:58: easy to confuse with a calendar occurrence event. Let's just call events. Okay, sure. Whatever. Recommended.

33:05: What you keep recommended. Make sure you unread it though. Yeah.

33:08: What must the first version to do to count as done? Yeah. Just a cool feature. That's the basics. Yeah.

33:15: Okay. Do we need over qued share mark availability see overlap? Yeah.

33:19: Plus organizer fix the final time, right? Don't you want to do that?

33:22: No, we that's too much. Yeah. Just we don't want to deploy as fast file.

33:25: Mhm. Well, we only have like 40 more minutes here. Yeah.

33:34: Yeah. I heard a sound, so I know like curses down because I'm notifications on.

33:38: Yeah, I should be careful opening this. I like I have some like personal messages there.

33:42: Okay, let's go through. Oh my god. Do you want to go through O, guys? O is so hot.

33:46: O, I think O is the O is like so hot. Okay, maybe we should make it a new session. I think O should be its own recording.

33:51: Uh, we can like we can like we can split it out. Okay. So this session is like this thing. Okay. Let's just do all in the end. Okay.

33:59: So for back end we use express because everybody know express. It's pretty very popular the most popular TypeScript back end and then TSOA. So this thing will

34:08: generate a open API spec for you. So you can go go to like see what it is. So like let's see example.

34:17: It's like swagger UI. It will create this. So basically see all the end points. Click for the cursor.

34:23: Yeah. Yeah. Yeah. Let's see what curs answer. Alice creates an event and PS a link in Discord. Charlie CMU signing opens it. Dana not CMU. Who is allowed

34:32: to view and mark availability? Why is ask me that question again?

34:35: Wait, no. It's saying like uh people now saying CMU versus non CMU. Okay. Who is signed in? Right. Yeah. Just Yeah.

34:43: Event not sign in. What should CC?

34:46: Uh signing war. That's just a signing war. Yeah.

34:49: And then specific days. Oh, this one is important,

34:56: bro. Let's talk too much. Send as when to meet. You should not do this. Yeah.

35:03: Yeah. You You guys should not do it because you should build a actual product, but we just want to do a demo and like replicate when to meet here.

35:11: Bro, it's asking about the time zones.

35:14: Wait, let's just put it in New York Times so it doesn't actually.

35:19: Wait, because that means it's going to like auto check your like current location time and accordingly.

35:23: Okay, just do this. Yeah, because we all in Pittsburgh. Yeah. What can they store? Yeah. Express. Yeah, let's just do this.

35:30: Two two options. Heat map. Yeah, let's do this. Continue. Okay. Okay. Let's just like open API.

35:36: Wait, maybe we should have just prompted Claw to give the full spec of when to meet and just pasted that, bro. We should we should do that. Yeah.

35:43: Okay. API documentation like this one give you like swagger UI. This one has a JSON specifications. So we with um error

35:52: handling we recommend use like something like never throw but it's fine and like database we use postgress SQL set up in

35:59: different ways as I explained before al mac or like on docker database OM use drizzle we have some rationale back back in the

36:08: day I was in tech about how su maps use like prisma which was it was pretty good a few years ago but drizzle is taking

36:15: over now error handling uh you also want to century for error handling. So we should yeah we'll talk about that later

36:22: when we deploy the app like a lot of things like user analyst and error handling is like only is important after you deploy your app because you want to

36:29: see what errors your user is seeing but like local development you can see what you're facing so it's like fine for now open full stack type safety is a re is

36:36: using like open API and it's using this yeah and you can share cross project you can read that part okay let's go 15

36:43: minute or 30 minute wait when use 15 I did not know that Listen.

36:52: Oh my god, bro. This is so complicated.

36:55: Actually, you should set up so it's like different events. That shouldn't be like overlap between your different events. That's too much work, bro.

37:01: No list. Same as uh when to meet. She must keep the No list. No list.

37:06: No list. No list. We don't have to overmplet. Okay. Okay. Let's not overmplet it.

37:10: Only anytime user can create an event, right?

37:17: Yeah, yeah, yeah.

37:20: Remove existing admin dashboard and option A

37:27: Monday, bro. Monday, Tuesday, Wednesday, Friday. Who's allowing what? What? What the hell is this? What is this?

37:35: What is this scenario, guys?

37:36: Maybe we just like stop the prompt question and we just like paste from Claude. Like, just I can just Wait, wait, wait. We This is important.

37:44: This is agree with me. Like, this is Gree me. like it ask you like specific questions so you can decide it. This is good for you guys.

37:50: I think it's okay. Frozen, bro. Guys, I'm just going to click on like recommend it for now.

37:57: We're just going to click on recommend it for everything for now and until like until like Okay, then we go over this. Okay, full stack. That's the full stack.

38:06: Uh what is next? Uh back end contribution. Contribution. Yeah.

38:09: Uh I put the license for you guys. You can change it if you want. Right now it's MIT and Apachi like very very open source. Yeah.

38:17: DevOps.

38:18: DevOps. We should save it later. Keep it keep track of the one we skip. Art and DevOps. Mhm.

38:23: Documentation. You should use a project board, GitHub wiki as I talked about before. Diagramming. I recommend using mermaid because it's like it's like it's

38:32: code. It's diagram as code. So you can just like paste it in like your wiki and everything. Like you can see one example here. Like this is what is diagram.

38:40: Oh my god. probably deleted my GitHub wiki. What does diagramming mean? Oh, here.

38:47: Oh, it is. So, you can see the diagram here. Okay.

38:49: And this is uh let's see if it's okay. This is a photo.

38:56: You can check it here. So, basically you can have like a you can have like a you can have like diagram as a code and the GitHub will automatically render it.

39:05: Okay.

39:05: Okay. Let's go back and do more recommend it.

39:09: Can we tell it to ask for no further questions just for the demo? Let's do that. Let's do that.

39:20: So, vibe coding actually takes time. Um, but like for the purposes of this demo, choose your owner.

39:33: And then we want to like as fast as possible back. We on high fast already.

39:39: You can also use Excal if you want to like if you want to draw things.

39:45: I just le some some some interview questions.

39:48: And you have Figma if you want like high lowi and high five fidity UI.

39:52: We can blur it out in post or something right. What the Yeah, we can figure it out. I don't think the company will be checking the sky left for the interview questions.

40:01: Okay, let's see this. Okay, schedule and everything. VLMs got that visual transformers.

40:08: Uhhuh. That's documentations. Uh front end very simple. React vit. Uh usually you guys will be using a app like

40:16: websites because in tech there's some like website we need to build rabbit should all be and why over next uh v build tool.

40:24: Uh like react uh next is something else.

40:28: Next is like serverless. This is something else. We have a actual server styling. Use tailwind CSS and use chassen whenever possible.

40:34: Uh if your designer like to use a skylight UI kit consider using qui but it's in development int text. So uh not really as in like

40:42: component library not component library routing with 10 stack router 10stack query state management you can use this

40:50: local storage search params and this thing you are you done? Oh my god has a spec ready for us. Okay. So after you

40:57: get a spec right, you want to say what you want to do is like write uh you want to do two sorry uh what is happening

41:06: two tickets and uh write each to GitHub issue in

41:15: did I lost the meat website? Oh my god, I should not close that window. the

41:24: projects and then delet so you'll write all the ones in here so you can keep track of all your issues

41:32: now just locally on one one person's computer.

41:35: So this is a spec to ticket and then we just implement each of them.

41:40: Okay. Then like after you document it like usually you want to assign each ticket to one person and you should work on that. For purpose of this demo I just going to ask Crawl to implement all of Len.

41:49: Yeah. Yeah. Yeah. just go like go implement land and commit land as fast as possible for demo purpose so I can deploy it.

41:58: Mhm.

42:00: Uh okay. State management. You can use this. You can just do stand. Oh my god. So quick. Oh no.

42:05: B stop. Wait. Approve this file. Oh only make five issues. Does it have 50 or five? Five. Okay. No 50. 50 issues bro.

42:13: Wait to meet up.

42:14: Yeah. Environments. We use EMV.ts TS file to like validate it so it knows when it's run.

42:21: It's front end is pretty simple nowadays. We talk about this, we talk about this repo settings, you can put branch djection if you want. Um you can

42:29: do branch merging like those things just like depend on your team if you want to do it. Just go practices I have skylab plus. So if you want like object storage you can use the railway storage buckets.

42:40: There's chron job as well. You can use emails uh docker cache that you can do that. It's just not that it saved a bit

42:46: of time but not necessary. You use SSR for better uh SEO.

42:52: If you don't build a mobile app, those are options. Confirm the plan.

42:58: Yeah, just do it.

43:03: Okay. Secret manion. We talk about style guides. It's full of AI toolings. Oh, here's all the toolings.

43:11: Like it's just like a bunch of tools we use like the lint like you're going to see here like we have a bunch of llinters. It checks all your format. We

43:18: check your we check your spaces to check everything. I need to update this one.

43:22: We use ox link now. Make a note. I need to update the llinter for scotty stack pre-commit. The one that checks it every

43:29: time you commit workflows. We have a monor repo. Your web and server is in the same folder. Like you can also create a new one like there's a in apps.

43:38: So let's talk about folder structure a little bit. So there's apps there server and web you can create a new one if you have like a chron job or another service

43:46: and you have a uh you have what you have packages this is like each pack each app uses like multiple packages it's like

43:55: package to be shared by the apps so like both of them use access control which is like related to o we later and

44:02: then db is here so access control can use db that was a reason testing uh we do a lot of testing here

44:10: that we do uh in each folder you can see server has a server test which are the unit test front end has like the front end test and then we have a end to end

44:17: integration test so a lot of tests we do but honestly AI write a test AI passes the test test is only there to show that show

44:26: that something doesn't work you have to manually verify something works as well but yeah that's test usually even in the industry as long as the test passes it's

44:34: fine and then we use dev container for development uh environment if you want to So I think I went over everything except DevOps and O.

44:41: Yeah.

44:43: So how fast is it? Can we like can we make it faster? Can we make it faster?

44:50: Uh okay. Let's talk about a little bit on the DevOps side and then we can make a side. We can do DevOps and then we can quit the Yeah, we can do we can talk about this one and we can talk about O.

44:59: Mhm. Because this will take a long time once.

45:01: Yeah. When intermittent we can talk about O for a long time and after we talk about O we can we can just like deploy it to show how to deploy it and then we'll be done with the session today. So hopefully we'll be done next.

45:10: Oh my god. You done? You done?

45:12: Yeah. Yo, after you approve that browser logging, I can use it. What? Browser logging.

45:22: Oh, okay. Okay.

45:25: I hope I hope it doesn't do stupid things. Enter the code displaying the app you sign.

45:30: Oh, wait. That's in the in terminal. Uh, it doesn't copy. Oh, thank you.

45:35: I did not need to do it last time. Yeah, I think I think expired here. Oh my god. Oh my god.

45:43: It's over. Access to 1541.

45:46: The claw's deleting everything. The claw's deleting everything. It's going to use it as data for training a compil.

45:52: Yo, I finished the class already. It's fine. Also, the class is uh LM ready. Also, the class is like LM open.

46:00: Oh, okay. Cool. Wait, bro. It's adding like six more issues. What?

46:05: Yo, wait. compilers you can use lm. Yeah, it's open lm at least last year.

46:09: Yo guys, look at it. We have all the issues here. You can assign to the members. Mhm.

46:13: Okay. Add all the issues. Okay. Now we can start implementing offline. Okay. Uh usually like what you can do is like you can do like

46:20: uh Okay. Let's expand this. Let's do a new context window. You can do like implement

46:30: all issues in use sub agent use sub agent for each. Yeah. And do it quickly.

46:38: Yo, wait. I think if you I do that then it's kind of like skip I guess.

46:42: Yeah. One thing you'll do is we do a code review. Yeah. Skip.

46:47: Code review. This is for demo only. Okay. Yeah.

46:56: Um yeah, we don't is fine. Yeah. No.

47:01: Okay. Now we can talk about we talk about art and then we talk about devops. Okay. Mhm. Art is hard but we figure out for you.

47:10: So we use open ID connect which you can find a lot of online videos talking about it. It is just like a very modern

47:17: like okay to understand OIDC you need to understand oath 2. OTH 2 is for authorization.

47:25: It's like it's a industry standard protocol. So you're gonna read about that and then you're gonna be like this one. It's for authentication. It's authorization versus authentication.

47:33: What's the difference?

47:34: Uh au authorization is like uh authentication is like you are who you are. You are who you say you are. And

47:42: authorization is like you can do what you say you want to do. Yeah.

47:46: So here Yeah.

47:50: So this two here this is a standard protocol we use. So you can easily switch to Google O in the future if you want to because everything is standardized. And then we use this

47:59: package called better o which is like pretty popular nowadays like it just reduce the code by a lot.

48:04: All the logic is in like o somewhere here. Yeah it has like it set up everything. It has a lot of documentation on that inline comments.

48:13: If you're wondering you can do that but like it's all set up for you.

48:15: Okay. And then we use uh O2 for authorization and castle. So and you can watch this YouTube video on castle. What

48:23: it does is that it it does access control uh access control package here. It does like all the type system.

48:34: Oh my god, this one doesn't have a lot of example but you can watch a video.

48:36: But like basically it declares like who can do what using the package and then we like share it between the front end and back end. So there's no redundancy

48:44: and discrepancy between the front end and back end.

48:46: That's why it's a single package. You can watch a video for more details.

48:49: And in any case you want to do like M2M like you have a web scraper that I need to access it. You can do using this code here which is sudo code in python and

48:59: you can just do this and then use the same ID and secret as the one we generated for you in the in the about in the b.skylabs.org.

49:08: uh o is hard because because you need all of secret ids but we populate it for you and generate for

49:16: you already we can you can find in here uh so actually to for you for for them like all it's like abstraction for that

49:24: I mean they don't have to like worry about it as much yeah because it's set up already also like you can also like uh we have the admins like we have a two groups in

49:33: keycloak which is admins and the members and you can use them in Uh where is it? Uh let's search up like admin.

49:42: Oh, here we go. Keycloak as well. Huh? Keycloak.

49:45: Keyclo is the one we generate the IDs in secret which they don't need to concern over. They don't have control over it. Okay. So it's okay. Yeah. Yeah. Okay. Cool.

49:53: Okay. Admin group.

50:02: Anyways, so like in the finished Oh my god, he finished. All six.

50:13: All you all done? Not yet. Only seven is in.

50:18: Well, what is the Oh, okay. Seven agents are done.

50:22: Okay, let's continue. Let's think. Oh, wait. Wait, wait, what?

50:25: What? Finish. Hold up. Shields and commit and push. What are you doing?

50:35: What do I want to show? I want to show the routes. So, let's do controller. So, we use like the controller service pattern.

50:42: Mhm. I think it rewrites a lot of things.

50:49: Okay. Here, here, here. You have like a secret like the security is like OIDC off. Mhm.

50:56: I guess you don't this like this one is not interesting. So let's go to Scotty stack because that has a more interesting example. Mhm.

51:04: Hello in demo.

51:08: What I want to do uh controller and look at admin controller. See here we have the admin scope. That means that

51:16: if you do this in TSOA with TypeScript open API what it does is that only people with admin permission can access this.

51:23: And it's all done using like the in the middleware and everything. Uh this yellow lip

51:30: o.ts it does a lot of like those heavy liftings. It get a row from the JWTn as well controller it gets a rose and what else?

51:41: Authentic. Oh this is the important one.

51:43: So you can see here it will resolve a bunch of things.

51:48: It will verify the scope and in verify scope it will do the does this groups

51:57: here has any scope. So this will check the scope and then map the scope to like to the groups. Oh my god, this is pretty complicated.

52:08: Yeah, if you're interested look more into this file as AI. I wrote this like a year ago, so I don't quite remember the details here.

52:15: Mhm. But this this p this this file is like mostly how it works. It verify the scopes which we gave it. Oh so the scopes is passed in like this scope is the one we declare which is admin scope.

52:25: So you check if it has any of the scopes. So the scope is like a any condition. So if it doesn't contain anything you just like throw an error. So you cannot access that route. Okay.

52:34: And then if it has a permission you just like resolve. So you don't need do anything. So they protect some some path only admins can access and some path

52:41: only like a normal user can access. You can always add more u scopes. You can add like a member scope so everybody in

52:49: your team can access this and everybody in like Yeah. And you can do the same pattern as here. Scope to group.

52:57: Any question off?

53:01: Um they don't so when they set up key club through gold they don't need to do anything like much else right um we will

53:08: have to give them access to all these things or no because gold will give them access.

53:12: Okay. Okay. Golden gives them access to the open bar.

53:15: Oh, okay. Okay. And open bar already has all the keys. Yeah. Okay. Cool.

53:18: And you don't even need to do yourself because secret pull it from the right place. Mhm. Okay. Yeah. Yeah.

53:23: So, it just magically work out of a box until they want to do something extra about it. So, this is a good starting point for them.

53:30: Took me three years to figure out all things Sky Labs. Oh, yeah.

53:33: We go from clerk to I think it's like five iterations.

53:36: Clerk last year, right? That was like clerk.

53:39: Yeah. Yeah, remember like the whole issues we had with Wait, we like did it with Google. We didn't even follow Clerk. We like set it up on Google Superbase, bro. Like,

53:46: bro, don't use Superbase, guys. Like, it's a third party service. You could never move to tech that way. Also, why would you need it? You can just Superbase what does it give you? Like, you can use Postgress.

53:55: Superbase has Google connections. So, you can like store data from Superbase and have users like Google accounts and we like filter Android. It was like, it

54:03: was really bad. This is like a lot more simple. Amazing. Okay. It did a lot of things. Okay. Okay. Can you say deploy deploy deploy?

54:12: Wait, do I need a code ravage check or are you skipping it for now?

54:16: I'm very confused. Like none of the none of the things is like done here. It's not Wait, can you just deploy as it's just like low key like

54:23: like uh commit and push or whatever you have. Yeah.

54:28: Yeah. Let's just do that. I think we're mostly done. Like the app we can like finish like async. Mhm. Just showing deployment though, right? Okay. Let's just show deployment.

54:37: Oh my god. Okay. Let me tell you. Okay, we're going to talk about DevOps now. Okay. Okay.

54:40: So, first I'll just ask you to push all the changes and then we can go over DevOps and we're done. Okay. Cool. Cool. Cool. Yeah.

54:45: So, first of all, we use uh we use railway for everything. You can look more on railway. We use IEC which I'll talk about in a second.

54:54: Repo template sendup. Uh okay, there's two things I'll talk about in a second. Are you done? Are you done?

55:01: I'm confused because look at it like Oh, wait. I think Oh, this is all changes. You already push everything. Okay.

55:07: Okay. Okay. All right, I think it's done. Okay, so DB migration.

55:10: You want to say the next thing to cursor?

55:12: What's cursor? I mean, okay, let's Okay, let's do let's do this. Let's do this. Okay, let's do this. It's like faster.

55:17: So, basically what you do to do deployment, you want to go here in railway.

55:23: This has instruction already generated by railway. Mhm.

55:25: And then this is this is IA everything's defining here. Mhm.

55:29: What you want to do is so when you're ready to deploy, you need to show us your project and then we're going to verify like it's ready for deployment to

55:37: show us a local version. So everything is working. You feel like a two-minute video and like send it to us.

55:41: We'll talk about more in the middle of semester and then you want to uh we'll give you access in railway. So let's go here. Railway you guys will give a get a new project.

55:53: Let's just create an empty project for now.

55:56: And then here, let's call this thing meet.

56:00: So you get a project and then we're going to like add the members. We're going to add the person who is the tech lead and the tech lead will invite everybody else. Basically, we get everybody in your project. That's why

56:08: we're using railway because we have infinite seats in railway. Okay.

56:12: Imagine log to Yeah. Yeah.

56:15: Using using email OTP disobeying their terms of service. Wait, how? Because it's like one seat per person.

56:24: You're not supposed to do that.

56:27: And then it was sell like $20 per proceed. Okay. Now what you do is you you check this file and the project name should match and then everything else should be fine here. And you know what?

56:36: Just you got it. You got it cursor. You got it cursor. Yo, bro. Yo, boy.

56:43: That's actually all you need. I give you a read me. Like what else do you want? So you try to do it.

56:50: I already signed into railway in in my browser. So like with your personal account so you need to link it to your account so it can run all the commands but like

56:58: I already linked it. I don't know how to declare it but like AI will tell you what to run. Also you deploy this thing once we'll probably help you if you have like issues on real on deployment.

57:08: Okay.

57:08: Yeah. You also deploy the recruit and then you will just you can see how process it's so it's very easy and here uh you just like deploy everything here. Mhm.

57:19: So this IA the template set up uh so I can talk about the rest of it while AI works through the rest of them. Amazing.

57:26: Okay. DB migrations. Uh I is infrastructure as code. So you define all your infrastructure as code. So you don't need to do any manual clicking.

57:34: So DB migration is here. Uh yeah there's a bunch of things right now. We just run as a pre-eploy command. So you don't need to worry about it. We just do it for you.

57:42: After you deploy your app, you want to use post hog to do user analytics analytics. You want to talk to our GTM head of GTM for that error logging you can we can use sentry you can ask us for

57:51: one and then uh like every time you run an app it tells you like it tells you like uh

57:59: sentry is initialized with like DNS undefined it's fine but like you probably want to do error logging like after you deploy your app so make sure like you're not running into issues and

58:07: then after you deploy it and we and we verify it looks good we can you can we can offer you a domain from your budget. So, you're going to go

58:15: to pokebond.com and just like go through all the domains you like to buy. Pick on a few, tell us which one you like, and then we're going to add it to crowdfill.

58:23: We're going to do all the domains for you because you have permission to do that.

58:28: If you're on a budget, you can use the CN skylive.org, which is free.

58:32: Just a note. But the CNAME Came is like you have something in front of the Oh, yeah. Yeah. I think deployment. Yeah. You just ask AI to do

58:40: IA and you want to Oh my god, it's up already. Yo, you guys want to check it out?

58:47: Wait, can we is it deployed at meet.skylabs?

58:50: No, because uh No, we need to do it ourself. This thing we need to do it manually, but like right now, let's just do a Wait, can we do that just for

58:57: Oh, yeah. We can do it. Oh, we have actually t just look.

59:01: Okay, it's there. It's okay. It's live.

59:04: Sign doesn't work. What you do is you command option I What's the issue? Block my course policy because

59:12: Oh, course. Yeah. password storage and resource sharing.

59:15: Yeah. So because in the gold door we defined our domain so it will not work until you have the right domains.

59:21: So you want after you get your domain you update your go door the tunnel file.

59:25: So this is like need metropolitan. Yeah.

59:32: Mhm.

59:34: And then you do not have access to do this. I we need to manually do it for you. Mhm. Okay. Just one click.

59:48: And then this thing I don't know why it's not connect because it's a naming issue. I just like do this quickly connect.

59:57: You can just redo it. Uh if you have issue we can do it for you. It's like one time thing. Mhm.

1:00:01: I think the issue is here. There's a demo I Oh demo branch. This is why because I use a demo branch for Scotty.

1:00:09: Oh.

1:00:10: Oh it's redeploying. Okay. It's thinking. is thinking really hard. We change it to main. So hopefully we'll get it right this time.

1:00:17: Oh my god, it crashed. So you can always check on things like view logs and then look issue env. We don't have the client

1:00:24: secret. So you want to put your client secret in there which there's no way for me to do it now because you're going to go see the secrets.

1:00:32: Oh, okay. Yeah. And wait, wait. We can just recording and like put the secret.

1:00:37: Okay. So we're going to start recording now and just like put a secret in. Yeah.

1:00:42: Hello, welcome back guys. So part three I guess. So we put our secret in there.

1:00:49: It's from open bow in generated pro copy pasted that we did ourselves. Yeah.

1:00:57: Oh, we solve all the tickets. Mhm. Let's go. Is the is a check passing? Oh my god. All the checks are also passing. Wow. Mhm.

1:01:05: Let's let's see the issue with the this. Let's try to fix this quickly. Oh, okay.

1:01:10: Got everything. Meat. Just do it yourself, I guess. Same thing for this one.

1:01:18: I don't know. Every time it does, I think it's because the first time I did a the branch is wrong. Yeah. Mhm.

1:01:28: Okay. Good. It's connect to main now because there's no demo branch. Okay.

1:01:32: And then here uh you also get two more things from railway on deploying things.

1:01:37: Amazing guys. Amazing work. Now, let's also fix this because the URL for this is not right. Mhm.

1:01:44: It should be API meet.skylabs.org. API. Why API?

1:01:52: API.

1:01:53: I guess uh application something interface. Programming. Programming interface.

1:02:01: Is this what it is called? Yeah.

1:02:04: Oh my god. This one you do manually because you cannot detect it correctly.

1:02:09: Surely it's fine to just go in there and add some secrets. Like surely it's fine. You can find it online. It's DNS.

1:02:18: This is a CNAM.

1:02:27: This is a TXT. TXT.

1:02:35: Oh, my bad.

1:02:42: Okay, now I will verify. Uh, let's see how this one works.

1:02:46: I think the URL will be wrong because it was deployed before. So, I need to update that too.

1:02:52: Kind of hard to do. Uh, did C stop running? What are you waiting for?

1:02:58: You trying to do a custom domain? Just give up, bro. I'm doing it for you.

1:03:06: Well, this is terrible. Look at it. All the reax is run. It's using stack. Oh, not sky stack.

1:03:12: Yeah, I got all of those run because Oh, because it was not updated here.

1:03:19: So, let's update all of them for then. Can you just switch stack?

1:03:25: Yeah, let's do meat. Meat. Meat.

1:03:35: Okay. You know what? You don't always need to depend on AI. It's like one commanded one, bro. Why is it destructive?

1:03:45: What am I destroying? Destroy.

1:03:48: Destroying the port.

1:03:52: I don't care about the port. It's 80. I defaulted to 80.

1:03:59: The port is defaulted to 80. It doesn't matter in the code. Yo, everything's building.

1:04:08: This one would be wrong because it was updated before. This is like a reference. So, I'll just fix it quickly by doing this.

1:04:20: Like I can go here like this is still old version. You can see like here you reach out to API.stack. stack which is wrong. Mhm.

1:04:28: So this is the one where you can fix fix things. Yeah.

1:04:31: Okay. I need testing this browser. So I actually have my I should have my Android ID and everything.

1:04:39: Back lock done. This is done.

1:04:43: I think we went over everything need to do.

1:04:45: Let's just uh wait for this thing to deploy and we'll be done. We can check this like API already status. Okay.

1:04:53: Point check working. Mhm. Signing is working.

1:05:02: Raining events is working. Everything's working. Is that okay? Wait, can I sign in? Yeah, sign in. Sign in. So, what event is this?

1:05:09: Labor engineering meeting.

1:05:11: Yo, what dates? Yeah, today. Today. Now, whatever.

1:05:20: Yo, guys, come to this link. I how to send it to you guys without It's fine. We can I just like No, no, I can like Oh, this is so long, bro. Oh my god.

1:05:28: Oh, like that.

1:05:30: Stack it to Yeah, just open Slack. Surely there's nothing in Slack. I cannot show you guys.

1:05:37: Harash and I think there's like a group chat with all of them. Okay. Try try it. Try it.

1:05:46: Iron free. Oh, okay. Save availability. I can withdraw.

1:05:55: Yo, I can see you.

1:05:57: Yo, yolo, you are so bad though. I cannot see who's where.

1:06:00: Yo, you there. You there. We can fix it later. We can This is why humans stay in the loop, guys. Yeah.

1:06:05: Can you highlight like a place that has like to make it three people? Wait, actually, I think it's I think it's Oh, I didn't say Oh, I didn't say. Yeah.

1:06:11: Yeah, I think it's correct cuz I can see yours. I can see where all three of us are working cuz I think 10:45 to 11:15.

1:06:18: Yeah. Yeah. Yeah. Yeah. Yeah. Okay. 10:45. Wait, what?

1:06:24: Oh, but I can't see mine. Okay, you know, it's okay. But I can see everyone still. Okay.

1:06:28: Yeah. Response. Yeah, everyone's names are all here. Okay, perfect. Cool. Awesome.

Clone this wiki locally