djoser VS MailHog

That's what I'd usually say too, but this issue does give some "neglected project" vibes - the version on pypi is still quite a bit older than what's in the repo.

e.g.: https://github.com/sunscrapers/djoser/blob/master/djoser/constants.py

Right now, I'm using dj-rest-auth for Token based authentication. I store token in the localStorage. Earlier I was using djoser for adding auth in the project (I wrote article about my approach with djoser).

View on GitHub

Djoser is an open-source authentication library for Django. It is a simple library for providing basic authentication in a Django app, and it is used alongside the Django REST Framework. In this article, we will be looking at how to customize URLs in Djoser.

For Djoser this looks to be fine, there is an issue mentioning Django 4.0 but it looks like that just requires a work around for a dependency.

djoser if you are using DRF

Customizing Serializers

A reusable library implementing auth logic in DRF: https://github.com/sunscrapers/djoser

I'm using Djoser on the backend and I want to save tokens in Redis when they are created. I want this because I want to single user from one account can use my app, so I'm about to store all created tokens and then invalidate them if a user with this `id` login's from another device/browser. So my question is, am I need to redefine this method? Please push me in the right direction, I'm kinda lost. Maybe there is a better solution.

Mailhog

hey HN, I recently published an article going deep into email previewing (in Ruby on Rails, but I think it's relevant beyond Rails).

MailCatcher (https://github.com/sj26/mailcatcher) and MailHog (https://github.com/mailhog/MailHog) are super handy and easy to run locally. Both spin up an SMTP server which you can direct mail to, and give you a nice web interface to browse mail and preview it.

Happy to answer any question! thanks, harrison

https://github.com/mailhog/MailHog This is set up for our test environments. Worth looking into

Does it say it's being send on localhost or on production? How is it "saying" it's being sent. We just setup mailhog to test emails for local development.

They should definitely invest in a chaos monkey (like Jim https://github.com/mailhog/MailHog/blob/master/docs/JIM.md)

depends on the infrastructre setup, but if you're able to specify smtp server the backend will use you can you something like https://github.com/mailhog/MailHog or https://github.com/rnwood/smtp4dev to catch any sent email, regardless of email address and read it via the respective api. Both mailhog and smtp4dev have decent api documentation.