Firstly you could create a function that uses these to models and renders a
html or csv format invoice. Then you could mail this to yourself. Once
the function is created then you could create a scheduled cron job using
celery or a even simple way would be to use crontab linux command with
monthl
/auth/
default/#topic-authorization
On Sun, Oct 30, 2016 at 7:59 PM, Amandeep Singh
wrote:
> Hi
> If student and warden have similar attributes and only differ in
> permission level than you could use the same User model for both of them
> and to provide different access levels by
The choices don't enforce any default validation. But if you are populating
the data from a http call then use ModelForm they show the invalid_choice
error message on entering value other than defined choices
On Mon, Mar 21, 2016 at 1:59 PM, Amine Yaiche wrote:
> Hi everyone,
>
> Given a field i
Hi Robert
As for as API key is concerned it's mainly to track usage records for a key
which would be linked to a person/user entity and provide a layer to block
unwanted requests(stops requests at middleware before hitting the view).
This key could be sent in headers or as the query parameter.
Bu
4 matches
Mail list logo
