starred/nsupdate.info-nsupdate-info

Fork 0

mirror of https://github.com/nsupdate-info/nsupdate.info.git synced 2026-04-25 08:35:56 +03:00

[GH-ISSUE #120] consider replacing django-registration #116

New issue

Open

opened 2026-02-26 09:35:46 +03:00 by kerem · 9 comments

kerem commented

2026-02-26 09:35:46 +03:00

Owner

Originally created by @ThomasWaldmann on GitHub (Dec 22, 2013).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/120

django-registration is used so users can register for an account, then it does send an email with an activation link for the account.

https://bitbucket.org/ubernostrum/django-registration/

but, looking at that project displays some issues:

no issue tracker (wtf?)
lots of (sometimes trivial) pull requests not merged since about a year
no commit to main repo since half a year
not even the link to the docs works due to a trivial markup error
latest pypi release as of now does not work with django 1.6 and needs a patch (that can be made from one of the pull requests)

so, let's consider other options....

Originally created by @ThomasWaldmann on GitHub (Dec 22, 2013). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/120 django-registration is used so users can register for an account, then it does send an email with an activation link for the account. https://bitbucket.org/ubernostrum/django-registration/ but, looking at that project displays some issues: - no issue tracker (wtf?) - lots of (sometimes trivial) pull requests not merged since about a year - no commit to main repo since half a year - not even the link to the docs works due to a trivial markup error - latest pypi release as of now does not work with django 1.6 and needs a patch (that can be made from one of the pull requests) so, let's consider other options....

kerem added the

enhancement

label

2026-02-26 09:35:46 +03:00

kerem commented

2026-02-26 09:35:47 +03:00

Author

Owner

@elnappo commented on GitHub (Jan 15, 2014):

https://github.com/pennersr/django-allauth sounds nice

@elnappo commented on GitHub (Jan 15, 2014): https://github.com/pennersr/django-allauth sounds nice

kerem commented

2026-02-26 09:35:47 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Jan 15, 2014):

yeah, that was one I was considering also.

@ThomasWaldmann commented on GitHub (Jan 15, 2014): yeah, that was one I was considering also.

kerem commented

2026-02-26 09:35:47 +03:00

Author

Owner

@elnappo commented on GitHub (Jan 20, 2014):

okay, make a branch for this? should i start with this? will close four issues.

@elnappo commented on GitHub (Jan 20, 2014): okay, make a branch for this? should i start with this? will close four issues. - #87 - #116 - #119

kerem commented

2026-02-26 09:35:48 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Jan 20, 2014):

yeah, create a working branch if you like. "allauth" maybe? thanks for helping!

@ThomasWaldmann commented on GitHub (Jan 20, 2014): yeah, create a working branch if you like. "allauth" maybe? thanks for helping!

kerem commented

2026-02-26 09:35:48 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Feb 1, 2014):

btw, we'll need some sort of migration strategy if we go to some other auth module.

the existing local accounts maybe are no problem as they are always handled in the same way.

but what about the existing associated social accounts? will they still work as before? what if somebody only has a social login but no local one, will he still be able to login?

@ThomasWaldmann commented on GitHub (Feb 1, 2014): btw, we'll need some sort of migration strategy if we go to some other auth module. the existing local accounts maybe are no problem as they are always handled in the same way. but what about the existing associated social accounts? will they still work as before? what if somebody only has a social login but no local one, will he still be able to login?

kerem commented

2026-02-26 09:35:48 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Feb 1, 2014):

for nsupdate.info site, we support google, github and bitbucket currently.
i didn't see bitbucket in the allauth configs.

@ThomasWaldmann commented on GitHub (Feb 1, 2014): for nsupdate.info site, we support google, github and bitbucket currently. i didn't see bitbucket in the allauth configs.

kerem commented

2026-02-26 09:35:48 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Feb 5, 2014):

https://github.com/pennersr/django-allauth/issues/530 bitbucket support added

https://github.com/pennersr/django-allauth/issues/531 some hints about migration

@ThomasWaldmann commented on GitHub (Feb 5, 2014): https://github.com/pennersr/django-allauth/issues/530 bitbucket support added https://github.com/pennersr/django-allauth/issues/531 some hints about migration

kerem commented

2026-02-26 09:35:48 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Feb 16, 2014):

btw, https://github.com/asmaps/hopper.pw is also using django-allauth.

@ThomasWaldmann commented on GitHub (Feb 16, 2014): btw, https://github.com/asmaps/hopper.pw is also using django-allauth.

kerem commented

2026-02-26 09:35:48 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Oct 28, 2014):

on hold for now:
a) switching to allauth isn't easy due to migration of existing data
b) have recently switched from django-registration to django-registration-redux, which seems better maintained, so it'll hopefully be less pain.

@ThomasWaldmann commented on GitHub (Oct 28, 2014): on hold for now: a) switching to allauth isn't easy due to migration of existing data b) have recently switched from django-registration to django-registration-redux, which seems better maintained, so it'll hopefully be less pain.