I would like to thank you and Kris on your previous docker vid. It helped me fix the issue on the docker setup I'm trying to use which took me more than a day to troubleshoot.
If you are using Compose V2, the command is now 'docker compose', not 'docker-compose'. It's docker's integration of compose commands as oppose to standalone docker-compose (V1) commands. And it's not just an alias, V2 has been rewritten in GO and has improvement like being able to run natively on Apple Silicon.
@@krisrivera4215 And thank you for the great video! I love start to finish tutorials where we see how each piece fits together and all of the debugging developers actually end up doing 👍 I joined a team with several docker projects in place so it's invaluable to see one built from scratch.
I think in a setup like this, its best to use docker networks to lock the container from being accessed outside the project. then we can also use the container name to access the container service instead of using localhost. other thing is using deploy resource limitations, restart policies and health checks for prod by having an override compose file to for the relevant environment.
When opening vscode from inside of vscode using “code .”, if you don’t want to have two windows, you can use the “-r” option. With that, the same window will be reused to open the new folder.
Alex, did you published your whole app somewhere? couldn't find any reference on your transcript. Thank you. Sorry I just watched on video your reference to your GITHUB
The ENV var is not used inside the code. The port 8080 is hard coded with a const inside so changing the ENV var or in the docker-compose.yml has no effect.
I was using ‘spawn’ in an image of an IDL app - spawning to the OS to run a compiled fortran app. This crashed the code. How to go about making spawn possible?
one important thing to consider is deploying containers on Azure. If the final deployment is going to Azure and your customer cares about security, the stock docker approach isn't going to well. It can work, but just not well integrated with Azure security. Instead, most of our customers prefer to use azure services to expose services running in a docker container. Some of our customers have standardized on Azure approach and don't recommend using stock docker nginx. In the extreme case, the security groups will slap your hand and demand you change the terraform setup before you're allowed to deploy to production or uat.
Thanks to Kris for teaching us how to do Docker compose the right way
I would like to thank you and Kris on your previous docker vid. It helped me fix the issue on the docker setup I'm trying to use which took me more than a day to troubleshoot.
If you are using Compose V2, the command is now 'docker compose', not 'docker-compose'. It's docker's integration of compose commands as oppose to standalone docker-compose (V1) commands. And it's not just an alias, V2 has been rewritten in GO and has improvement like being able to run natively on Apple Silicon.
Thank you for the information. I found this out after the video recording as well and will make sure to mention it any follow up docker videos.
@@krisrivera4215 And thank you for the great video! I love start to finish tutorials where we see how each piece fits together and all of the debugging developers actually end up doing 👍 I joined a team with several docker projects in place so it's invaluable to see one built from scratch.
Thanks for the great video series. Kris was excellent
Great video, Alex... Kris is a real great chap... very knowledgeable yet humble and down to earth!!
The bug is on line 26 of server.ts - you are using a hard-coded variable for the port, and not the env variable PORT. Great video! Thanks
I think in a setup like this, its best to use docker networks to lock the container from being accessed outside the project. then we can also use the container name to access the container service instead of using localhost. other thing is using deploy resource limitations, restart policies and health checks for prod by having an override compose file to for the relevant environment.
When opening vscode from inside of vscode using “code .”, if you don’t want to have two windows, you can use the “-r” option. With that, the same window will be reused to open the new folder.
nice tip!
Damnnn Nice tip tho :D
Nice explanation and how it all ties together. Thanks.
What a nice and smart guy Kris is :)
This was a great set of videos. Thanks!
Awesome! Definitely will use this vid for my reference
Great video! It's pretty cool that not everything went "smooth", and you had to debug some errors, just like one would do in "real life" 👍
Darn, it is like the ever good TV Show, "Tech Crunch with Alex and Kris"!
I was waiting for this !
Another great video! I love it!
Great videos, well presented, Keep it up. Looking forward to one where you use K8s as an orchestrator🙂
Alex, did you published your whole app somewhere? couldn't find any reference on your transcript. Thank you. Sorry I just watched on video your reference to your GITHUB
The ENV var is not used inside the code. The port 8080 is hard coded with a const inside so changing the ENV var or in the docker-compose.yml has no effect.
Thanks for the content!
Hello 👋 how to automate docker-compose up command for watching the changing in the files
I was using ‘spawn’ in an image of an IDL app - spawning to the OS to run a compiled fortran app. This crashed the code. How to go about making spawn possible?
great video
Thanks!
Great video, just a comment, you can use `docker compose` without the hyphen as docker ships now with Compose V2.
Could you maybe do a video about the best way to reply this kind of docker setup with the two projects to Azure?
It would be nice to see how you handle any updates to front-end or application. Maybe some form of CI/CD thrown into mix.
we might do more in this series. stay tuned
@@AZisk I will
As I write this, I’m seeing 99.9K subscribers on Alex Ziskind channel! Great channel Alex 🙌 🎉
💯
you’ve been here for a while. thank you!
Cool 👍💪
Awesome
hope you enjoy
Yes I did. Thank you for the videos
one important thing to consider is deploying containers on Azure. If the final deployment is going to Azure and your customer cares about security, the stock docker approach isn't going to well. It can work, but just not well integrated with Azure security. Instead, most of our customers prefer to use azure services to expose services running in a docker container.
Some of our customers have standardized on Azure approach and don't recommend using stock docker nginx. In the extreme case, the security groups will slap your hand and demand you change the terraform setup before you're allowed to deploy to production or uat.
Lesson of the day, do not hard code the port 😂😂
😂