The env file in Django is crucial. It holds sensitive information like API keys and database credentials, ensuring security while allowing for easy configuration. Thank you.
Thanks a bunch for this. It would be great to see how the deployment process looks like with dev and production and how the further development process is. For example if you want to add a new feature, what are the steps you take.
Sir I have a doubt if we are able to fetch data from .env why can't we read the values from it based on the environment. I don't understand clearly what is the purpose of creating separate settings file for every environment. As far my understanding I described above single settings file with the combination of env file is enough right? Please clarify my doubt.
Why do we have DJANGO_SETTINGS_MODULE in .env file? I thought purpose of this is so that we can change here value from 'local' to 'production' and then simply run 'python manage.py runsever'. But for me, it did not change to 'production', it continued running 'local' settings. Is it somehow ignore .env value and just taking 'default' set in manage.py?
More or less I followed what you did, but, can anyone explain how do we in practice use that configuration when we want to push it to github and then to our server? I actually understand nothing after this configuration. Why can't I simply ignore everything on this video and once I have finished developing I make the last important changes in the files like debug = False, and allowed_hosts to the IP and cname of my website. Can anyone give a hint?
I liked the method of making Django Ninja Extra, but I feel frustrated that there are not more videos to learn this technique, as I found that it is somewhat different from Django Ninja, and I want to make a large High Performance project, but there are no sources. Can you explain what combinations of Django Ninja Extra projects will be large projects? Like Tik Tok or Amazon?
You make me a better developer!!! Thank you. Looking forward to a Celery, Huey, Dramatiq tutorial. Your django-webpack series is top notch!!
Thanks a lot, appreciate it!
Celery + Huey will be coming up soon!
I truly believe your videos are the best in TH-cam for Django Intermediate level and above. thank you sooo much :)👌
The env file in Django is crucial. It holds sensitive information like API keys and database credentials, ensuring security while allowing for easy configuration. Thank you.
Thanks a bunch for this. It would be great to see how the deployment process looks like with dev and production and how the further development process is. For example if you want to add a new feature, what are the steps you take.
Just one thing to say. THANKS!
Thanks for commenting!
great video, love seeing how to use best practices for production!
Thanks a lot!
Thanks for explaining in easy way
please create a video for deployment with docker as well
Thank you! Will do!
Thanks so much, I've been looking for a good tutorial of this.
Thanks for the comment, hope the video was useful!
Very interesting, thank you.
Thanks a lot!
Great big brother
Thank you!
Thanks for sharing.
Bro you always teach something new . But bro would you make django rest framework playlist.
Thanks
Thank you!
Thanks a lot!
Sir I have a doubt if we are able to fetch data from .env why can't we read the values from it based on the environment. I don't understand clearly what is the purpose of creating separate settings file for every environment. As far my understanding I described above single settings file with the combination of env file is enough right? Please clarify my doubt.
Why did you move BASE_DIR setting to .env file? Can you please explain?
thanks 🥰
what about use django-oscar or saleor ?
Would love to do some content on those! Hopefully in the future!
Why do we have DJANGO_SETTINGS_MODULE in .env file?
I thought purpose of this is so that we can change here value from 'local' to 'production' and then simply run 'python manage.py runsever'. But for me, it did not change to 'production', it continued running 'local' settings. Is it somehow ignore .env value and just taking 'default' set in manage.py?
Hi BugBytes, For how long have you been Django'ing?
More or less I followed what you did, but, can anyone explain how do we in practice use that configuration when we want to push it to github and then to our server? I actually understand nothing after this configuration. Why can't I simply ignore everything on this video and once I have finished developing I make the last important changes in the files like debug = False, and allowed_hosts to the IP and cname of my website. Can anyone give a hint?
please you said you will make a playlist about django channels tutorial
are you still planing to do it or not?
Definitely planning it but will not be for a few months at least.
I liked the method of making Django Ninja Extra, but I feel frustrated that there are not more videos to learn this technique, as I found that it is somewhat different from Django Ninja, and I want to make a large High Performance project, but there are no sources. Can you explain what combinations of Django Ninja Extra projects will be large projects? Like Tik Tok or Amazon?
Should i be using multiple apps in a project?
Do a tutorial on django-sonar.
thank you
Thanks for watching!
🙏 thanks
Thanks for watching!
thank
Thanks for watching!
When importing the stars to the base settings, your best luck is to hope you are not shadowing any variables names.
It doesn't matter.
You should always inherit everything from base import *.
When you are using dev settings vs production settings
I find this horribly convoluted and complicated