Sprint 3: Scrum based project building a web app in 8 weeks.

hello and welcome to the sprint 3 demo for my web app project let’s get into this by having the product backlog. so i’m going to share my screen hopefully the image does actually appear on the bottom right-hand side I’ve had a little bit of trouble, I could say a little bit with Zoom but it’s been quite a lot, I’ve had to re-record these sessions several times just because the screen just gets messed up it doesn’t like VM images and you can see that i have the 2 start menu’s on the left-hand side, task bars as we call them, and, so this print it was about fixing a couple of bugs and the logout button didn’t work and we also had unauthorized access going on the next one was the web service, so, the logout button quite quick login button, it shows us the pop-up and it goes to google gets your access and takes you back to the site, that’s about it. you see it’s not transitioning into this tasks list just yet, i will get that the access part, we logout again, we could just give that a quick try by typing in tasks and seeing what happens nothing should happen exactly. it did try to get it, but it has not i access, so that’s that part of the demo. so the web service was quite an interesting thing I could have gone and used a linux server with YSlow which is an API from Yahoo but i found out that this is not being maintained, hasn’t been maintained for about 3 to 4 years, so i had to seek an alternative and in the end i went for Google PageSpeed, which i’m sure is an industry standard, it has an API which we can call as well, so what we’ve got is a web service which is calling another web servers and i’m using google containters now, I was, looking around for solutions and found that google are offering $300 for 60 days for free and that’s quite an exciting offer, and after reading about the container engine which allows you to get away from this infrastructure part where you’re actually having to set up machines allows you to concentrate more on programming, i got quite excited and i ended up landing quite a few new technologies this week to get the webservice up we’re just gonna have a quick look at those steps of the actual service. what we’ve got is my localhost here my machine it should not be working right now there, i’m gonna fire up a tool called gulp I did the programming in Node.js you can see the program here. I have hidden the API key which you do need to get access to google and i’m using a Node package called PSI to make this possible, so you can see the route here, slash site and if we go to page now and i refresh this something should happen. in fact I could do my / site and we could give in a URL like google and see how fast they are it didn’t like that I can’t get the URL what’s going on there um, i don’t know, i forgot to put in the API part the namespace, so let’s add that 100 and we go to my website is going to be much much slower I would assume cos Im not using CDN’s and all this kind of thing that they have to their disposal, see it’s taking a little bit longer that obviously reflects the speed of my website, 42 !?! I cant believe it, i’m gonna have to speak with those guys at Squarespace what are they doing with their servers well, more about that later on you seen the source code here, i can actually change that and let’s do a quick check you what happens when a change is code and I save it. go back in, i would expect it just to actually show me. so this is how I developed the API, it was really quite comfortable to do that and I find a tutorial on this very quickly it was really quite a fast thing to develop so the next part of this while I kill that was actually learning docker. that was a bit more difficult, actually Im quite lucky I have access to PluralSight that I’ve used for a few years I strongly recommend it as a great resource and you can do docker images here and have a look docker images you can see I have been publishing different version of my web api, and, instead of building something, Im just actually going to run it there we go. we should see, press f5. it’s changing again so now I’ve got a docker container and actually the next step you could do there is using the google command, so there’s the gcloud APIs that you can use to publish to google and lets have a quick look google there. so we have the container engine part of the Google cloud container registry and you can see actually have a published version here of my webservice and once you actually get your app up there what you’re gonna do is you’re gonna fire up a container cluster and that’s really just done in a couple of clicks you just really just create cluster and then you’re going to have the option to choose how much memory and so forth and then within a couple of minutes your containers are running and from the command line we do have some commands there I think its ‘kubectl get services’ and we’ll see what I’ve got published in the moment. we actually see my page speed cluster and that’s that IP inside the data center and that’s the public IP, so unfortunately right now my API is not secured, its totally public to the world anybody could use it and that’s not really so awesome and google have provide something called cloud endpoints and with a couple of code snippets we can actually secure our web endpoint which is going to be great i want to do that next week and we can even try this so here is our URL let’s just check it’s working i might have to down this site cos i’m not sure if i want the entire internet actually going on here but we try it anyway. a bit of copy paste problem yep it’s online that’s great it’s still working so know it actually does work i have managed to publish my container up onto the cloud and I could also start checking page speeds so for me that is actually a job done, it would have been really awesome if had a button inside the app you can click and it does it, and, lets go and have a look at the backlog for that. so I’ve come up with a sprint 4 and in that, I’ve actually said, okay, the user is able to trigger the website speed comparison, I think it’s this smaller job now, I just have to call this web service. to visualize it, is even smaller job and I want to secure that service and I’ve given it a 3 pointer because I’m still a little bit unsure about service and then it’s not totally trivia. that’s about all I have to show this week, I wish you all a great start for the year and i’ll be back again next week. bye for now.

Add a Comment

Your email address will not be published. Required fields are marked *