Thank you so much. I had struggled a lot with yaml file deployment where its taking too much time to upload artifacts which you mentioned the resolution. that saved me. Thanks a lot again.
Thank you so much man. Words cannot describe how appreciate I am. I was driven crazy by the amount of time it took to deploy every time especially during the process of debug/testing. This saves tons of my time. You deserve more subs, and now you earn a sub from me. Well done.
I appreciate the kind words my friend! So happy to help! Let me know if you want me to cover anything else. Your comment had perfect timing. I'm sitting here without electricity from hurricane Ian. Thanks for the sub too!
i appreciate that you kept it very real and relatable all the way down to when there was an error and you showed how to solve it. thank you for keeping it honest and thorough. you have made it to my top video tutorials to watch.
I appreciate that! I think my next video is gonna be about sending verification emails to new sign-ups. I'm planning to do it totally on the fly including googling anything I need to figure out. May bee helpful to see how much programmers use Google! Anyway, thanks again and let me know if there is anything you want me to cover!
Appreciated man! now my CI/CD is up and running, pretty easy to follow your video thru thanks from the heart of a novice on this stuff. What if we would like to connect that frontend app to a Nodejs backend server, would be like the same in azure? or what kind of config would be needed to make the frontend app and the backend one to talk to each other?
That depends on a lot of things. In a simple scenario, when you deploy the node api, you can just point react's api calls to the url of the node app, but in more complex setups, you might need to run through proxies and open ports up so the two can talk to each other.
Thanks a lot, was thinking that was the reason but wasnt sure if I was right since there arent any videos addressing this issue which is weird, so I thought I was doing something wrong. Why are there videos that just upload the entire folder instead of only the build but still have it working? Im confused lol
@@NobleCauseCode I couldn't find a single video addressing the problem of the whole project folder being hosted instead of just the output build. I kinda understood that that was the cause of the issues for me, but I was finding it hard to confirm if that was the case, since there were basically no video addressing this issue. You would think that this would be a common problem and people on RU-vid would point that out lol Thanks again and sorry for confusing you lol
Not sure what you mean? I was logged into the Azure portal in Chrome. Once logged in, I was able to create a web app and hook it up to my github account with the authorize button. I didn't need any secrets to hook up CI/CD. Can you give me more detail on what's not working?
Ahh OK, I think you mean on your local machine. You won't initially have a build folder, but if you saw the yaml does npm install and then npm run build. That makes the production build that will be deployed. If you want to see that folder locally, just do the same. Type npm run build and it will create all of it. The build command is defined in package.json. Hope that clears it up
Hi there, I followed the same steps as you did, but I still received the "You do not have permission to view this directory or page." Would you give me some advice on how to debug this? I tried to debug this but kept failing.
If you drill down into the kudu tools like I do in the video, what is deployed to the wwwroot folder? If the build folder files are there it should work fine.
@@benjaminnguyen592 hmm It's been a while since I did this video but I wonder if those files should be in wwwroot not inside a build folder. See if you can manually copy the files into wwwroot. If it works then you can change the yaml to match what it needs to do.
