Django ChatGPT Clone Tutorial

[@xxoooOFxx]

Well done, and an excellent intro to Django. Happy to see more of my African brothers doing programming! AI and software is the future, and Africa is the next frontier.

[@williamlennon2070]

Nicely done! Thank you for explaining things the way you do. I like how you run the code with it not working first, then explain why it wasn't working. Gives the video a great pace and helps debug our own issues.

[@lemonjuice6177]

thats the best front end professor ive ever seen, OH MY GOD I LOVE YOU

[@jennifermckeithen1498]

This is great!! I really appreciate the detail and explanations! You have the heart of a teacher, mon ami !

[@ChrisEj_The_Broly]

This young brother wants me to not give up on django, well done bro👏👏👏

[@CodeWithTomi]

Thank you freecodecamp for publishing this tutorial. I hope it’s helpful

[@CheckMateBoyz]

I can not thank you enough :) I am new in Django and your video realy helped me ... Thank you so much :)

[@sandeepnayak6357]

crazy tutorial man loved it! well explained

[@pinkflower03]

Oh Oh, going for next level now.

[@Chisanloius]

this chap is so good, thanks so much man

[@AaronTheImposter]

Why y'all put "Django" so large next to this man? Y'all tryna say he's unchained?!?

[@yourfriendlyneighborhood5547]

Caught me so off guard💀

[@dentrifications]

Lol..nice one😂

[@julionicolinopavettiavila5342]

Your work is impressive my friend. One question... How can I change the language of the AI, for example in Spanish?

[@21cyco33]

there must be a api for that?

[@liliyalopez8998]

Very well explained! Great job!

[@AliceQian-s2m]

Nice work!keep going🎉🎉 3:33

[@MrDekassia]

Thanks Tomi! Amazing tutorial😊

[@infoboxind1874]

Great work!!!!🎉🎉 Love your content

[@vbncml]

Thanks for the tutorial! I've learned a lot and even more

[@paulrmaurer1]

Great job, Tomi!

[@GAMINGASTER]

Thank you guys for helped me a lot ❤

[@usmanadesola5144]

Thanks for the tutorial Boss Tomi.

[@kazethenoob8591]

Doesn’t work again for me now I get an error saying the OpenAI is not supported again bla bla and I am using gpt 4 api

[@kaydeeinmy]

The tutorial is understandable !

[@farooqirshad4432]

Thank you very muss, that was very good

[@SamGralla]

Is there a relatively simple way to receive data back as a stream and forward to the client? I know django isn't built for this... but I'm stuck with it for my project. Thanks for the video.

[@xushnudbekjumayev]

i am stucked on this turorial with this isuee pls help me if you know raise self.handle_error_response( openai.error.InvalidRequestError: The model: `gpt-4` does not exist [01/Jun/2023 14:03:12] "POST / HTTP/1.1" 500 91452

[@Famelhaut]

You want django-channels for that

[@NonnoSgrenf]

Niceeeee video!!!

[@HuzaifaSaran]

Thanks MAN. Everything worked perfectly just my chatgpt quota is finished without even showing any reply. but if i get paid version and connect with this. hope so it will reply me . again Thanku.

[@AlindaAnthonykeidy]

Thanks free code camp

[@amansamant6398]

If you remove the message-list class from chatbot.html the chats do not render. Can someone explain how that works

[@muhammadubaid6576]

Sir make tutorials on document tracking system web based in MERN Stack with source code

[@AlindaAnthonykeidy]

Thanks free code camp... We truly appreciate

[@amarnath.c7861]

this one couldn't respond me? what can i do?? if i put input , it couldnt respnd me..tell me a solution

[@EricMwangi-r1d]

Thanks bro.

[@JamesLove2]

When I went to refresh the page, it says template does not exist at chatbot.html, but I copied the provided code and saved my file as chatbot.html. What could be wrong?

[@amarnath.c7861]

same here

[@briansalvator31]

make sure your templates folder is in the correct directory

[@briansalvator31]

guess this project is restricted to those who have paid access to the openAI huh

[@jishnusaurav]

Can you also share to add a voice button ?

[@user-gq1ij]

I don't understand the need of gpt-4 integration Can someone explain

[@adewebs]

Tomi, can you please make a tutorial on how we can convert our Django projects into .exe or .apk and iOS. This will come helpful, thanks bro, thumbs up

[@TechDesignHub]

Django is for back end .. you can use other framework for front end and you can serve that into exe or APK which will still connect to a server ( backend )

[@mohdalim77]

Bukayo saka doing side quests 😂

[@momojafar9385]

can you do one with llama instead?

[@Duke-of-Minecraft]

can we add our own ui and if yes then how to do it and wher to do it

[@pritampatil7521]

The OpenAI api key that generates its free of cost

[@VishwajitRajput-i2q]

i can not get answers by api key why, please help me??

[@rupesh5365]

Same bro may be model id not working

[@ENDTIM3SPRODUCTIONS]

could had added a link to the original video to get the templates!

[@moneymemes]

YEAH , WITHOUT THAT THE PROJECT IS MEANINGLESS; I HAVE SEARCHED IT EVERYWHERE

[@AzimQurbonov-j1n]

where can i get js code ?

[@rahulky9574]

i am getting error : Uncaught SyntaxError: Unexpected token '

[@samuelodunayo2632]

Same here How did you resolve it?

[@cloverbeats7990]

i keep getting a "Uncaught (in promise) SyntaxError: Unexpected token '

[@areejshoona4165]

How you open the finder plzz help me

[@tobechukwumarizu2471]

My aiohttp is not downloading 😢

[@jayy4081]

Hi do i need a paid openai account?

[@jeremy6749]

yes and to pay 18$ for paid account

[@dhananjayadk4611]

❤❤❤ first

[@biragacharya9745]

is it still working?

[@youssefliti]

Thank's

[@ittechzone8036]

Missed to add GitHub url

[@ENDTIM3SPRODUCTIONS]

right i was about to say the same thing

[@quincylarsonmusic]

GitHub link is now in the description.

[@ittechzone8036]

Thank you

[@그대여달99]

43:00

[@angeldiaz3018]

Yo where are the html files?

[@koalapeach7477]

18:31

[@oyesaurabh]

is this api paid ?

[@lewisndungu7239]

Nope

[@noxknock2740]

@@lewisndungu7239 Is this api paid now

[@Tman234h]

wow how old is this kid??

[@quincylarsonmusic]

He's 18. One of the brightest, most ambitious devs I know.

[@qaissabbas1237]

رررع

[@avantikashaileshraodeshmukh]

thanksss buddy

[@Ceejayokoye]

This accent looks Nigerian

[@Lil-Undercover]

Yes he is a Nigerian

[@Ceejayokoye]

@@Lil-Undercoverreally

[@germanpinto883]

WOW he's a child 🤯

[@moomoo-bv3ig]

I learned frames in HTML before I was 17, and had a free page that hosted my website with frames, complete with message boards on every page and it lasted almost ten years. That is the best time to learn and teach code.

[@areebahmad56]

Hey! I am first.

[@Famelhaut]

This project is filled with bad practices. Be warned.

[@vishnuhunnithan3086]

Like? Just making remarks without qualifying it with observations is neither useful nor does it make you sound like someone who is serious about learning.

[@Famelhaut]

@vishnuhunnithan3086 You're right, I should have elaborated. The project doesn't have a gitignore, requirements txt or a pyproject toml file. It wasn't made with dependency or package management in mind, or from a project template. This is why the sqlite3 database and pycache files were committed to the project. The production secrets are hardcoded in the code instead of being imported from enviroment variables with something like python-dotenv or better yet, from the system itself. There are only development settings. In a real application you would either have another settings file for production or another branch with all the production settings. The templates aren't namespaced to the app. The Django tutorial explains very well why this is important. The chat model uses the User model directly. You should never do this, and instead create a new User model from the AbstractUser class. The Djando docs explain why aswell. The templates define the style directly. This should be in a specialized css file that is imported in the base html. The base html template uses cdns, you shouldn't use cdns in production unless you're the owner of them. It also imports bootstrap, so I wonder why even have custom styles in the templates. The register and login templates can probably be simplified, but it's not a big problem. The chat template uses vanilla js when jquery was imported in the base. The code should either be using jquery or base html shouldn't use the jquery cdn. The chat template uses vanilla js in a script tag, it should be in another file specialized js file. The js code is fine, altough I would have personally used htmx instead of json. Now, the biggest problems are in views py: This project should have used websockets with django-channels instead of doing rest-like ajax requests. Chat applications need to be responsive to requests and don't follow the REST pattern very well, this is why if you use any chat application like discord, whatsapp, telegram, etc and switch to the network tab, you'll see that they use websockets. For a simple demonstration project it's fine, but it should have been done with websockets. The django-channels tutorial teaches you how to make a chat application. Leaving that aside, there are other problems in views py: ask_openapi shouldn't be in views py. It's not a view, it should be in utils py or services py or anywhere else. The project only uses functional views. These don't scale, and will only bring problems down the road if you don't refactor them into class-based-views. The project should have overriden one of the generic views from django with the additional needed functionality or written one from scratch by inheriting from View. login and register shouldn't exist. Django comes with pre-defined, customizable class-based-views for login, logout and changing password. registering can be done using the default UserCreationForm and a CreateView. The only thing that isn't done for you are the templates. The project shouldn't have a a view returning Json data, this should be handled with a serializer, with either django-rest or django-ninja. The view isn't the place to be doing this. The view that returns the Json should be in another one, not the same. And preferably in another application. The filtering shouldn't be done from filter() directly, a custom manager or queryset should have been defined and a custom method like "by_user()" should have been used. The project uses the Chat model directly to create new objects. This is VERY VERY WRONG AND DANGEROUS. You should ALWAYS sanitize data coming from the frontend. Django has a forms framework that helps you do this ultra easy. Worse, this same data is used for a call to chatgpt's API. This same pattern is used in the login and registering. The project is also missing tests, but most tutorials don't usually include those. There's probably more stuff that I've missed, but the conclusion is that the person that made this tutorial isn't experienced enough with web development nor django. This is fine, we all start from 0 and learn. The problem is that this is a tutorial in a programming learning channel with 9.3 million subscribers. People will learn from here and use this code for real applications, and by doing so make stuff filled with bad practices and vulnerabilities.

[@Famelhaut]

@@vishnuhunnithan3086 You're right, I should have elaborated. The project doesn't have a gitignore, requirements txt or a pyproject toml file. It wasn't made with dependency or package management in mind, or from a project template. This is why the sqlite3 database and pycache files were committed to the project. The production secrets are hardcoded in the code instead of being imported from enviroment variables with something like python-dotenv or better yet, from the system itself. There are only development settings. In a real application you would either have another settings file for production or another branch with all the production settings. The templates aren't namespaced to the app. The Django tutorial explains very well why this is important. The chat model uses the User model directly. You should never do this, and instead create a new User model from the AbstractUser class. The Djando docs explain why aswell. The templates define the style directly. This should be in a specialized css file that is imported in the base html. The base html template uses cdns, you shouldn't use cdns in production unless you're the owner of them. It also imports bootstrap, so I wonder why even have custom styles in the templates. The register and login templates can probably be simplified, but it's not a big problem. The chat template uses vanilla js when jquery was imported in the base. The code should either be using jquery or base html shouldn't use the jquery cdn. The chat template uses vanilla js in a script tag, it should be in another file specialized js file. The js code is fine, altough I would have personally used htmx instead of json. Now, the biggest problems are in views py: This project should have used websockets with django-channels instead of doing rest-like ajax requests. Chat applications need to be responsive to requests and don't follow the REST pattern very well, this is why if you use any chat application like discord, whatsapp, telegram, etc and switch to the network tab, you'll see that they use websockets. For a simple demonstration project it's fine, but it should have been done with websockets. The django-channels tutorial teaches you how to make a chat application. Leaving that aside, there are other problems in views py: ask_openapi shouldn't be in views py. It's not a view, it should be in utils py or services py or anywhere else. The project only uses functional views. These don't scale, and will only bring problems down the road if you don't refactor them into class-based-views. The project should have overriden one of the generic views from django with the additional needed functionality or written one from scratch by inheriting from View. login and register shouldn't exist. Django comes with pre-defined, customizable class-based-views for login, logout and changing password. registering can be done using the default UserCreationForm and a CreateView. The only thing that isn't done for you are the templates. The project shouldn't have a a view returning Json data, this should be handled with a serializer, with either django-rest or django-ninja. The view isn't the place to be doing this. The view that returns the Json should be in another one, not the same. And preferably in another application. The filtering shouldn't be done from filter() directly, a custom manager or queryset should have been defined and a custom method like "by_user()" should have been used. The project uses the Chat model directly to create new objects. This is VERY VERY WRONG AND DANGEROUS. You should ALWAYS sanitize data coming from the frontend. Django has a forms framework that helps you do this ultra easy. Worse, this same data is used for a call to chatgpt's API. This same pattern is used in the login and registering. The project is also missing tests, but most tutorials don't usually include those. There's probably more stuff that I've missed, but the conclusion is that the person that made this tutorial isn't experienced enough with web development nor django. This is fine, we all start from 0 and learn. The problem is that this is a tutorial in a programming learning channel with 9.3 million subscribers. People will learn from here and use this code for real applications, and by doing so make stuff filled with bad practices and vulnerabilities.

[@Famelhaut]

​@@vishnuhunnithan3086 You're right, I should have elaborated. The project doesn't have a gitignore, requirements txt or a pyproject toml file. It wasn't made with dependency or package management in mind, or from a project template. This is why the sqlite3 database and pycache files were committed to the project. The production secrets are hardcoded in the code instead of being imported from enviroment variables with something like python-dotenv or better yet, from the system itself. There are only development settings. In a real application you would either have another settings file for production or another branch with all the production settings. The templates aren't namespaced to the app. The Django tutorial explains very well why this is important. The chat model uses the User model directly. You should never do this, and instead create a new User model from the AbstractUser class. The Djando docs explain why aswell. The templates define the style directly. This should be in a specialized css file that is imported in the base html. The base html template uses cdns, you shouldn't use cdns in production unless you're the owner of them. It also imports bootstrap, so I wonder why even have custom styles in the templates. The register and login templates can probably be simplified, but it's not a big problem. The chat template uses vanilla js when jquery was imported in the base. The code should either be using jquery or base.html shouldn't use the jquery cdn. The chat template uses vanilla js in a script tag, it should be in another file specialized .js file. The js code is fine, altough I would have personally used htmx instead of json. Now, the biggest problems are in views py: This project should have used websockets with django-channels instead of doing rest-like ajax requests. Chat applications need to be responsive to requests and don't follow the REST pattern very well, this is why if you use any chat application like discord, whatsapp, telegram, etc and switch to the network tab, you'll see that they use websockets. For a simple demonstration project it's fine, but it should have been done with websockets. The django-channels tutorial teaches you how to make a chat application. Leaving that aside, there are other problems in views py: ask_openapi shouldn't be in views py. It's not a view, it should be in utils.py or services.py or anywhere else. The project only uses functional views. These don't scale, and will only bring problems down the road if you don't refactor them into class-based-views. The project should have overriden one of the generic views from django with the additional needed functionality or written one from scratch by inheriting from View. login and register shouldn't exist. Django comes with pre-defined, customizable class-based-views for login, logout and changing password. registering can be done using the default UserCreationForm and a CreateView. The only thing that isn't done for you are the templates. The project shouldn't have a a view returning Json data, this should be handled with a serializer, with either django-rest or django-ninja. The view isn't the place to be doing this. The view that returns the Json should be in another one, not the same. And preferably in another application. The filtering shouldn't be done from filter() directly, a custom manager or queryset should have been defined and a custom method like "by_user()" should have been used. The project uses the Chat model directly to create new objects. This is VERY VERY WRONG AND DANGEROUS. You should ALWAYS sanitize data coming from the frontend. Django has a forms framework that helps you do this ultra easy. Worse, this same data is used for a call to chatgpt's API. This same pattern is used in the login and registering. The project is also missing tests, but most tutorials don't usually include those. There's probably more stuff that I've missed, but the conclusion is that the person that made this tutorial isn't experienced enough with web development nor django. This is fine, we all start from 0 and learn. The problem is that this is a tutorial in a programming learning channel with 9.3 million subscribers. People will learn from here and use this code for real applications, and by doing so make stuff filled with bad practices and vulnerabilities.

[@yahhdsad3041]

@@vishnuhunnithan3086 You're right, I should have elaborated. The project doesn't have a gitignore, requirements txt or a pyproject toml file. It wasn't made with dependency or package management in mind, or from a project template. This is why the sqlite3 database and pycache files were committed to the project. The production secrets are hardcoded in the code instead of being imported from enviroment variables with something like python-dotenv or better yet, from the system itself. There are only development settings. In a real application you would either have another settings file for production or another branch with all the production settings. The templates aren't namespaced to the app. The Django tutorial explains very well why this is important. The chat model uses the User model directly. You should never do this, and instead create a new User model from the AbstractUser class. The Djando docs explain why aswell. The templates define the style directly. This should be in a specialized css file that is imported in the base html. The base html template uses cdns, you shouldn't use cdns in production unless you're the owner of them. It also imports bootstrap, so I wonder why even have custom styles in the templates. The register and login templates can probably be simplified, but it's not a big problem. The chat template uses vanilla js when jquery was imported in the base. The code should either be using jquery or base.html shouldn't use the jquery cdn. The chat template uses vanilla js in a script tag, it should be in another file specialized .js file. The js code is fine, altough I would have personally used htmx instead of json. Now, the biggest problems are in views py: This project should have used websockets with django-channels instead of doing rest-like ajax requests. Chat applications need to be responsive to requests and don't follow the REST pattern very well, this is why if you use any chat application like discord, whatsapp, telegram, etc and switch to the network tab, you'll see that they use websockets. For a simple demonstration project it's fine, but it should have been done with websockets. The django-channels tutorial teaches you how to make a chat application. Leaving that aside, there are other problems in views py: ask_openapi shouldn't be in views py. It's not a view, it should be in utils.py or services.py or anywhere else. The project only uses functional views. These don't scale, and will only bring problems down the road if you don't refactor them into class-based-views. The project should have overriden one of the generic views from django with the additional needed functionality or written one from scratch by inheriting from View. login and register shouldn't exist. Django comes with pre-defined, customizable class-based-views for login, logout and changing password. registering can be done using the default UserCreationForm and a CreateView. The only thing that isn't done for you are the templates. The project shouldn't have a a view returning Json data, this should be handled with a serializer, with either django-rest or django-ninja. The view isn't the place to be doing this. The view that returns the Json should be in another one, not the same. And preferably in another application. The filtering shouldn't be done from filter() directly, a custom manager or queryset should have been defined and a custom method like "by_user()" should have been used. The project uses the Chat model directly to create new objects. This is VERY VERY WRONG AND DANGEROUS. You should ALWAYS sanitize data coming from the frontend. Django has a forms framework that helps you do this ultra easy. Worse, this same data is used for a call to chatgpt's API. This same pattern is used in the login and registering. The project is also missing tests, but most tutorials don't usually include those. There's probably more stuff that I've missed, but the conclusion is that the person that made this tutorial isn't experienced enough with web development nor django. This is fine, we all start from 0 and learn. The problem is that this is a tutorial in a programming learning channel with 9.3 million subscribers. People will learn from here and use this code for real applications, and by doing so make stuff filled with bad practices and vulnerabilities.

[@naspy971]

Django ? This sh*t is still alive ?

[@bijayaojha8288]

but why not django??

[@AzusaSnowflake]

Yea, way better than your MERN sh*t.

[@theencryptedpartition4633]

Unchained

[@MarcusHCrawford]

Django is doing just fine, thank you very much.

[@MarcusHCrawford]

Not everyone uses JavaScript and React for everything.

[@chordiasankalp820]

Not well explained

[@xxoooOFxx]

Would love to see how you'd 3x0lain it better.

[@R3zacs]

hi right now ghat gpt doesnt offer any free api we should buy chatgpt4

[@sukuna1374]

can any one tell me how to open the db.sqlite3 file it says ( file is not displayed in the text editor because it is either binary or uses an unsupported text encoding)

[@nomanshariq4165]

use this extension SQLite Viewer

[@briansalvator31]

I keep getting this error. openai.error.RateLimitError: You exceeded your current quota, please check your plan and billing details.

[@m4y4nknyon34]

same i don't know how to make it right

[@nathanloco8]

you need to sign up for a new account since your api free trial expired, this happened to me too and i made a new account

[@Returnofonz]

Your api token is deprecated. Add card info and try again with new token