Jason, we agree. What I mean by having a public app is the same as what you
mean by having something in production. Anything in production should have a
reverse proxy like nginx or Apache, etc. Reading my message again, I can see
why it could have been taken that way when I ranted about the
>
> If you said no to any of these, then you shouldn’t be using nginx.
>
I *strongly* disagree with this. you should use apache with mod_wsg or
nginx with uwsgi/gunicorn/etc for production, in which having 10, 1000 or a
million users is beside the question.
--
You received this message
Hi, I encountered the same situation, do you know how to deal with it?
在 2018年3月24日星期六 UTC+8上午6:48:23，Sassan Haradji写道：
>
> Is it possible to dynamically change queryset of a nested field based on
> request.user for example? It is possible for PrimaryKeyRelatedField by
> changing queryset
Remove nginx from the equation. Use runserver because you’re clearly still in
development. Does your app work then?
IMHO you are not ready to add more things to your stack yet. The ONLY thing
that should be in your stack right now is Django, and possibly a different
database because ...
http://www.django-rest-framework.org/api-guide/validators/#writing-custom-validators
You need to write a custom validator
--
You received this message because you are subscribed to the Google Groups
"Django REST framework" group.
To unsubscribe from this group and stop receiving emails from
sounds to me you don't have server_name set up for your nginx. But not
sure if this is the relevant place for that, since its not Django/DRF
related, but rather nginx configuration.
Perhaps stackoverflow would be a better place to ask?
--
You received this message because you are subscribed
