send your views pls

I'm getting error " no such column: home_information.time " . Home is my app information is my model and time is a variable which is getting value through date timefeild Please see this https://paste.pics/7DAI5

I am having a knowledge of html and Css...can I start learning backend directly... Using django

Start with learning python

But i dont have knowledge of javascript bootstrap jquery

And then move on to learn work structure of backed

so, using Jinja with django is kinda redundant and useless 🤷🏻‍♂

Hi, How to enable csrf protection in DRF Token authentication?

pass csrf token in your header.

If I enable only token authentication, django bydefault disables csrf protection. So I added csrf_protect method decorator on unsafe method requests.

what i know it doesn't disables csrf protection.

i didn't know that.

after adding that decorator it is raising csrf token missing error.

after adding that decorator it is raising csrf token missing error.

i didn't know that.

Do you know, Does django generate a new token after using previous token in unsafe method?

https://docs.djangoproject.com/en/2.2/ref/csrf/

yeah

Question for the advanced Django players here (@izznogooood, @c0x6A, @LuchoUY, any other qualified?) What solution would you see to somehow allow a frontend build system (webpack or gulp), to use the django templates to render static pages? In other words, you have django templates in your project, that make use of models and stuff, they are already implemented. They already work fine, on Django's runserver. However, In top of that, I want gulp/webpack to watch those SAME files, to render them in a separate local webserver, somehow ignoring the {% for item in items %} and other dynamic content, or having default hardcoded ones.

Question for the advanced Django players here (@izznogooood, @c0x6A, @LuchoUY, any other qualified?) What solution would you see to somehow allow a frontend build system (webpack or gulp), to use the django templates to render static pages? In other words, you have django templates in your project, that make use of models and stuff, they are already implemented. They already work fine, on Django's runserver. However, In top of that, I want gulp/webpack to watch those SAME files, to render them in a separate local webserver, somehow ignoring the {% for item in items %} and other dynamic content, or having default hardcoded ones.

Many messages such as: "hey I need hlp plz system dont work how should I do PLEASE NOW"

how can i notify the user that they entered incorrect password . i use django authentication and i think the name of error message is not messages . how can i notify then the user incorrect password or username errorr?

but i dont know the builtin django auth

thank you very much i was on this page but i didn't notice this

.

pls send information model details

I think your overthinking this. Why don't you make a dummy site in docker-compose with everything the site needs then you can just run the dev server inside letting him see the changes live. For a front end dev to understand the core things of Django templates is easy. Like her comes x amount of this or show this if user is logged in etc...

If I understood it good, I dont see an easy way to achieve this if you want to use the SAME templates, maybe you could play with verbatim template tag or create a specific template tag which allow to encapsulate a block to ignore and provide a default value which the front end dev would provide, but the frontend dev should anyways learn where he should put the default code snippet and deal with lots of verbosity. Additionally these extra template logic would also need to be processed in production which could decrease a bit the performance

Thank you for your input!! well if I understand it well you suggest that I might ask the front end dev to run my dev docker-contained django app in order to let him build the frontend, hmm I see your point. I didnt understand what you said about DB, how will he be able to have one ready for him to code? Front end stack is ever evolving and I'd like to find a way to let the frontend engineer use their favorite tools / typescript / babel / scss / whatever without having to bother about Django. Today I have to manually migrate their nunchuck templates into Django. Both look pretty similar so I'm wondering how I could make it the same file. If you know better ways to make frontend devs collaborating on Django while still using their tools and keep the whole thing simple, I am highly interested : )

Related to template engines, not sure if its an stupid idea but recently I have been dealing and experimenting with vuejs, I really like it but having to deal with a django project for the API and a vue one with SSR for getting good SEO I think is a mess for some small projects and was thinking that maybe it would be possible to create a dropin replacement for django template language where you pass the django context object as vuejs data and then compile all the template from django with vuejs instead of DTL (similar to what nuxt does but from django). Any impressions/ideas/problems you could see about this?

Well, separate them. Build a Django graphql backend and let the front end do exactly what they want.

I mean mount a folder for your dB and keep it versioned so whenever you run the dev env you have a db. How do you develop now?

I am using vuejs in one of my Django projects. That's an interesting question. I guess it should work, but I cant tell for sure as I'm not sure how the "let vuejs compile" part of it would take place. Do you mean using vuejs as a full SPA or just on some pages? What I mean is, do you want to let vuejs manage the routing? I find it better to let Django do the routing, load a templateview that will pass some serialized data to vuejs's data and then vuejs works from there on this specific page. No need for SSR to solve any SEO problems, it's already rendered by Django, but still you have vuejs to do whatever you want (except routing). If you absolutely NEED vuejs to work as a full SPA (including routing) then why use Django at all? you can serve it as a static index.html and then make all your API calls to a DRF backend.