kstypik / letteranne Goto Github PK

Currently, after #10 we are using JWT for authentication and they are problematic (1) (2)

Switch over to standard Django sessions which are battle-tested, provide reasonable security and are easy to implement.

Probably dependency on dj-rest-auth should be dropped and custom views should be provided or we can try shoehorning django-allauth into our API needs (see pennersr/django-allauth#360)

It is recommended by Django to provide your own User model to simplify future changes and omit frustrating database migration problems.

Documentation reference: https://docs.djangoproject.com/en/5.0/topics/auth/customizing/#substituting-a-custom-user-model

Update the README to include information on how to start developing the application.

Describe usage of

• DevContainers
• Docker
• EditorConfig
• pre-commit
• mise

One of the most basic features that should be available in the application is allowing users to log in to their accounts.

Create API endpoints to:

• log in
• register a new account
• logout
• change credentials
• reset password

Things to consider:

• authenticate by username/email/both?
• which authentication method to choose? Token-based? Session-based?
• provide SSO using Google, Facebook, etc.?

Include HadoLint and ShellCheck in containers.

Users should be able to authenticate. Depends on #2

Might be useful to start with pre-existing components from the excellent Mantine UI collection: https://ui.mantine.dev/category/authentication/

Just can simplify maintenance of the project by adding commands to do common tasks, such as generating & applying migrations, compiling translation files, seeding the database, linting, etc.