There is nothing that requires you to use that path for the auth urls. The docs show that as an example. You are free to assign the auth urls to any path you wish. (You would also want to change the LOGIN_URL and LOGIN_REDIRECT_URL settings to match.)
Now, you can still create and use your own authentication views if you want - but that’s a different question.
Yes i am using AbstractBase User, and will inherit from to a Client Class.
Custom Folder: my authentication folder Named accounts not registration as in the views.
this url as i understand if i will use it i have to use the same url password_reset,
i guess its not very critical i can use the same naming for url paths. if it will not conflict with the django Authentication views itself.
What “folder”? I don’t understand what you’re referring to here. There are no “folders” involved in the views.
Again, I think there’s a terminology issue here - I don’t understand what you’re trying to explain here.
What is your objective behind all this? What specifically do you want the results to be? (I’m beginning to think these questions may be a type of XY problem. Instead of addressing what you think the solution is, I’d like to get to the root issue you’re trying to resolve.)
Why does that matter? That is not something visible to the outside - it’s purely an internal function. If you have 'APP_DIRS': True in your TEMPLATES setting, those templates would still reside in your app. If not, you can include them in your project-level templates directory.
Then work with what’s provided. I don’t understand what it is you’re trying to change, or why.
I have a personal motto I rely upon regularly: “Don’t fight the framework”. Work with Django, not against it. Things work a lot more smoothly that way.