Hi,
In the last couple of days I started experimenting with Django and Django Rest Framework. Using the excellent documentation and ViewSets I was able to create a PoC API in a very short time. I was also able to add Django Rest Swagger for documentation of the API. However, at this point I'd like to secure access to the Swagger API documentation, but I'm unclear on how to limit access to Django 'superusers.' I'd appreciate clarification on how to do so.
-- In the last couple of days I started experimenting with Django and Django Rest Framework. Using the excellent documentation and ViewSets I was able to create a PoC API in a very short time. I was also able to add Django Rest Swagger for documentation of the API. However, at this point I'd like to secure access to the Swagger API documentation, but I'm unclear on how to limit access to Django 'superusers.' I'd appreciate clarification on how to do so.
Also, in unit tests (particularly of views) I'd like to mock the model, rather than have the models call against the database. Are there any Django "conventions" or best practices for doing so?
Thanks.
Best,
Ari
Thanks.
Best,
Ari
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/65270a6c-eee4-44a0-b58c-ffad78e864c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment