[GH-ISSUE #187] add a slug field for domain and hosts #174

New issue

Closed

opened 2026-02-26 09:36:17 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 09:36:17 +03:00

Owner

Originally created by @elnappo on GitHub (Nov 29, 2014).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/187

e.g.: nsupdate.info/host/test-nsupdate-de/ instead of nsupdate.info/host/1341/
This makes urls much more readable and don't expose host and domain ids
django-extensions already has a AutoSlugField or use https://bitbucket.org/neithere/django-autoslug/

Originally created by @elnappo on GitHub (Nov 29, 2014). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/187 e.g.: nsupdate.info/host/test-nsupdate-de/ instead of nsupdate.info/host/1341/ This makes urls much more readable and don't expose host and domain ids django-extensions already has a AutoSlugField or use https://bitbucket.org/neithere/django-autoslug/

kerem

2026-02-26 09:36:17 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-26 09:36:19 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Nov 29, 2014):

do we really need an additional db field or can it work with existing fields, like domain and host?

@ThomasWaldmann commented on GitHub (Nov 29, 2014): do we really need an additional db field or can it work with existing fields, like domain and host?

kerem commented

2026-02-26 09:36:19 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Feb 8, 2015):

looked at django-autoslug shortly. latest release seems to be behind repo quite a bit and repo has changes for django 1.7 support that are not released yet.

@ThomasWaldmann commented on GitHub (Feb 8, 2015): looked at django-autoslug shortly. latest release seems to be behind repo quite a bit and repo has changes for django 1.7 support that are not released yet.

kerem referenced this issue

2026-02-26 10:31:20 +03:00

[PR #174] [MERGED] template improvements #399