Hey Miguel, thanks a lot for your efforts. You are presenting the stuff very well and you are concise and quick at the same time. I like it a lot. Fo extending your tutorial it would be nice if you could show how to connect a MongoDB or a MySQL database on top of it and use volumes between the docker containers. I am working at that currently and would really like to have your opinion on that. :) Cheers, take care.
Thank you so much!!! I am developing small flask and svelte app (my firtst web app), and thanks to you I finally learned how to properly serve static frontend files from dockerized flask app! You saved me alot of time and frustration.
It's funny, I started my Carbon footprint calculator using your react + flask app tut. Now I was looking to dockerize it and I found this! Thank you 👍👍
Hi Miguel, in terms of security is it better to create user in the docker container and make the flask app run under this user? or does this not really matter?
I have just one question: If I want to configure the client and move to reverse proxy like localhost:80, how do I automatically make the React app run?
hello sir miguel grinberg, the video calling app that you made, can it be deployed in heroku. I'm having difficulty running it. please help. I reached the step of python app.py. But as i launch the app it is blank completely.
Check the Heroku logs for errors, I'm not sure what else to suggest. The application doesn't have anything that would prevent it from running in a dyno.
@@industrialcounsel4501 I don't really understand what you mean. A web server listens on a network interface, so it can receive requests from that network interface. What do you mean by "outside the network". You may be asking about something that is completely unrelated to the web server.
@@miguelgrinberg If I'm understanding this correctly though, when you run your docker-compose it does not connect the api ports on the image to any ports on your system, so you cannot access the api through your browser.
When you test with docker-compose you still use port 3000 despite the fact that the config says 80. I tried with localhost only without specifying 3000 but it did not work.
@@programmer1379 For a production server you will map port 80 from the nginx container to port 80 and 443 in your host, and you will do a proper TLS/SSL setup. I did not intend to cover how to deploy in this video, the topic is how to create the containers. There are a ton of tutorials out there on how to deploy Docker containers.
Give this man a medal... 🏆 his contributions to Flask is commendable...
🏆🏆🏆
Dear Miguel, you have saved a few liters of my blood, sweat and tears. You are the real MVP!
I've already learned that from your flask mega tutorial, so I just came here to like the video and wish you the best
Still using this video after 2 years as main reference for dockerizing my web projects :)
Thanks, Miguel!
What an MVP! Just spend 6h of my life trying to do what u did in the video. 5 minutes with part of it fixed my problem. Great content!
Thank you Miguel, that ties a bunch of fiddly little details together nicely.
Thank you Miguel! I'm a fresh grad, brand new developer and I learn through your tutorials.
Another amazing video as expected! Pls more of docker Miguel
You are the best in the field, Miguel! ❤️
Thank you so so much for this tutorial series, Miguel!! This was so helpful and well taught!
Series about React + Flask is great
Hey Miguel, thanks a lot for your efforts. You are presenting the stuff very well and you are concise and quick at the same time. I like it a lot. Fo extending your tutorial it would be nice if you could show how to connect a MongoDB or a MySQL database on top of it and use volumes between the docker containers. I am working at that currently and would really like to have your opinion on that. :) Cheers, take care.
I wanna invite you a beer. You're the man.
Thank you so much!!! I am developing small flask and svelte app (my firtst web app), and thanks to you I finally learned how to properly serve static frontend files from dockerized flask app! You saved me alot of time and frustration.
It's funny, I started my Carbon footprint calculator using your react + flask app tut. Now I was looking to dockerize it and I found this! Thank you 👍👍
Excellent sir - Thank you indeed
Thanks!
Wow, thanks so much for sharing this. Excellent content as always, you're the best!
Brilliant stuff !! Hats off to you for sharing this.
Massively helpful tutorial, thank you very much!!
Thanks for this tutorial. How would we deploy this app to a real production web server?
Really cool. Cheers!
Great guide, thank you.
Thank you!
Hi Miguel, in terms of security is it better to create user in the docker container and make the flask app run under this user? or does this not really matter?
I have just one question: If I want to configure the client and move to reverse proxy like localhost:80, how do I automatically make the React app run?
Miguel when will your react mega tutorial be coming out?
I don't know yet.
many thanks
Amazing!
When you will come back?
Thanks sir💙. Can you make video of using redis with 2 socket io servers.
hello sir miguel grinberg, the video calling app that you made, can it be deployed in heroku. I'm having difficulty running it. please help. I reached the step of python app.py. But as i launch the app it is blank completely.
Check the Heroku logs for errors, I'm not sure what else to suggest. The application doesn't have anything that would prevent it from running in a dyno.
@@miguelgrinberg great sir. your reply was very much appreciated.
awesome
I cant believe I have not found you earlier, great work... One Q I had for you.. When built as a combo image can the api's be accessed separately?
Yes, the API cannot tell who sends requests to it, so it accepts requests from all sources.
@@miguelgrinberg due to outside the network or from the network.
@@industrialcounsel4501 I don't really understand what you mean. A web server listens on a network interface, so it can receive requests from that network interface. What do you mean by "outside the network". You may be asking about something that is completely unrelated to the web server.
@@miguelgrinberg If I'm understanding this correctly though, when you run your docker-compose it does not connect the api ports on the image to any ports on your system, so you cannot access the api through your browser.
@@decimater75 You can map port 5000 of the API container to a port on your host, then you can send requests to the API bypassing the client.
When you test with docker-compose you still use port 3000 despite the fact that the config says 80. I tried with localhost only without specifying 3000 but it did not work.
Port 80 is only used inside the nginx container. My docker compose file maps this port to port 3000 in the host computer.
@@miguelgrinberg How to avoid typing the :3000 in the browser?
@@programmer1379 on your development machine? Why would you want to do that? You can I guess, but what is the point? It is not worth the trouble.
@@miguelgrinberg For a production server. I don't want users to have to type the port.
@@programmer1379 For a production server you will map port 80 from the nginx container to port 80 and 443 in your host, and you will do a proper TLS/SSL setup. I did not intend to cover how to deploy in this video, the topic is how to create the containers. There are a ton of tutorials out there on how to deploy Docker containers.
Great content! Please start making Udemy courses around these topics. You will definitely earn a 5-star rating.👍
👍👏👏👏